text:
How to limit charging to a user defined limit?
My UleFone Armor 2 has a 4700mAh battery and I would like to limit the charging to 60% to reduce battery aging. The batteries in most of the phones are not user-replaceable and I am worried that a factory/service battery replacement might affect water resistance negatively.
How can I limit the charging to 60%? (But not limiting charging speed. I love fast charging.)
Lenovo ThinkPads have a built-in feature that does this, called “battery preservation mode”.

(One way is an outlet timer switch, but it would be great if the phone could limit it itself.)

I have always charged my phones to 100, and even kept them plugged in overnight all year long after each day's use, and so far none of them had any battery issues.

@NVZ How old is the battery? And which phones are they? (to find out the wattage and battery capacity)

I've done this since my Nokia N73, N82, Nokia 6233, Nokia E52, Samsung Galaxy W, many years ago.. then I have done so for all my phones including Samsung Galaxy S4, Duos, HTC 728, OnePlus One, 3T, Nokia 8, 5.1 Plus, etc to name some.

@NVZ That merely proves that your battery lifespan has been ok for you, not that it couldn't have been better if you used more optimal charge cycles. It is well known that doing full cycles (e.g. 0 to 100%) will wear out your battery faster than e.g. 30% to 80% cycles. All batteries will degrade over time, and you have had issues with all of those batteries, just not serious enough that you noticed or cared. Also typically a battery will last around 500 cycles before you start to notice anything.

@JBentley I just wish manufacturers could replace non-removable batteries without loss of water resistance.

@JBentley I'm aware, thanks. Another fact is, keeping it plugged in overnight does not have a significantly harmful effect on the battery. It is however better in the long run to unplug it if fully charged.

@NVZ Do you have a citation / source for that? What I've read is the opposite (see here for example). Charging every time to 100% can half or worse your lifespan, depending on which lower cutoff point you choose.

@JBentley I would not mind that lifespan so much if batteries were replaceable. But then, Apple intoxicated the mobile phone market with their inferior technology.

@neverMind9 Yes, I completely agree. It's not just Apple. For a long time I avoided upgrading from the now very obsolete Samsung Note 4, because it was the last in the series with a replaceable battery. It's nice to be able to get a 100% capacity battery every year or so for very little expense. But phone manufacturers want you to swap phones every couple of years rather than refurbish existing ones. The problem with NVZ's approach is that the higher end of the phone market is now very expensive, and I don't want to replace a £1000 phone every 2 years just for the battery.

@JBentley The Note 4 still works well in 2019, despite it is nearly 5 years old, in our case, it works as if it were new. Even the Note 3 from 2013 does fine (and has a lot of functionality that newer phones lack). But battery age has always been a nasty thing for non-removable batteries. When that battery is dead, the support service might be able to replace it, but whether they preserve water resistance and whether I will get my phone back intact (if at all) is not guaranteed. I have always avoided charging over 70% for that reason. I have battery-gerascophobia.

@JBentley But fast charging is so useful that I am ready to trade in a bit of battery life to enjoy the pleasure of watching the battery percentage indicator shoot up in a very short amount of time. I really enjoy fast charging. But the problem is: When the battery ag*s, the maximum terminal voltage of ~4.35V is reached at lower battery levels already (i.e. 45% instead of 65%) at full charging speed, so the charging current starts decreasing earlier already. Before reaching the 45%, the charging current is the same to avoid overcurrent thermal runaway, despite the battery voltage is below 4.3V

@NVZ, you are factually incorrect.  A battery can lose 20% of its life in less than a year by charging at 100% overnight.  This is by definition considered significant in the technical sense.  Probably what you mean is that you don't notice a difference, which is entirely subjective.  [1] https://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[4] https://www.macworld.com/article/3408336/ios-13s-new-optimized-battery-charging-feature-explained.html
[5] https://www.howtogeek.com/423451/how-ios-13-will-protect-your-iphones-battery-by-charging-to-80/

There now is a hardware+app solution for that, it's called Chargie. https://chargie.org
Basically, Chargie is a Bluetooth switch that is linked to an app on your phone. You set the desired level of charging, the app runs in the background and stops the charge at the percentage you set.
*disclosure: I am the CEO of Lighty Electronics, we have developed this solution and this isn't meant to be a spammy post with a link, but rather a very relevant solution to this issue. As far as I know, there are no other manufacturers of such devices.

No USB-C model?

I was all set to purchase one but shipping is $16.50, the device itself is only $23.00 (with the current sale.) Can we get another shipping option? All I'm given is DHL Express shipping, I don't need express.

@Gibolt, just use a USB C female to to USB A male adapter. My Google Pixel 5 even came with one in the box. Then, you can plug in a USB C charge cable to the adapter, and the adapter into the Chargie USB A female output.

Many ways - all of course, need
root. Without root, it's not possible and you can only  be notified either by automation or using an app as suggested in Chang's answer

Battery Charge Limit from Play Store. If it doesn't work directly, look for help in the XDA app thread. It doesn't trip safety net if you are using Magisk. I use this app currently (Bonus, it's open source and on f-droid) Edit: Not under active development and would not work with recent Android versions

Magisk Charging Switch Magisk module is also well spoken of.

My Charging Controller is another option. I recall seeing it as Magisk module but not listed now

Above modules not tried by me

If none of these work or you want to automate it yourself, some pointers in my answer here Automatically limit (stop) battery charging at a given percentage

Edit: Advanced Charging Control (acc) Magisk Module is a very versatile module with an associated front end app, which allows you to create profiles and even run profiles on schedule. For more details, see answer here
It allows the phone to charge up to a certain point and then be powered by USB only.  For example, you set the cut off at 80%,beyond 80% it doesn't charge the battery but draws a low current to keep the phone running. So when you disconnect charging, your phone is still at 80%! This feature requires to be supported by kernel though. I am using this currently on my One Plus 7 with Kirisakura kernel. For details see this Don't charge the battery but use connected power to run the phone

Do you know of any good solutions that use external hardware, like a Sonoff device to cut power?  Along the line of chargie.org, but open source.

@jdk1.0 Sorry but no Open source solutions I know of. If you do get to know, please make that an answer. Thanks

AccuBattery can notify you when the battery charge reaches a certain level. It won't stop the charging, unfortunately, but it's still worth a try. :)

Okay it's a while ago this thread was started ... ;-) The app you mentioned here has a big drawback. If you keep your phone plugged in over night you will be kicked out of the bed because of the alarm. Makes more sense to have a device that cuts off the power if a specific charging limit has been reached. I was searching for such an device for months. Finally I found the chargie app with its device and it does a great job since I started using it. I'm even thinking about developing an device that can even more than that und can change more that one phone at the same time.

My solution is to just use a CountDowntimer on the power outlet, set at 1:20 for me. One hit on the CD button to start the power (ON), and after 1:20 it's OFF again which will be at about 80% charge.
I use this:
https://www.clasohlson.com/se/Digitalt-kopplingsur/32-8618
Today you can buy a smart power outlet controlled with an app. It shouldn't be long until that app can turn of the power outlet charging the cellphone when it reaches 60%.

If your phone is rooted, do prefer an opensource Advanced Charging Controller module to flash either from Magisk or Twrp or any root solution u have choose. Here is the Github link for all details.
My experience in this module is, I am using this on my Oneplus 5 for about a year now, it doesn't disappoint me. It creates a charging loop. You can change it's default preference by typing acc commands. 80% is the default stopping point. And there is heating machining where its charge/discharge on & off if ur phone is expected to reach a peak point, which is a nice way to tackle the heating issue which is generally seen while charging.
If any problem occurs u can ask him on telegram or create an issue on Github.


text:
What does "SMS Messaging Account" mean in Hangouts?
I'm using Nexus 5. In my Hangouts settings, I noticed that the setting called "Default SMS Messaging Account" was set to my email address with my full name (And can alternatively be changed to "SMS" instead, which hides previous chats)
Does this mean that I've been broadcasting my full name and email address to everyone I sent "SMSes" to?

It is a weird and confusing design decision in my opinion.
To answer your question : No. Your full name and email address is only
linked to your Google account and is only used for your Hangout chat.

Thanks. Can you provide sources, or is this just a hunch? If this meta-info is transmitted, it may or may not show up in all messaging apps.

I do not have a source but I am sure about that.  The MAP protocol (used for SMS) does not even allow such thing. Jakar provided a good explanation here. ;)

So what is the difference?

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/

sort: votes


text:
Samsung reboots daily, but 'uptime' says otherwise
I'm pretty sure my Samsung Galaxy A20 reboots daily, at around the same time, showing the usual signs of a reboot: sounds some kind of notification it's rebooted, takes a few seconds to find the SIM and reload the weather widget, asks for the password instead of a fingerprint to log in ("after a reboot").
However, Settings/About Phone/Status/Uptime says it's been up for weeks.
What's going on with it? Is it just reloading part of the OS? Is this normal? Why is it rebooting daily?

Uptime (as exported in /proc/uptime and as in source code) changes only if kernel restarts. The signs of a reboot you've described may occur even if only Java stack is restarted i.e. Android framework has performed a soft reboot.

@IrfanLatif I think the big questions are why would it be doing this, and is this normal?  What do you think?

@RockPaperLz-MaskitorCasket why is it restarting? No it's not normal. Might be a bug. And bugs have many possible reasons, in fact countless. logcat (or pstore in case of kernel panic) usually helps to trace the root cause. But apparently this isn't the main question OP asked about.

@IrfanLatif Thanks.  I've never heard of it for a Samsung phone, but I wanted to make sure it wasn't some sort of weird Samsung thing.  Over the years, I've had various devices that intentionally auto-restart at a certain point, but IIRC, never an Android phone.  I think some of the Android-based TV boxes may auto-reboot once in a while though.

do another reboot yourself and check uptime

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Is there a way to set a global http/https proxy on Android 8 either with root or no root?
I am interested in setting up a global proxy on a rooted android 8.1.0 device. Is there a way to configure a system-wide proxy?
I have already tried a couple of apps to achieve this but have not had success.
shadowsocks - can't remove encryption and password setting. The password can be set blank but still does not seem to work as a plain proxy setup.
Proxy manager - doesn't allow you to set proxy host/ports manually. Only seems to support preset proxies
Drony - can't click on settings tab. I can only press turn on/off
ProxyDroid - keeps crashing. Does not run.
postern - insists on having an encryption method and user login credentials.

Related: How to set up a socks5 with Android cli?

Which kind of proxy you want to set? Is it a public one or do you have your own server?

I have my own local proxy server.

@IrfanLatif: Regarding the socks5 question that you referred to, I looked at that and tried it and it doesn't work for me. The app runs but it is not behaving as an http proxy, but perhaps more as a socks5 proxy. I need an http/https proxy

Instead of a proxy server you should set-up a PPTP VPN server and configure your device to use this VPN server. In difference to a proxy a VPN is used by all connections.

@Robert For my use case, I need an http/https proxy specifically. A VPN would not be the right solution.

@user55570 I just mentioned the VPN as it captures all the traffic. On the VPN end point you can of course implements a transparent proxy which therefore also processes all data as you don't have to configure it on Android side.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
How to determine why my pixel 3a running android 12 just beeped, and stop the unexplained beeping
My cell phone has a habit of beeping, with no recent notification present either on the lock screen or on the screen you get when you swipe down from the top of a home screen. (Sorry, I don't know what that screen is called.)
Casual investigation showed no way to find out why it just beeped, and three different screens showing different (inconsistent) sets of recent notifications - one of them showing only what time each app had last produced a notification, with no content.
One of these three lists distinguished between silent and non-silent notifications.
I was unable to find any interface that controlled what kind of notifications a given app could generate. The best I could do was a binary control for whether they could generate notifications at all.
I don't want to be interrupted by beeps without any associated notification I know how to find. I'd prefer to be able to get notifications, with beeps, from a selected small set of apps (calendar, text messages). Ideally, I'd prefer to apply more detailed controls (my podcast player need not tell me about automatic downloads, but I'd like to know about download failures). But given the (ahem) user friendly design, I'll settle for shutting up the random beeps, even if it means I can't get audible notifications from other apps; I do however require an audible ring for phone calls, so permanent do-not-disturb-mode is not an option.
Note that I'd be overjoyed to RTFM. Pointers to documentation will be gratefully welcomed. But from experience, Android vendors routinely customize the UI, such that a manual for e.g. a Samsung might well require me to interact with UI elements not present on a pixel running the same Android version. Also, Android 12 "made Android fun again" (according to one reviewer) by making major unexplained UI changes, as well as breaking existing functionality. So I fear that a manual for an earlier Android release will just tease me with instructions to do things no longer possible.

Guess your device has the Google apps (Playstore etc) installed? I saw that with one such device I had here a while ago. Took me quite some weeks to pin-point the culprit – and it was auto-updates being installed via Play. You could try to "silence" related apps one by one via settings › apps – like Play Store, download manager. I cannot remember which one finally did it. And yeah, that "fun" of breaking things has a long tradition – at least back to the times of 2.x from where I remember it still…

Aha - that also answers the question of how to control app notifications in more detail. You look for Apps, select each individual app, and look for notifications within that, so settings doesn't take you there if you search for notifications.

Nope, else it would turn up each single app you've installed. And the trouble with those "update notifications" in my case was they were "audio only" and thus left no "visible trace". I can't remember what brought me on the track – probably the fact that it was the only device with GApps on it and the other devices didn't have that problem (I usually run my devices Google-free; that one was a simple test device).


text:
Update work address
I configured my work address and now I can't change it. Sometimes Now shows me: "15 minutes to work" and the route, but it is the old one.
In and older version of Android you could just hold for a sec on location settings, but now you can only enable/disable and see which apps requested permission to my location.
Update: using CyanogenMod 11 (android 4.4.2 KitKat).

Install Google Maps.
Under Settings from Menu select ' Edit Home or Work'

Thanks, that is exactly what i needed. Not the first place I'll look at, but makes sense.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/


text:
Google Play Store suddenly started crashing with a java.lang.StackOverflowError error
Today I discovered that I can no longer open Google Play Store on my Galaxy S4, running Sumsung's version of Android v4.2.2.
When I try to open Google Play Store, it opens, but shorty fails with the following stack trace:
I/Finsky  ( 6299): [1] com.google.android.finsky.utils.dp.a(1041): Starting LocationRefresher
I/Finsky  ( 6299): [1] com.google.android.finsky.selfupdate.f.a(166): Skipping DFE self-update. Local Version [80691500] >= Server Version [-1]
I/Finsky  ( 6299): [1] com.google.android.finsky.utils.ji.a(102): TOS is accepted (pref)
I/Finsky  ( 6299): [1] com.google.android.finsky.utils.dk.a(64): com.samsung.groupcast available because owned, overriding [restriction=7].
I/Finsky  ( 6299): [1] com.google.android.finsky.utils.dk.a(64): ma.wanam.xposed available because owned, overriding [restriction=7].
I/Finsky  ( 6299): [1] com.google.android.finsky.utils.dk.a(64): com.questvisual.wordlens available because owned, overriding [restriction=7].
D/AndroidRuntime( 6299): Shutting down VM
E/AndroidRuntime( 6299): FATAL EXCEPTION: main
E/AndroidRuntime( 6299): java.lang.StackOverflowError
E/AndroidRuntime( 6299):    at java.util.HashMap.get(HashMap.java:298)
E/AndroidRuntime( 6299):    at com.google.android.finsky.FinskyApp.e(SourceFile:1355)
E/AndroidRuntime( 6299):    at com.google.android.finsky.FinskyApp.e(SourceFile:1379)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:83)
E/AndroidRuntime( 6299):    at com.google.android.finsky.api.model.Document.Z(SourceFile:1105)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:317)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:62)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.v.a(SourceFile:335)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:261)
E/AndroidRuntime( 6299):    at com.google.android.finsky.installer.b.a(SourceFile:3159)
E/AndroidRuntime( 6299):    at com.google.android.finsky.autoupdate.r.a(SourceFile:326)
E/AndroidRuntime( 6299):    at com.google.android
D/AndroidRuntime( 4557): Shutting down VM

I attempted to fix this by side-loading the latest Google Play Store APK (6.9.15.G-all [0] 3104571), but this did not fix the problem.
Considering that the infinite recursion is between autoupdate and installer packages, I assume this is some sort of bug that happens when Google Play Store tries to autoupdate something?
I am not sure how to recover from this situation, so any ideas would be appreciated.
EDIT 1: I was able to get rid of this particular error by downgrading Google Play Store all the way to 6.3.20.B-all [0] 2734767. However, although Google Play Store no longer crashes, a new error prevents me from actually downloading any content:
I/Finsky  (11347): [1] com.google.android.finsky.receivers.h.a(443): Request install of com.staircase3.opensignal v=120530 pri=2 for single_install
I/Finsky  (11347): [1] com.google.android.finsky.receivers.h.a(1184): Installer kick - starting com.staircase3.opensignal
I/Finsky  (11347): [1] com.google.android.finsky.receivers.ac.a(1177): Received VolleyError 922 (Error while retrieving information from server. [DF-DLA-15])
I/Finsky  (11347): [1] com.google.android.finsky.receivers.v.a(766): Cancel running installation of com.staircase3.opensignal (null)

Now, this DF-DLA-15 error appears to be quite famous:
https://productforums.google.com/forum/#!topic/play/pqV-NFm-qy8
I have tried all troubleshooting steps suggested in that thread, even the crazy-sounding ones. To be specific:

I cleared Data and Cache for Google Play Store and Service
Recreated and re-synced my Google Account
Deleted Dalvik cache
Unmounted the SD Card
Deleted and recreated my payment info in Google Play Store

After all that, still getting DF-DLA-15

It seems like it thinks two packages are dependent on each other, or something along those lines.  Have you tried clearing the data for the Play Store and Google Play Services?

I have tried clearing the Cache and Data for both Play Store and Google Play Services, as well as clearing the Dalvik cache, although that was probably needless. I have also tried recreating and re-syncing my Google account.

I was able to get rid of the error by DOWNGRADING Google Play Services all the way to 6.3.20.B-all [0] 2734767. But this still doesn't work... I'll update the post with more detail.

Maybe try removing your Google account(s) and adding a different one, just as a test.

Matthew, tried as you suggest to use a different Google account, and got a different problem. This time installing an app results in "Authentication is required. You need to sign into your google account", when I am already signed in and even defined a payment source. Clearing Data from Play Store and Services didn't help.

That is incredibly weird.  I'm pretty much out of ideas other than trying to upgrade to a new Android version with a custom ROM, which you may not want to do especially over one issue.

I was able to fix the problem with a suggestion from Brandon Heston, although I am not sure that my situation was exactly like his (see comments).
I fixed the problem by doing the following:

Uninstalled the last 2 apps I installed (Sleep as Android and Hue Disco).
Deleted Data for Google Play Store, Google Play Services, Google Account Manager and Google Services Framework
Rebooted

After this the Google Play Store stopped crashing. However, unlike Brandon's situation, neither of the 2 apps I uninstalled have become unavailable for my version of Android, so I am not sure why this solution worked, but it did.

I just had what seems to be the same problem happen to me a couple hours ago. I think an app I was using suddenly became outdated in the store without a possible version for my phone (s5 running 4.4.2). This app had a subscription tied to it so I'm not sure if that played any role. But I deleted said app and cleared cache and data on Google play store, Google services framework, and Google play services. Seems to work now.

How did you figure out which app to remove?

Well I was also getting an Unfortunately Google Play S has stopped working or something along those lines message continuously. I tried clearing cache and data on everything to no avail. I remember I started getting the notification when using a Map my run app by mapmyfitness (under armour). Then I couldn't load the store for more than 2 seconds. And the message. I uninstalled that app. Then Google play store opened and gave me the option to install and said I still have subscription. I restarted. No more issues. Went to the store after the reboot and no more option to install because

There was no compatible versions for my device and firmware anymore. So I more or less got lucky I suppose.

I didn't Install when it gave me the option after uninstalling. Restarted and that option was gone. So probably an auto update issue with compatibility.

Brandon, you were right! I uninstalled the last app I installed (Sleep as Android), and the original problem went away. Play Store no longer crashing, but still stuck on DF-DLA-15 :(. I'll post that as a separate topic though.


text:
WhatsApp MessageService is always killed shortly after exiting the app
A couple of days ago I noticed that I no longer receive WhatsApp messages until I manually start the app, which is when the pending messages get delivered all at once.
I started my investigation by monitoring the com.whatsapp.messaging.MessageService in the Application Manager.
Here's what it looks like at first, after I exit WhatsApp:

And here's what it looks like a few minutes later:

It looks like the MessageService either quit, or it was terminated. To verify this, I checked with adb. I can see the service at first:
$ adb shell dumpsys activity services | grep wh
  * ServiceRecord{43deec28 u0 com.whatsapp/.messaging.MessageService}
    intent={act=com.whatsapp.messaging.MessageService.START cmp=com.whatsapp/.messaging.MessageService}
    packageName=com.whatsapp
    processName=com.whatsapp
    baseDir=/data/app/com.whatsapp-1.apk
    dataDir=/data/data/com.whatsapp
    app=ProcessRecord{42d19f90 10037:com.whatsapp/u0a10187}

But then this service disappears, even though the main process is still running:
$ adb shell ps | grep wh
u0_a187   10037 215   988084 78996 ffffffff 00000000 S com.whatsapp

The service does not get terminated at the same time. I have seen it killed as early as 6 minutes after exiting WhatsApp, and as late at 11 minutes. But in the vast majority of cases, it is terminated some time on the 8th minute.
I have carefully examined the logcat during the moment of service termination with the following logcat query, which I believe silences only the stuff I don't care about:
adb logcat -v time LightSensor:s LightsService:s  SensorService:s SensorManager:s STATUSBAR-BatteryController:s BatteryService:s HeadsetStateMachine:s android.widget.GridLayout:s MP-Decision:s SignalStrength:s McClient:s McDaemon:s QcrilMsgTunnelSocket:s | grep -v ss_tz_mobicore | grep -v ss_daemon

I was not able to see anything in the logs that would hint at what happened to the service. Did it quit? Did something kill it? How can I find out?
I thought that maybe the service was terminated b/c the OS was low on RAM, but this does not appear to be so. Here's the RAM at the moment of termination:
$ adb shell free -m
             total         used         free       shared      buffers
Mem:          1821         1587          234            0           75
-/+ buffers:               1511          310
Swap:          399          134          265

While working on this issue, I have used Titanium Backup to freeze all apps that might interfere with normal operation of WhatsApp, so these are the apps I froze:

Greenify
Amplify
XPrivacy

I also turned off "Per App Hacking", which is an Xposed Module.
Any ideas on how I can learn more about why MessageService is being terminated?
EDIT 1: Is it possible that MessageService is supposed to get terminated, and that WhatsApp relies on GCM to be notified when there are new messages?

I've been having exactly the same issue as yours. I can also see that the MessageService service is being killed after around 10 minutes. After the service is killed, messages are only received when opening the app. While googling today for this problem, coincidentally found this thread which you had posted just 3 hours ago.
I'm using a new phone on which I installed Cyanogenmod 13. I've already tried to change several settings related to battery usage, memory optimization etc., but to no avail.
I've started using this phone 2 days ago and the whatsapp issue has been happening since then. Tomorrow I'll try to uninstall and reinstall whatsapp from the Play Store, since this one was restored from a Titanium Backup backup. I saw in a forum someone who resolved a similar issue by doing that... he also had restored from a TiBu backup and was having such problem.
By the way, your theory about GCM seems to point to the right direction - in my wife's phone the MessageService service is also killed after around 10 minutes, however, she doesn't have any delays in receiving whatsapp messages - so maybe it indeed relies on GCM for that.
Let me know if you make any progress on the investigation or come to a solution. Let me also know if I can help you with anything else.

This doesn't answer the original question.

@sickgemini: Although it doesn't answer the question, knowing that MessageService is also stopped after 10 minutes on a working phone is very valuable to me. It tells me that the service is stopped by design, rather than being terminated by the OS. I am removing the downvote.


text:
Authy: Is it possible to gain access via backed-up filesystem?
If a user makes a complete backup of an android file system, is it possible to subsequently install authy on a different device, but authenticate as the original identity?

Copying the contents of /data/data/com.authy.authy from one phone to the other seems to accomplish this.


text:
access xperia z1 compact with broken screen?
My Xperia Z1 compact runs CM12. Unfortunately it has fallen on its bottom left corner and the touch screen is completely unresponsive. The cost of a replacement screen is more than a new phone with similar specs so I bought a new phone.
Now I am trying to get access to some files that are on the internal SD card (loads of contacts that I don't want to re-type, but also the latest photos).
The phone has Cyanogen recovery on it so I booted into that, and on my computer ran adb:
# adb version
Android Debug Bridge version 1.0.31

but then
# adb devices
List of devices attached
CB5A24NPRD      offline

which I cannot seem to change. Because I cannot use the touch screen, the only way to control the phone is in recovery mode with the volume and on/off keys. Is the best thing to do just to dismantle it and get the internal SD card? If it is a physical card then that may be the best way to go?

Only the touchscreen is dead or is the display dead too?

The display works -- I still see the keypad for unlocking my SIM; the problem is the touch screen. I think the crack from left to right makes localisation impossible.

You should try connecting a mouse via OTG. Once you enable USB debugging, photos and files can be pulled via adb. For contacts you will have to export to Sdcard before pulling.

You should try connecting a mouse via OTG. Once you enable USB debugging, photos and files can be pulled via adb. For contacts you will have to export to Sdcard before pulling.

Finally had time to try out the OTG solution which worked straight away! After setting up the phone I could pull it all to the computer with ADB.


text:
adb 1.0.31 fails to detect device
I noticed a strange behaviour. I am fixing different bug, so I am trying different version of adb one by one on my phone.
I tried 1.0.26, 1.0.29, 1.0.31, 1.0.32, 1.0.36, all except for 1.0.31 are able to detect my device.
my phone is
MI4LTE
Android
6.0.1 MMB29M
and I am using MIUI
MIUI 8.1 | Stable 8.1.3.0(MXDCNDI)
Anyone has an idea what could possibly cuase that?

Problem was caused by phone not set in USB charging mode in settings
Settings > Additional settings > Developer options > Select USB Configurations > Charging only
This made 1.0.31 behave just like remaining versions of ADB mentioned in the question.


text:
How to get ALPHA symbol using Google keyboard?
I want to type Symbol of aplha but I couldn't figure out how to get it , however I can type ß(Beta). But not alpha.

Why not just copy it from here, and paste when you need to when you're typing

@Cup of Java Then I have to do each time , Which is pain you know

realistically, how often are you going to use the α symbol?

@Cup of Java You got the point but still...

IIRC, what you're typing is not Greek 'beta' at all which should look like [β]. What you actually typed may be German 'ss'. LOL.

@iBug Lol oh ok I didn't knew that anyway doing copy paste now

If you have superuser(root) access, install xposed framework. Search for an xposed module called 'Google Keyboard Custom Smilies' (GKCS) and install it. Open GKCS app and add 'α' symbol in it. You can use your own labels for inputs.

Any other way for Non-rooted device?

@ShubhamWagh Be simple. Grab another IME.

Use greek language.
Tap and hold space button for quick accsess.


text:
ADB without PC is it possible?
Currently I don't have PC but I need to execute some commands via ADB. Is there any way to access ADB from other phone or anyhow without PC?

Install a terminal emulator

@beeshyams I need to execute "sh /data/data/me.piebridge.brevent/brevent.sh" to make brevent to work without root. Thanks for the thread but it won't work to me since neither of my phones support OTG, make an answer if you want.

@esQmo_ It won't work since command requires root or ADB to execute.

@beeshyams I lack root on this device, that's biggest pull-back.

Limited commands for adb and fastboot are possible according to this XDA post, that too on ARM architecture
Requirements :-

Rooted android Tablet / Phone.
OTG cable [ Make sure that your device supports OTG. (If not search your device's thread for OTG )]
A root browser ( eg:- Root Explorer, ES file explorer)
Terminal emulator

As indicated by OP in comments, this solution doesn't help as there is no OTG support nor is device rooted
Without root, to my limited knowledge, it is not possible

authors: Једноруки Крстивоје


text:
Saving image from gmail app
I have downloaded some images from an email using my gmail app . I tried to find it in my gallery and also in my storage but i couldn't find it either in my gallery or in my storage

I've cleaned up the remaining comments here, glad to see it was resolved and the answer posted.  In the future, please use [chat] for extended discussion.

In your Gmail app go to settings, then click on your your target email address (where you want to get image attachments downloaded) , then untick the option which says "Auto download attachment to recent messages via Wi-Fi" try again to get your image.
It seems attachment downloads are restricted to wi-fi (default) but option is not clear at all as it seems to imlply a different thing. So disabling this option implies both data and wi-fi are considered (although the option is a bit misleading) It however fixed the issue.
Edit
Downloaded images are saved in downloads folder of sdcard or here /storage/emulated/0/Download
credits: beeshyams


text:
Prevent music players from auto play on bluetooth connect
Whenever I connect my android device with a bluetooth device, it automatically starts spotify and starts playing.
As far as I know this also happens to other users/players (according to google)
How can I prevent this (without signing out of spotify)?
Android: 6.0.1
Spotify Version: 6.2.0.1015

@beeshyams yes it is, but the solution should also cover unrooted devices, as this is not only a concern to me.

@beeshyams How would a tasker solution look like? You can add it as an answer here for rooted devices and if someone would come up with a non-root solution, he could edit your answer.

It's not mine. I don't know Tasker so will not post that solution. But here it is

My solution is using Macrodroid which is another automation app. You can test it and let me know if it works- I can't test since I don't use Spotify. Trigger: Bluetooth Event > device connected > any device Action: Kill app > Spotify (requires root ). You can test this in 5 minutes

@beeshyams I like the link you posted! AFAICT it doesnt need root (since you can do adb commands via usb debugging) only need to enable Tasker accessibility service, good research though!

@beeshyams unfortunately I don't have Spotify installed too, perhaps I could have tried it but at the moment I can't replicate the autoplay with my music apps :( thanks though

Let us continue this discussion in chat.

Background
Major part of this guide was extracted here: How to Disable Bluetooth Automatic Playback on any Android Phone
The point of this guide isn't to disable Bluetooth music entirely, otherwise the latter can easily be achieved by:
Disable Bluetooth Music : Settings >> Bluetooth >> Your device(Car) >> Settings  then uncheck audio support.
..and this simply destroys the whole purpose of the guide.
 It is important to know that autoplay is a feature of many Bluetooth devices, despite the fact people do see this "feature" as a problem though, which is the original reason the original author wrote the guide.

Understanding Bluetooth Autoplay on Android

What essentially happens when you connect a Bluetooth device that sends an autoplay command is that this command is seen as a KeyEvent for toggle play/pause in Android.
Applications with a MediaButtonReceiver broadcast receiver can then react to this Media Button event.
Android keeps track of the last application that requests to receive Media Button events.

Any new media application can take over to listen to Media Button key
  events by calling setMediaButtonReceiver in AudioManager, and that
  application will handle Media Button key events until another
  application requests control.

You can actually see which application is currently set to respond to these key events by entering the following ADB command:
adb shell settings get secure media_button_receiver
On the author’s device, this command yielded the following output:
com.google.android.music/com.google.android.music.playback.MediaButtonIntentReceiver

This is the broadcast receiver set up by Google Play Music to respond
  to Media Button key events. So if I plug in my Bluetooth device, my
  phone will automatically start playback in Google Play Music.

Disabling Bluetooth Autoplay with Tasker
Profile (or Trigger)

Goto Profiles Tab and click the "+"
Event >> State >> Net >> BT Connected
Tap back to exit from this window

Task
You will notice as soon as you exit, you will be prompted to link this to a Task

Scroll all the way up the Task list select "New Task + "
You can just keep it anonymous or give it a name
Click "+" to add new Action
Media >> Media Button Events >> Grab
Tap back to exit from this task

AFAIK root is not necessary for this task

Once you’re done, Tasker should now automatically set itself as the Media Button Receiver in Android upon connection to your selected Bluetooth devices. This way, the play/pause action that is sent will not be received by any of your media applications, but instead by Tasker
Unfortunately I couldn’t get Spotify or Soundcloud music application to replicate the issue. However, I retested this feature using a PC with the remote audio service (Bluetooth module on my PC supports that) to test the bluetooth autoplay feature.
Tests done

Enabled Bluetooth audio service (to use PC speakers to listen to remote audio).
Open two different music apps on android and played music and play
Created a “media button grab” in Tasker to handle Media Button key events.
Retested (2) with Tasker running the previously created task.

Results

On test (2) the audio output was transferred to PC speakers indicating that the autoplay feature was still active.
After performing test (4), the audio sound output came from android and was not transferred to PC speakers. Which essentially solves the issue.

Alternatively..
Head to playstore and get Bluetooth connect & Play

You can tell it which app should play for each bluetooth device (or to NOT play on a given BT device)
Acknowledgements

Original author: Mishaal Rahman
Beeshyams

Install a paying app...right... is there an actual solution?

To prevent Bluetooth playback, create a Tasker profile and associated task. For the task, choose "Music Play." I have mine set to play a 1 second clip of silence such as this. This grabs the playback and does not automatically continue to the prior app playing media.
I tested this on Android 13 (LineageOS 20) with a Pixel 4a.
I tried the solution suggesting to grab playback with Tasker or the media_button_receiver option (both rooted and not), but neither worked.

Check your Bixby routines is you have a Samsung.  It might be set to turn on music as soon as Bluetooth is connected.

If you are been annoyed by your smart android phone auto starting the music when you start your car. Here is the solution I found snooping around:
Open up your Google Chrome browser on he phone, click on the right upper corner bottom, click on settings, advance, site settings, media and turn off auto play. Bingo.
Now you can play any media when you want.
JT.


text:
Hibernate apps, but have them wake up periodically for a short time
Many of us Android users have probably already heard of Greenify – an app that can automatically hibernate apps as soon as you turn off the screen. That even works while keeping their GCM functionality working – so whenever a cloud message for them comes in, they get awake again.
Unfortunately, that wakeup only works with GCM. Now I want to hibernate a non-GCM app, but have it awaken in intervalls (eg. de-hibernate it all 30 min for 1 min, then auto-hibernate it again).
Is this possible – and if so, how?
My device is rooted, the XPosed framework is installed, and tasker available as well – so solutions involving one or more of those criteria are perfectly welcome as well.

Oh well, oh my … question almost included the answer. Still needs some testing (I've just set it up now), using tasker which has a Greenify plugin:

Condition:

Event › Display › Display Off

Task:

Task › Wait: 20 s (just in case)
Task › Anchor: (Name, optional step)
Plugin › Greenify › Hibernate: Pick the app
Task › Wait: 30 min (or however long you want to have the app hibernated)
Plugin › Greenify › Wakeup: Pick the app again¹
Task › Goto: Action Number, 2

Exit Task:

Plugin › Greenify › Wakeup: Pick the app again¹

Note: That's how I would set it up. Had to skip the exit task as Tasker won't let me add one. So that's the crux here: I have to trust Tasker to restore the "previous state" correctly. If that doesn't work, I'll have to create a second profile for Event › Display: Display On (which would, being an EVENT, fire when the display will be turned on – it's not a state) and have a single task to do what otherwise the exit task would do.
Note 2: In order for this to work, you need to add the "target app" to Greenify's hibernation list first (i.e. tell Greenify it should hibernate it when turning the display off). If you don't do that, it won't ever be hibernated at all.

¹ if your app doesn't react on the wake-up command, see Xavier's answer for an alternative shell command to try

@beeshyams A bug in Conversations (the "Jabber" messenger), which I use the F-Droid version of (comes without GCM). Often turns up to be the top consumer (50% and more). Before I started using that, I had a battery time of ~5 days. With it, it's 2..3 days when I'm lucky. I don't really need to react immediately if someone pings me – so I want to have it hibernated, and only check every 30min if there's something new – for which I grant it 3min currently. As I wrote, I'm not yet sure how it works – should be able to tell in a few days (will accept the answer if it does).

@Izzy Good workaround I was in the same situation where I wanted to wake non GCM apps after hibernating them with Greenify plugin, but some wouldn't respond to the "wake up" command provided by Greenify plugin.. I will short put my workaround as answer :)

My candidate doesn't seem to respond to the "Freeze!" command :( Was on 78% battery usage when I killed it. Crazy enough, 2h later I found Hangouts running (accounting for another 12%), which I don't use at all – I'm totally confused now. Killed and disabled it Grmpf!

I found out some of the hibernated apps wouldn't respond to the Greenify Wake command, instead I used the start service command to "wake" the target application (without opening its UI)
Profile  Context

Event › Display › Display Off

Task

Click "+" to add new Action
Task › Wait: any preset e.g 20s (like above)
Task › Anchor: (Name, optional step)
Plugin › Greenify › Hibernate: Pick the app
Task › Wait: 30 min (or however long you want to have the app hibernated)
Code >> Run Shell [ Command (am startservice -n com.package.name/.service name
, Tick "Use Root"]
NB: service name is just a declared service in Android manifest that starts an application without opening UI i.e in background, there are also tools to use if you're not sure of the service name)
Tap back to exit from this task
Click "+" to add another action
Task >> Goto [Action Number, 2 (anchor task)]
Like @Izzy said you can rely on Tasker 'previous state' to reset the config, because adding an exit task is not probable

My workaround simply involves starting the service of the hibernated app (IMO=waking the app) because sometimes the app won't wake up using the Greenify wake option as I previously encountered :)

Mmm I doubt if it needs donation pack,  in the meantime have you checked if secure lock is possibly interefering with greenify functionality? Found this here: Facing issues while using plugins such as greenify, autoshortcut etc

Donation pack not needed for this functionality, correct. Trick was something else – see "Note 2" in my (updated) answer: the app must be in Greenify's "Todo List" ;)

Yes and no. Without that restriction you've had the chance to hibernate apps under certain conditions only (e.g. only if no WiFi available, only if the battery is below a certain threshold, etc.). With this restriction, that becomes harder. But of course it's good to know this restriction exists – or you'd wonder, like me, why the profile is not working ;)


text:
Retrieving app messages
Is there a way to (offline)  retrieve app messages (messages that  appear with on the top right on the home screen with a small icon of the app)
Without opening the app itself? (or when the app doesn't store these messages)
Or is there an app that I can install that can remember these messages?
I am using a Dtek 50 android 6.0

Notification History records  notifications, toasts, Dialog message and many more.
You can configure it store these either for 30 days or 300 Notifications and view off line
From app description:

(click image for larger variant)

Android still (far as I know until 8) has an internal notification log. You have to access it via Nova Launcher / Activities / Settings / Notification Log. I've detailed this in a post below.

Use Nova Launcher, then once installed, add a "widget" to your Nova Launcher home screen for the "Notification Log". Proof this is possible on Android 8 Oreo:

Install Nova Launcher and run it
Long press on your Nova Launcher home screen
Press and hold to add an ACTIVITIES widget (should be near the top)
From there choose a Settings widget
Choose Notification Log
Select your new Notification Log to access the Android Notification Log.

I don't know why Google hid the notification log widget and judging from the huge number of apps in the Play store that offer to record notifications for you, it really is a sought after feature. Thanks to Nova Launcher for making such a great app!
Originally seen in a comment from Javier P on this page. May the gods bless his life.

+1. At the time of posting my answer, I wasn't aware of this and later saw that it works on Pie too. Good to have alternatives for users


text:
Google Keyboard takes a few seconds to enable autocorrect after the latest update. How do I fix this?
In the latest version of Google Keyboard (6.6.22) I've noticed that for some reason it takes 5-10 seconds for autocorrect to start working after the keyboard is loaded. I've disabled multi language typing but it didn't help.
Is there a setting I can change to make the keyboard load test dictionary fast again? Or perhaps it's a known bug?

The issue was resolved by clearing the cache of Google Keyboard.


text:
Is a PIN reducing the security of a fingerprint based encryption?
Many smartphones and programs are using fingerprint's to secure the phone or encrypt data. In many cases, those programs want a PIN as backup authentification method.
A PIN just got 10000 possible combinations, while a fingerprint got many more. So an encryption isn't safe if there is a backup pin, is it?
The same question for a phone lock-screen: If there's a 4-digit PIN, people could just bruteforce this pin instead of bruteforcing million of fingerprints, couldn't they?

Welcome to the community ☺

A backup plan is always necessary in case the fingerprint sensor doesn't recognize fingerprints or gets broken or something that it doesn't function as expected
Coming to app locking system, it totally depends on the app lock system if it has limit of trying PINS then you should be safe but if it doesn't YES it can be bruteforced if there's no limit on no. of wrong attempts
Coming to Androids PIN lock feature, it doesn't have limit of only 4 digit PINS so you can make it more secure by making large complex PIN
Assuming 4 digit PIN, AFAIK Android wouldn't allow you to attempt 10000 wrong PINS infact it will allow only few and then will lock up itself

A PIN just got 10000 possible combinations, while a fingerprint got many more.
If there's a 4-digit PIN, people could just bruteforce this pin instead of bruteforcing million of fingerprints, couldn't they?
Biometric lock is weak, hence insecure - it's only for user's convenience.
PIN can be generated from set of 10 numbers - it can be with or w/o repetition.
Password (on factory Android) can be generated from ASCII charset, including numbers, without control chars - c < 32 || c > 127, thus having 94 printable chars.
Again, minimum lock screen length is 4 && maximum lock screen length is 16 (on factory Android).
Also, default password policy is PASSWORD_POLICY_UNSPECIFIED (on factory Android).
With that said, factory (AOSP) Android has low security margin; it is only on user to define password with complex quality thus to mitigate online attacks (bruteforce).
Off course, you can change policies with DPM (DevicePolicyManager) application or build custom ROM.
Regarding your q about bruteforcing, I suggest to read this


text:
"Change your phone number?" notification
Since I got my new Google Pixel, I've received a "Change your phone number?" notification upon each boot up. Nothing I've done has remedied the issue...
Here's what I've tried so far:

Selected the notification, provided my credentials, updated my phone number (which has been the same for years), and applied the changes.
Rebooted lots of times.
Wiped the cache for Google Play and Google Play Services.
Removed my account's recovery phone number, then re-added my phone number.
Removed my Google account from the phone, then added it again.

Short of factory resetting the device, I'm not sure what else to try. This issue has been going on for 8 days now. It's rather frustrating.
Here's a screenshot of the issue:

Install [this app] (https://play.google.com/store/apps/details?id=com.evanhe.nhfree) to see which app is responsible for this. Maybe that will help in next steps

@beeshyams Downloaded the app and rebooted. The notification was created by Google Play Services.

IDK what's to be done since you don't want to reset. Was hoping it would be an errant app that can be uninstalled

You can try uninstalling the updates of Google play store, deleting cache and data of it and updating again. Sometimes it fixes things. You have cleared cache but not data as per Question

Thought I'd follow up on this. After trying just about everything, I caved and factory reset my phone. The notification hasn't appeared since.

This may not be the ultimate 'answer' to your question, but I too received a similar notification from Google Play services just yesterday:
As you can see, mine is slightly different in that it was asking for me to "add" my "new" number as opposed to change it. The thing is, my phone is not new (2 year old Nexus 5X, most recently fully reset more than 9 months ago), nor are any of my account/numbers, and I have not done anything recently in the way of adding phone numbers (cellular or Google Voice) or recently connecting Google accounts to the device.
At first blush the message I received just looks like Google attempting to get people to fill in the phone number field on all Google accounts, but that doesn't make sense in my case as the account referenced does have a phone number configured for security purposes. Even if the specific field they care about is empty I don't know why they would have worded the message as such, making it sound like they are somehow aware of a "new" number added to my phone, somewhere. It really was a strange notification to receive.
So with that said, I wonder if your similar notification on your Pixel is a symptom of a larger issue Google is having on their back-end systems. So far I have only received my bizarre notification once, it didn't coincide with a restart of the phone, and restarting the phone now doesn't seem to trigger it. So again, this may not be the ultimate answer to your specific symptom, but it seems like Google has gone notification happy with Google Play services soliciting phone number input.

I had this problem here is what I did
went to apps > google play services > force stop > storage > clean all data there>
now disable google play services and erase all data
now go again apps > play store > force stop > storage> clean all data there
Restart phone
now google play store will ask to update google play services > update > restart
done notification didn't appear when restarted my phone anymore

All those ">" on one line makes it look like you're going very, very deep into a menu or something. This answer needs something to separate actions. Perhaps more punctuation or line returns.

RESOLVED: I was getting the same message on my phone so I went into my Google account with my PC and found that one of my recovery email addresses was invalid (I had closed one of the accounts).


text:
Can I grant permanent access to external storage to an app in Nougat?
I'm using OnePlus 5 running stock 7.1.1.
I use the OTG function to transfer file between my phone and my flash drive very often, and my preferred file manager is Root Explorer. Every time I try to copy stuff to flash drive, I must first grant it access.
Can I permanently grant Root Explorer access to external storage? I don't mind messing around with system configuration files (like packages.xml).

Manually granting permission
For rooted devices, there is a way to inject a specific permission inside the /data/system/packages.xml file, which details any and all installed apps, alongside their signatures and permissions.
The permission mentioned above is <item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />, which is usually granted to system apps only. This line must be added under the <perms> node of the package name one wishes to grant permanent access to the external storage, be it an SD card or a drive attached via OTG.
For Android to acknowledge the new permission, a reboot is needed.
Revoking permission
To revoke the abovementioned permission, one just needs to remove the <item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" /> line they themselves added.
Automated alternatives
If one does not want to manually edit packages.xml but has Xposed, it is possible to achieve a similar result by using the XInternalSD module. Upon activating it, enter its settings and disable any checkbox but the one next to Full access to external SD card.
This, depending on the Android version in use, is able to grant read-write access to external media. It is tested and running up to Nougat 7.1.2. This method is not granular, hence any app will be able to access any external media.
I am not affiliated to either XInternalSD, or to its developer.

I agree for sure.

I edited the packages.xml for an app called Termux, as per your suggestion but I still can't write to the  External SD card from the app. I am not really familiar with Xposed and would rather not go down that road. Any other suggestions?


text:
How can I edit the URL of a home screen bookmark?
I want to have a bookmark shortcut on my Home screen to launch a web app I use regularly. The only way I found to achieve this is using the Add to Home screen from the Chrome browser menu when I'm on the site. However, this does not let me edit the actual URL the bookmark will point to.
This is a problem because said web app automatically appends the current date to the end of the URL when it's loaded. When I add the shortcut to the Home screen, the link will then actually open the app to display data from the day on which I created the shortcut. I'll always have to open the date picker and navigate to the current date to start using the app.
I'd like to edit the Home screen bookmark shortcut's URL to remove the date added to its end, so it always opens to the current day. Can I achieve this without third-party software?
I'm using an unrooted Sony Xperia Z5 Compact running Android 6.0.1.

Some sources say to create a standard bookmark in Chrome, where the URL can be edited, then long-press it in the bookmarks manager and choose to add it to the home screen from the context menu. This context menu entry does not appear to exist anymore in current versions of Chrome.
Some sources say to look for a Bookmarks widget that allows to choose a Chrome bookmark to display. This widget doesn't appear to exist anymore in Android 6. The only bookmarks widget I have displays the entire bookmarks folder.
The website in question loads too quickly for me to be able to cancel before the URL is modified. I tried many times.

Why don't you try this? Install Tasker, setup a 1x1 widget on a home screen and in the task choose Net -> Browse URL -> your URL. Done! MacroDroid can be used as an alternative to Tasker.

I havent been able to find an intuitive way to modify a desktop shortcut's URL, but I have found a workaround for the problem.

Put your phone in airplane mode and disable WiFi to turn off all internet access
Open the Chrome browser
Type in the URL you are trying to set a shortcut for
Press enter and the browser will alert you that you are currently in an offline status
On Chrome, click the settings (hamburger) button
select add to desktop

You will now have a shortcut on your desktop that refelcts the URL that you have just entered into Chrome
Turn off airplane mode and you're golden.
This applies to Android Marshmallow 6.x as well as Nougat 7.x. It may also apply to older versions as well

Best part? Not even working for me. It changes in airplane mode too.

Nice hack - I added a maps URL query this way.

Works but PWA display rules are not respected to me. It opens the correct URL but in classic Chrome (with the address bar and stuff). When doing "classic way" I have the wrong URL, but it's displayed full page.

Still works on Android 14 :-D

Doesn't work for gmail. Can't get the desktop version to show up reliably.  It seems to redirect to the mobile version.  :v(

This was super helpful! Till seeing this, I couldn't figure out how to add Substack URLs as home screen links because those pages only had the Install App option (and I don't want to install the Substack app).

I really don't see the point of this. How is this different from deleting the original shortcut, going to the wepage you want a shortcut to on your Android Homepage, tapping the three-dot menu, and tapping on "Add to Homescreen"? I mean, except for adding several unnecessary (and apparently problematic) steps.

Inspired by the airplane mode by @axelderhund, the following is my way.
Add any URL you like to home screen
Turn on airplane mode, type in your desired URL in your browser, and add to home screen.
In this way no redirection happens and the url is intact.
Check (original) URL of a home screen bookmark
Turn on airplane mode, which prevents redirection. Then connect your phone with your computer via a USB cable. Run browser on the computer and turn on USB debugging. The USB debugging page shows the URL of opened pages on your phone.

Okay, this was my solution for Firefox haha:
Search online for a link shortener. (Edit: The one I linked previously is no longer active.)
Use it to create a link, then press and hold on the link to open a drop down and create a bookmark from that. Then, you can press and hold that bookmark and click "Add Page Shortcut".

Now that I did this, I think another solution would be to bookmark the wrong URL and then just edit the bookmark and repeat the "Add Page Shortcut" action above.

easyhyperlinks.com seems to be down. But it should work with any link shortener. Just make sure to access and add the link to the home screen before saving the shortened URL.

This answer was the only method that allowed me to create an Android desktop icon that opened up Google Chrome on https://outlook.office365.com/mail/ link. I used the tiny URL shortener in order to do this as otherwise Outlook .com blocks the Google Chrome browser from showing the Add to Home screen menu entry. Placing the phone in airplane mode is a requirement. My current phone is a Samsung Galaxy Note 10 lite, unrooted.

Unfortunately I know of no way to edit an Android Homepage/Desktop Web shortcut. And neither do any of the people who provided answers.
The easiest and fastest way to achieve what you want is to delete the original shortcut, and create a new one the way you did before.
If you need more specific instrunctions:

Long-Press the current shortcut
Tap Delete
Open Chrome
Go to the webpage you want a shortcut to
Tap the three-dot menu
Tap "Add to Homescreen"

Then you can drag it to wherever you want it.
No need to for Airplane Mode, or anything else.
Pretty simple. Very straightforward.

This doesn't help the case when the final URL is a result of redirection, while the user wants to link to the source URL, which is what this question asks.


text:
Why is my Galaxy S4 still not appearing as a device in Mac OS X
I am trying to solve the problem of having an empty list of devices when running adb devices. Why is it not appearing?
I have tried the following to no avail:

Installed Kies and ran Tools > Install driver; then restarted
Turned off the Mac OS X firewall in
run sudo adb devices instead of just adb devices
Read the user manual from Samsung, which simply refers me to use Kies
Attach S4 to a different macbook in case the USB input is faulty
Try both different USB inputs in my Macbook Pro

The output I see after doing a fresh restart and plugging in the S4:
./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

(with nothing more shown underneath)
Also, even after installing the drivers using Kies, the device does not appear there.
I am running OS X 10.9 on a Macbook Pro. The phone lights up and does start to charge when it is plugged in to any of the 2 USB ports on my Macbook.
What else can I try to have my brand new S4 appear in this device list?
EDIT It seems according to this thread (http://forums.androidcentral.com/samsung-galaxy-s4/282817-pc-cant-detect-galaxy-s4.html) that it may just be a faulty cable. I'm currently using the cable that came with the S4. I'll try other cables.

Answer: I was using the cable that Samsung provided with the phone
Solution: Go get a USB<>MiniUSB cable that was provided with a digital SLR a few years back and use that instead. The S4 now appears in the adb output and in Kies just fine.
<sarcasm>Thankyou Samsung</sarcasm>

Same issue and same resolution for a brand new Samsung Galaxy S7 (in addition to enabling Developer Options and USB Debugging).

If using a better cable doesn't work be sure to enable the USB debugging feature under Developer options > Debugging

Enable USB Debugging mode solve the problem! For those who don't know how to enable it (it's very hidden on Android 4.3 onward), see this.

This worked for me: try unlock screen after phone is connected. Screen lock seems to block access to the device from USB as well it seems.


text:
unable to upload doc files in android latest version
I am not able to upload  .doc files on my android mobile.I have Kingston software installed so whenever I use the upload button from the webpage it just displays my gallery, camera, voice and video recorder. It does not display the file browser so that I can select the file from my file system.

Please consider that we don't all have exactly the same software as you, so we don't necessarily know what this "Kingston software" is you mention, nor what webpage you're talking about. To get better answers, [edit] your question to describe the problem more fully, and include your phone and Android version.

This is a genuine question. I just did a factory reset on my Android 4.2.2 and there is no Kingston software. But when I try to attach a file in Gmail, I am not given an option to choose a file from the filesystem. Even trying to attach a file from Google Drive doesnt work

By installing androZip my problem is getting resolved :)

I don't know the software you're using but I'd recommend looking into Airdroid, it installs a small application on your phone and lets you manage it from a web interface. After starting the service you can copy all data in both directions.

And how does that help uploading files to a website? Airdroid is to remotely manage your Android device, which is a completely different task.

"Kingston" is similar to MS Office where you can edit/modify doc, xl, pdf and view presentations. I have read similar issues I am hearing about EStrong File Explorer and androZip. Are they helpful software ? can resolve my issue ??.

that might be right Izzy and is now clear when I know that Kingston seems to be some kind of office suite.
@RizwanSA So what "webpage" are you trying to upload your files to?


text:
Fresh Cyanogenmod install, location doesn't work
Yesterday I installed Cyanogenmod using the one click install on my Nexus 4.
There is a little problem though: when using location in the battery saving mode, when it only uses cell and wifi signals to guess your position, it simply can't locate. Using GPS is fine, it locks position within seconds, but it's too battery hungry, kills my phone in a few hours.
Is this a known thing? Can it be fixed?
EDIT: After 2 days, location in power saving mode comes and goes.

What version of Cyanogenmod do you have? And do you have the Google apps (Gmail etc.)?

Latest One CLick installer version (11.0-InstallerXNPQ02R). I have all Google apps installed, the installer did it for me.

If your using cyanogenmod 11, then the issues your having are very common. Its still under development so there are things that don't work. Some of the times something works, but then is broken again in the next release. Right now your best option would be to either flash cyanogenmod 10.2 or just bear with it and wait for a release that fixes the issue.


text:
Samsung Galaxy S2 drops carrier network
My SGS2 is dropping it's network connection multiple times a day without any notification.  The signal bars disappear and it just says NO SERVICE/VODAFONE NZ. No data, no 3G, no 2G, nothing...
I was previously on Gingerbread 2.3.6 and was hoping that CyanogenMod would fix the issue.  I flashed it to CM 10.2 but the same issue remains.  This makes me think it is a hardware issue and not a software issue, however it did not wipe my internal SD card - could there be settings in there that are causing this?
It seems to really love the ground, so I'm wondering if it has just been dropped one to many times and cracked some solder connections somewhere internally?
UDPATE
Installed the GetRIL tool and it said the stock RIL was unknown.
I installed the first RIL on there.  It said that it would backup the stock RIL.  The one I installed didn't work so I installed another one.  That didn't work either.  So I tried to restore the stock RIL but then I read in the FAQ it only restores the last one installed.
So it restored the broken RIL.  And now I have no network and can't figure out how to get the stock one back.  Yay.
Here's the stock details:
RIL: Unknown - 163ecafa01912637fe344ec1f8264d70
Baseband: I9100XXKE7

Anyone know how I can get the stock RIL back?
As an aside: the battery lasts sooooo long without the carrier network
UPDATE
Reflashed with CyanogenMod so I got my stock RIL back.  Still monitoring the network drops.

I assume the phone is rooted. Search for baseband applicable to your device model, country etc. Try downloading an app called GetRIL, which will show you the list of applicable RIL which matches the baseband applicable to your device. This fixed it for me based on my searches on xda-developers. Hope it fixes for you too.

Yep, installed GetRIL then I broke it by installing too many RILs (only backs up last installed RIL) so I lost the stock RIL. :(  Updated question.

I think GetRIL shows you compatible RILs, from which you can choose. Also, you can search for RIL compatible for your phone, country etc. There used to be a list where you could see baseband version applicable to your phone, country etc.

Yea it said my ~~baseband~~ RIL was unknown, but had a recommended one which I tried - if I had hit restore straight after seeing that one didn't work I would be fine.  Luckily I had sent the report to the GetRIL developer so I know the details for my stock RIL but just have no idea how to get my stock RIL back.

Created another question for this specific issue: http://android.stackexchange.com/questions/61768/manually-replace-ril

I have had the exact same problem.  CyanogenMod SGS2, baseband I9100XXKE7, checksum 163ecafa01912637fe344ec1f8264d70.  The only difference is I'm with Optus in Australia.
After extensive research, the solution I found was simply a matter of identifying an appropriate Modem+RIL (Radio Interface Layer) to install.  I'm still looking for an appropriate one for me, although I9100XXLS9 has stopped the dropouts, it won't let me make calls.
Unfortunately it seems the best Modem+RIL combo is very dependent on your carrier+phone combo.  I found a discussion about various RILs to use for SGS2 in New Zealand.  You may find what you're looking for there.  I've seen people discussing I9100JJLS2, I9100XXLS8 and I9100PBVLP7 as good modems.
If you look at your other question (How to manually replace ones RIL) you'll see it's pretty quick and easy to flip around between different RILs when you know what you're doing.  Give them a try and see how you go.

After a day of testing, I've discovered I can't make calls on I9100XXLS9, although it's fixed my other problems.  Sorry if that steered you wrong at all, but the rest of my answer should be good.  I'll let you know if I find out more.

This is a warning only for S2 i9100 owners, reading this question after seeing carrier drop in their phone. This thread suggests using GetRil. As far as I understand carrier drop issue, RIL depends on the firmware installed. What is to be changed is the modem/baseband. Now, before you try that out,

*#1234# in your s2 i9100. If the response contains "Phone: Unknown", there is hardware fault and chip RFIC(U100) will need to be replaced as in this link
Other wise, your phone don't have hardware fault. Feel easy. Before you proceed with rest of steps, I suggest, you take it to Samsung Service and they will easily fix it for you. The issue is only software now and could be fixed easily by Samsung. If you try too many things, it could end up affecting hardware as in Step(1) and then that will need chip level servicing which might not be performed by Samsung service in your locality.
Ok. You are willing to take the risk. Now check your baseband version in About->device. In my case, carrier drop was accompanied with baseband unknown. If your baseband is known - a tip, which I haven't tried out is to, first flash the stock firmware from sammobile.com and try flashing different modems/baseband. Think of modems/baseband as like PC drivers. Don't change RIL. It comes with firmware. Also before proceeding with step(3), take a backup of your EFS folder( with apps mentioned in step(5) ) if your baseband is known.
If your baseband is unknown, check if your IMEI is unknown/null.
The baseband/IMEI unknown is result of a corrupted EFS folder. There are mobile apps like GSII repair, kTool( for rooted phones) in play store which will restore your EFS folder. Also there is desktop based EFS Professional ( for rooted phones ) which again will restore EFS folder. They work some times. Some times they don't. They all depend on a good EFS folder backup. If you have an EFS backup from a good phone of exact model/firmware, you can try restoring it.
If Step(5) didn't help, there is also a SRS remote unlock client which has steps for first restoring baseband and then flashing IMEI. You need some credits to use the software though.

Suggestion: You might feel you are geek and could fix this. You might feel like this will be great experience fixing this phone. I felt the same. But unless you are very sure of what you do, please proceed to Samsung service.

I would try to flash the device to stock rom first. This should install the updated drivers. Latest version of SGS2 official rom is 4.1.2 .
http://xperiahtcrootingrom.com/stock-rom-for-galaxy-s2-i9100-official-firmware-variants/

I doubt that would be any help. OP was on stock before, and had the very same issues. The approach recommended by shahkalpesh in his comment sounds much more promising, as problems in the baseband/RIL are the most likely case with the problem existing on different ROMs.


text:
Xperia M4 Aqua loop-crashes infinitely when trying to connect to my wifi network
This morning I woke up and dropped my xperia down to the floor. When I would connect to my wifi network, my xperia would loop-crash infinitely. My xperia runs on Marshmallow (6.0.1)
To fix this situation, I used Xperia PC Companion to repair and reset it. Yet, any time I would connect to my wifi, my xperia would loop-crash infinitely.
The situation became quite irrecoverable applicatively.

Dropping it to the floor may have broken somthing inside the phone, this is definitely an hardware problem. You should take it to a repair shop.

Intuitively, I'd think dropping the xperia might have unconnected some hardware inside, most likely hardware linked to the wifi.
I watched the following videos to get more knowledge about what is inside that sealed water resistant phone.

https://www.youtube.com/results?search_query=xperia+m4+disassembly
https://www.youtube.com/watch?v=aIvllLIefxcac
https://www.youtube.com/watch?v=e-QRcGrUK8M

From those videos, I planned I'd open my phone with an airdryer and small screw drivers. It's more sketch than what is suggested in the videos, but the phone is 2 years old already and I don't plan on keeping it many years longer.
So, I opened the phone and it was a scary experience. Hopefully, I managed not to screw up much of the glue setup. Like in the videos, I disassembled the battery and the bottom part of the phone in order to get to unplug and replug several components to make sure they are properly plugged.
I put the cover back on the phone and it sticked ok... From now on, I won't put it into water anymore, I can live with that.
Booted it back up and set it up. It works just as new.


text:
How to unbrick a samsung galaxy S5 (Softbricked no hardware keys)?
So the phone is a S5 SM-G900P, it is stuck in the Sprint logo when booting and the volume keys are broken (power and home keys work).
Developer mode and adb weren't activated in the phone previously
What I have tried:

adb (doesn't recognize my device)
bought a JIG that gets me to the download mode screen
I have flashed 3 official firmwares using odin (
G900PVPS3CQD1_G900PSPT3CQD1_G900PVPS3CQD1_HOME.tar
.md5
G900PVPS3CQC1_G900PSPT3CQC1_G900PVPS3CQC1_HOME.tar
.md5
G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar .md5).
Tried flashing TWRP recovery via odin so i could do the factory reset without pressing keys, it gave me a pass and i was hoping that it took me to that screen after that but same story getting stuck

All the flashing goes smoothly, but like i said gets stuck in the sprint logo
   on all 3
I've read that going into recovery mode and wiping dalvik cache and cache plus factory reset fixes the stuck in carrier logo screen, but with no volume keys i can't access recovery mode.
So i'd love to hear any input or any ways you guys come across that can help me
Much appreaciated

You didn't mention what caused the brick as it can be a hardware issue, a damaged eMMC chip for example.
However, instead of flashing one file, you should try flashing ''repair'' files which are 4 flashable files you can load individually. These files contain the full set of Samsung firmware files. Inside these packages you will get PDA, AP, Modem, Phone, CP, BL, Bootloader, and CSC file.
Download theme from here and flash using Odin.
Fell free to ask if you encounter any problem.

well when i got the phone it didn't register the volume keys, and had android 6.0 got it to a repair shop to unlock the phone to use with a local carrier (outside the US) and then tired of the bloatware flashed a custom rom (lineage OS to be specific) when i did that the local carrier stopped working both phone calls and data plan/internet so i decided to go back to the official firmware and that's when the stuck in sprint logo happened.
P.D: Downloading the repair firmware from the link right now

So in this case, the files should fix that. Just load everything correctly.

just checking, i downloaded the file now and is a single tar.md5 like the other ones instead of the separated ones you pointed do i proceed?

The description said 4 files.... Yes try flashing and see the result.

It worked!!!!! thank you so much! I have been trying for weeks and read all the internet. Wish i could give you thumbs up but i dont have enough reputation for that

I'm glad that I helped. :D


text:
Android ignore the hosts (etc/hosts) when it's in LTE network?
I use hosts to block some sites, which works in WIFI connections,
but when I am in LTE mobile network, these sites seems accessible, I thought somehow android ignore the hosts.
I am in Lineages OS 14.1 (android nougat)
anyone knows how to fix this?

Any VPN involved maybe? Not sure whether that's really relevant, but it's the first thing coming to mind.

This is most likely due to proxy enabled in your APN settings, you can try disabling the setting first and see if the hosts are still blocked.

@xavier_fakerat Since that was the correct answer, would you mind posting it as an answer so the questioner can accept it.

As already suggested by OP, the issue was caused by proxy in APN settings.
Disabling proxy in APN settings (which interferes with host blocking usually by ignoring the hosts file) solved the issue.

thanks for your hint, I finally manage how to set up an APN without proxy, and problem solved. Didn't know had a default proxy there.


text:
Can i get pop-up notifications on my Moto E4?
I just got my new Moto E4, it's my first Android too, so i'm still figuring everything out and i don't know if i just haven't found the settings or it doesn't do what i want. My old Nokia Lumia would put a little pop-up banner notification at the top of my screen (even when my phone was locked, the screen would light up) whenever i got a notification. However, my E4 only chimes, whether the phone is unlocked and the screen is on or not.
It shows an icon on the screensaver when i move my phone, which i can touch to see a message preview, and the lockscreen does show a constant notification after a message is received. But i want to know if there's any way to get a banner at the top of my screen (locked or otherwise) as the notification happens, without having to touch my phone to see what the notification was. Are there any settings for this? Or an app maybe?
Thanks.
Ps. I found an option for it in Whatsapp but nowhere else (although i haven't seen it in action yet so idk what it's like)

Unfortunately there is no option on the Moto E4 in settings to enable these types of pop-up notifications, so you will have to either go into each app (like you did with WhatsApp) and enable pop-up notifications or install an app from the Google Play Store.
An app that I use on my phone is called Heads Up Notifications - https://play.google.com/store/apps/details?id=codes.simen.l50notifications&hl=en

Ah, i guess i just have to live with it then, thanks anyway.


text:
How can I efficiently move 40+GByte of mp3 data to my phone?
My entire music library is sitting on a server that I access through SSH (could be setup for HTTP) and I would like to copy it to my Xioami Mi A1 (running Nougat).
What would be the best way to accomplish this without using an SD card?  I installed Termux, and an rsync client, but:

I don't know the location of where I should download too, and
there seems to be a permission issue anywhere outside Termux's home directory ('whoami' reports my user credentials as "u0_a###")

I would like to transfer the music to the "proper" directory (not just the downloads directory).
With 50+G of unused storage space, I'd really like to make use of it.

The default path for music is typically /sdcard/Music. Don't be fooled by the sdcard in the path, that's a relic of the past from a time where devices didn't feature their own external storage.
For Termux to work correctly in this regard, you have to manually grant read/write permissions to your "SD card" to Termux. Do that in the Settings app under the point of app permissions (exact naming may differ by manufacturer).
The user identifier is the one of the app, because on Android every app gets its own separate user to protect the data of each app.
I have no experience with rsync but I can imagine it will work, if you just switch into the /sdcard/Music directory and use rsync from there.
Termux should have all the tools for doing what you are trying to achieve.

File copying over SSH, with scp, is quite fast, depending on your network environment, and is more reliable than adb push and MTP.
In fact, copying over network is my primary choice for bunches of files.

Agreed.  But you neglected to address my only two points: permissions and proper location.


text:
How do I open an app that Play Store lists as installed, but that isn't accessible?
I installed an app today on a six month old ZTE Axon 7.  I have installed many apps on this device before and never had a problem, and I have plenty of storage left on my phone.  This app downloaded and installed normally, including a playstore alert that installation was successful, but it never appeared on my home screen.  I went to look for it in my list of all apps, but it wasn't there either.  When I go back into Play Store and view the app's detail page, it only shows one button: uninstall.  All other apps also show an "open" button.
I did install this from the play store and not a browser.  I searched for it an installed from Play Store and did not follow a link to the details page.  The app works on my old Sony Xperia Ion, and Play Store lists it as "compatible with all your devices".  I tried uninstalling the app and then reinstalling the app.  I also tried restarting the phone.
I have searched Google and found many reports of other users having a similar problem, but the only solution reported to work is to download it from the play store (as apparently these users installed from a web link).  Just in case, I enabled the "allow installation of apps from unknown sources" and then reinstalled the app, but still got the same result.
What could cause this and how can it be fixed?
If it's relevant, the app is: https://play.google.com/store/apps/details?id=com.nightscapecreations.anim3free&hl=en

It uninstalls normally like any functional app.  And the install takes just as much time as expected to download the apk and then install it.  What side effects might clearing the playstore data have?

Here are the instructions from the page that you linked:
INSTRUCTIONS
Setting a live wallpaper works differently from device to device, and on different versions of Android. In most cases you can set a live wallpaper the same way you set a static wallpaper. Try these methods, and if they don't work feel free to contact us:
1) Tap an open area of your desktop, look for an edit icon, and choose "Wallpaper" and then "Live Wallpaper" from the list that appears
2) Go into "Settings" - "Display" - "Wallpaper" - "Live Wallpaper"
3) Go into "Settings" - "Personalization" - "Wallpaper" - "Live Wallpaper
Try going to set the wallpaper the way you normally would and see if WPS Video Live Wallpapers is there waiting for you.


text:
Xposed Framework: what is it, how does it work and why is it so prevalent?
Some years ago, the term Xposed Framework was not present in the custom ROM and developer scene.
Now it seems to be everywhere.

Xposed is a framework for modules that are able to modify the
  behaviour and looks of the Android operating system and apps. This
  means, that you are able to install modules which add custom ROM like
  features to the Android OS running on your device. These modules
  include both visual- and performance improvements.

This description (quoted from trendblog.net) doesn’t really say anything, because with root priviliges (Xposed seems to require root), users could just as well alter the system in any way they like, so they wouldn’t need Xposed.
What is this Xposed Framework, how does it work, why would I want it and why is it so important nowadays?

To get an overview, you might wish to read my article on it: Xposed: The mighty Android toolbox. I will see to place a summary below as answer.

For a short abstract, let me quote from my article Xposed: The mighty Android toolbox (available behind the link in German and English):

Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. Instead, it reaches deep into the system, modifying the corresponding DEX or ART representations of the app. To be able to do so, Xposed must be deeply integrated with the Android system – which is done on installation of the framework, where it replaces some system components (after backing up the originals, so you can revert back anytime).
There are multiple advantages to this approach. Listing some of them:

you can modify parts of the system you otherwise could not
you can apply multiple modifications to the same app in a combination best fitting your intentions
changes are easy to undo: As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back.

For more details, also on installing the framework and on dealing with modules, please refer to the linked article. Though written almost 2 years ago, it still reflects how it works today; meanwhile, Xposed is also available for Android 7 (which was not released at the time the article was written).
PS: Your next question will probably be on Magisk – but that article is still on my todo list


text:
Do I have ROM in my phone?
How can I find how much ROM I have? This is my phone, Samsung Galaxy S LCD I9003. Samsung Galaxy S I9000 has a ROM of 2 GB. What are the uses of ROM? I heard it is used to flash custom kernels. Cant I flash custom kernels in mine as nothing about ROM is mentioned?

Usually, Read-Only Memory is called internal storage, specifically the system partition on that storage (since other areas are writable by default). The image of the phone's firmware and OS is the ROM.  (That's how we do it on this site, anyways).
So your internal storage is 2 GB, and your phone's firmware and OS is installed on that storage space.  You can flash new kernels or entire ROMs (kernel + other firmware + OS) as long as they fit on the internal storage.  Generally, this isn't a problem; you won't find a ROM image for your phone that doesn't actually fit on your phone.


text:
Galaxy Tab A's Bluetooth draining battery when Bluetooth isn't on
My Samsung Galaxy Tab A just upgraded to Android 7.1. My battery life decreased dramatically after the update. What used to give me days of battery life now only lasts me hours. I checked my battery stats, and this is what I found:

Bluetooth was using most of my battery, but Bluetooth isn't even enabled! What is causing this immense drain of battery from a feature that hasn't been enabled?

A friend I have that also recently got the update on a different Samsung device has been having issues with shortened battery life as well. I'm not sure if it is the Bluetooth on his though.

If it's an option for you, you could try performing a factory-reset of your device (WARNING: All data will be lost, so be sure to have relevant stuff backed up). It could be the update messed up some configuration.

You can also turn off those 2 flags in GPS settings.

Yeah this fixed it for me. Since I forgot to post this answer on my own. You can have it. Welcome to Stack Exchange!

Settings is broken.
Either it's not turning off Bluetooth or the battery history is flat wrong.
I've seen both types of errors over the years.
If the set won't turn off Bluetooth radio power, no amount of force stopping or add on apps is likely to save you.
Nonetheless, maybe they missed something so go at it from another angle.
Check out "Power Toggles"
https://play.google.com/store/apps/details?id=com.painless.pc
If you're using an add-on task manager, stop, most of them flat out lie, and try GSam Battery Monitor.


text:
Where to report issues regarding the stock-email-app
Is
    http://code.google.com/p/android/issues/entry
the right place for bug reports?
My device is a Samsung Galaxy Note 10.1 LTE 2014 Edition (SM-P605) with it's original shipped OS (Android 4.3).

This depends upon the ROM that you're using.
If its stock, you're stuck, for most OEMs don't allow sending big reports as such.
If its a google device, or any other device running AOSP, then, the link you've posted is appropriate. Be sure to provide as much related and useful info as possible.
If you're running custom ROMs, they'd often provide you with links, so as to where to post bug reports, (most often being the thread itself (assuming that you're using a custom ROM taken from a forum)), which is where you ought to be posting bug reports.

After I'd specified my target device now, may you have an idea where I have to go?

Here's something on [Where to report device-specific bugs to Samsung?][1]
[1]http://stackoverflow.com/questions/4928267/where-to-report-device-specific-bugs-to-samsung

Actually I'd contacted Samsung at     (http://developer.samsung.com/forum/board/thread/view.do?boardName=General&messageId=254492&messageNumber=7642&listLines=15&startId=zzzzz~) and I'll post the solution here as far as I succeed.

authors: أحمد الضعيفي


text:
What is Android 3DTourViewer?
I'm removing or disabling all non-necessary apps since I had a malware scare this morning.  I'm using a Note 3 with Android Lollipop.
In the Application Manager "All" tab I see 3DTourViewer.  Can I disable this app without ill effect?

Please mention device and Android version in the question

It is Samsung bloatware not malware nor part of regular Android
It is safe to be disabled or removed, if your  device is rooted, as per this reddit post and this XDA thread

I don't have a rooted machine but I was able to remove this without ill effect.

authors: אליהו בן עמי