Jump to content
Poweramp

RBEmerson

Approved Members
  • Content count

    86
  • Joined

  • Last visited

About RBEmerson

  • Rank
    Advanced Member
  • Birthday June 26

Profile Information

  • Gender
    Male
  • Location
    SE PA USA
  • Interests
    messing with music, phones, motorcycles and not in that order

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. RBEmerson

    v3 build 823 - High Battery Consumption

    FWIW, I often use PA while I'm doing something that has me carrying my phone in a pocket. I use a "turn screen off when in dark place" (Samsung? Android?) option to keep the screen blank. NTL battery temps go over 100F and the battery is run flat, from 100% in 3-4 hours. BT is off, WiFi is on (I should try with it off). Not a chance I'll use airplane mode at least while I'm the tractor (this is a phone, after all). I tried airplane mode once; no change.
  2. RBEmerson

    v3 build 823 - High Battery Consumption

    IMHO the problem is tied, inversely, to the number of sunspots. No sunspots, lots of consumption. If that's not it, let's resort to astrology and the sign your phone was "born" under. Or maybe bad feng shui? These seem to be as good explanations as any.
  3. RBEmerson

    v3 build 823 - High Battery Consumption

    Sigh... I keep getting apk corrupt. Using Chrome and FF on the phone fails. Ditto for Win10 on my laptop. I went through this for 820. Using d/l to Win10 bypassed whatever was breaking the file on my phone, but not this time... Suggestions?
  4. RBEmerson

    v3 build 823 - High Battery Consumption

    Um... that's pretty drastic.
  5. RBEmerson

    v3 build 823 - High Battery Consumption

    When high battery use kicks in, the problem is tied to PA and rebooting it doesn't change anything. I'm still suspicious of how much Google Play activity I've seen. For a number of reasons, including problems associated with PA, I completely reloaded (down to re-flashing the stock ROM) and re-rootred my phone (Samsung S7). For the record, without being able to use Titanium backup/restore app the job would have taken too many hours. Rooted, and now being able to use Titanium, the job took a couple of hours. Which is why I require rooting for any phone I own. I haven't had time to use it as a player, but I've been working through the curious images choices, and PA hasn't appeared to cause problems. There's a lot of screen use, of course, which also take a bite out of the battery. However, once I leave PA alone, the phone cools down, and battery use doesn't plummet. I still have more testing to do before reporting whatever I find, though.
  6. RBEmerson

    v3 build 823 - High Battery Consumption

    62 Gb with about 10,500 files, 494 folders (many separating albums within one artist).
  7. RBEmerson

    v3 build 823 - High Battery Consumption

    I went through several cycles of power down and up - it didn't make any difference. Additionally, Play finally calmed down. Something is hammering power put even the obvious villain (Play whatever) seems to have either calmed down or is waiting for another round of power grabbing. Somewhere there has to be a tool to point at what's going on outside of PA that sucks down power. Sigh...
  8. RBEmerson

    v3 build 823 - High Battery Consumption

    Another data point, looking some info about Google play. For some reason, Firefox started to cycle through "just crashed - OK this report?" crashes, one immediately after the previous one. After serious round of Oh S***! I found a way to Titanium to freeze (almost an uninstall) Firefox. End of problem. But the phone's still hot. What's going on here??? GSam battery monitor said Google Play was taking about 12% of consumption, with Google Play Services pulling down about 8%, or 20% altogether. It seems that somehow PA may be tickling Google Play into acting up. I'd temporarily freeze Play and Play Svc but suspect that might break something that really matters. Has anyone else seen this or have a sense of how much I can do to Play?
  9. RBEmerson

    v3 build 823 - High Battery Consumption

    Hmmm... Maybe using airplane mode points to a possible source for the problem. With phone and wifi connections disabled, and no more than BT between buds/speakers and the phone, the phone is disconnected from the rest of the world. Which suggests some sort of continuous activity between PA and somewhere outside of the phone. "All" that's left is to figure out what that activity is, and how to stop it, or at least throttle it. Since we power over-consumption sufferers are in a very small set of all users, it's pretty much to guessing at a cause. The notion of effectively disconnecting the phone to use PA has, I think, problems. For example, I use PA to keep me amused while running around on my tractor to cut grass (close to 3 hours if all goes well). If I can't take calls while I'm out... Not Good. In any case, I think going back to .820 didn't really do much good. On to .833...
  10. RBEmerson

    v3 build 823 - High Battery Consumption

    Re VLC: Whatever gets the job done, there you are. For me, I see complaints about file formats, not working well with video, choking on playing back 4K video on a local HDD, the list goes painfully on and on. (Your reply to Blaubär came in while I was busy dissing VLC.) Just so I have things right, you used flight mode and then enabled BT. What about WiFi? If you left WiFi off, are you saying that, in effect, an interaction between PA and WiFi causes excessive drain? Also, which version of PA are you using?
  11. RBEmerson

    v3 build 823 - High Battery Consumption

    @andrewilley @blaubär I didn't realize that the number of folks with problems are enough/so few as to be effectively lost in the noise. Darn... the problem is very real. Being rooted, it's easy enough to freeze (make disappear) almost anything, including excess Google stuff. If only I knew what to nuc... @FinisRonin IMHO VLC is about the last app I'd consider. Even in the PC world it's too fragile, cranky, and unwilling to do stuff to make it very useful. I recommend looking for a better Plan B.
  12. RBEmerson

    v3 build 823 - High Battery Consumption

    I'm baffled about the problem not being reproducible from the production (v. consumer) side when many consumers, including me, experience the problem. This isn't a criticism, just a "I don't get it". Could it be the production side doesn't have items that are common to consumers? Too bad I don't have a spare phone to a) confirm for myself the problem exists, and b) lone it for examination. Oh well too bad I don't have free beer, either.
  13. RBEmerson

    v3 build 823 - High Battery Consumption

    AFAIK PA is now up to 832. Is power consumption addressed in the update?
  14. RBEmerson

    v3 build 823 - High Battery Consumption

    For me, using .820 seems to have moved in the right direction for reducing power consumption. I wonder how much consumption is "playing music" and how much is the process beyond reading the MP3, etc. and how much is feeding the BT or 'phones at the end of the process. In loose terms, how much power does playing consume, how much does audio processing (filters, etc.) consume, and how much does driving speakers, etc. consume. All of that is by way of wondering if .83n is is eating power in signal processing.
  15. RBEmerson

    v3 build 823 - High Battery Consumption

    Um... rooting plays very little role in this save TI's what saved me from spending another $4. Google effectively said "well, yes, it's in your library of installations but you have pay for it anyway." I certainly don't begrudge the donation, but I do expect Google to respond to the key being in my installations library. In any case, that's water over the bridge or under the dam. TI (which requires rooting) got past Google; TI still had a backup copy of the key. That's hardly TI and rooting causing problems. The .820 d/l problem remains a mystery. I'll play with that a bit further in case my d/l functions are somehow in trouble. Thanks for the suggestion about stopping auto-updates. I did that after seeing the update to .83whatever come in. Needless to say, I killed that update, and will manually update until the power consumption issue is resolved. Anyway, this sub-thread is OT. I'm grateful it wasn't drop-kicked off into the bit bucket. Others maybe not so much.
×