Jump to content


Approved Members
  • Content Count

  • Joined

  • Last visited

 Content Type 





Knowledge Base

База знаний


Everything posted by RBEmerson

  1. At least I'm not sure which full version of PA "V30" refers to. My general experience with with V3-build-838-arm64-play is that power consumption is marginally reduced and heating similarly reduced. - - - - - - In general, for any electrical device, the heat generated is a direction function of power consumption. As this applies to any phone, the busier a phone gets, the hotter it gets. This is not application specific. Running any specific app does not, per se, mean the phone will get hot for running that app. What does indicate any app will be tied to heating is how "busy" the CPU, etc. will be as demanded by that app. For example, a benchmark app that drives the CPU, memory, etc. to full capacity will heat the phone significantly. An app that does nothing more than blink the notification LED is not likely to much heat because of its low demand on the CPU, etc. Applying this to using PA, the question is simply how much demand is placed on the CPU, etc. when using PA. High demand, high heat. Low demand, low heat. It's my understanding that of the roughly 50,000,000 downloads, accepting there are not 50,000,000 users, the "PA high battery demand/high heat" syndrome is reported by a very small percentage of users. Stipulated that not all who experience this problem have reported experiencing the problem, there's still a very low percentage of users with this problem. That leaves me with the conclusion that the problem is tied to some specific configuration of those phones that causes "high consumption/high heat". It's the developer's call on whether to address the problem or not. Either the conclusion is "there's no way that everyone who uses or tries to use PA is going to be satisfied" or "the problem may be pointing to a something in PA that's worth investigating as it may be a symptom of a potential problem for the wider user community". There is, as part of the latter conclusion, the "non-Google" release, which seems to be giving mixed results. Other strategies also seem to give mixed results. All of the above leads me to think it's best to look at what, in any particular phone, may be using power that, when adding PA's nominal demands, push a specific phone into the domain of excess demand. Excess demand, for whatever reason, means excess heat. Or, PA isn't a pocket warmer, it'the total of the phone's activity that's a pocket warmer. Personally, I'm still trying to figure out what else in my phone is busy when it shouldn't be. My main tool for running down "who's busy when I don't want it to be" is GSam Battery Monitor. I have no skin with this monitor, it's just the monitor I have. I do suggest doing a consumption inventory and use that to decide what apps should shut down, or deleted, if they "do nothing to earn their keep". --- Your mileage may vary, prices higher in Hawaii and Alaska, some assembly required, not tested by the FDA to determine if this product will prevent, treat, or cure any disease, do not use while driving or operating heavy machinery, pursuant to California Proposition 65, this item may contain cancer producing agents. Have a nice day.
  2. 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.
  3. 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.
  4. 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?
  5. 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. 62 Gb with about 10,500 files, 494 folders (many separating albums within one artist).
  7. 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. 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. 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. 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. @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. 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. AFAIK PA is now up to 832. Is power consumption addressed in the update?
  14. 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. 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.
  16. When I tried to reload the key, using the same account, Play said, "$3.99, please". TI, wisely, left a backup for me to find once I got my finger out...
  17. Understood. Fortunately, TI protected me from having to pay $3.99 a second time because I uninstalled the key. Yea for backups! At this point I'm ready to test .820's battery consumption. Great thanks for your help with returning me to .820.
  18. Argh! I slid right past backing up playlists. OTOH, I did get some better album art. Win some, lose some. Anyway .820 is up and running. One last round of questions and and I think this sub-thread reaches its (long sought for) end. At what point did the "pay to play" key app take over? Is it safe to use the current version of the key without running into compatibility issues tied to keeping .820 running? Or does .820 even a problem with continuing to run for an unlimited time?
  19. I tried Chrome and still no joy. I used FX (File Explorer) to install the apk; I had to use root to get the apk installed. That's the good news. The bad news is 820 repeatedly stops. At the moment 83whatever is frozen with Titanium (AKA TI), which means Andy doesn't know it exists. Ditto the pro unlock. PA launches and then stops to the point of showing a message about "keeps stopping" or close that. Of course a crash log is created. I haven't sent it yet, pending whether something is really broken or my phone's to blame. Samsung S7, Andy 7.0, rooted but stock ROM.
  20. No joy - I got the same results. I'll move the apk across from my PC.
  21. Here's how FX reports the d/l: Poweramp-v3-build-820-uni_apk.bc54bb0ef3456ef0a98d7ef17dbec1eb Scary, eh what.
  22. OK, probably OT but... I downloaded 820, expecting an apk but... it sure ain't that. FX will look into the file as an archive, and the contents look about what I'd expect. In other words, looks good to me. My apk installer says this isn't an apk. How do I install 820 over the current PA? Sort of nevermind about the above. I went after 820 from my PC and I got an .apk. Which is fine. But why didn't it download as an apk on my phone? Weird... The S7's version of the file name has what seems to be all sorts of check sums or security strings in the name, and "_apk_" is embedded in all of that.
  23. I may be going OT but... Please add support for .wav tag editing. AFAIK PA doesn't handle .wav tags well, if at all. At the moment, I'm using Mp3Tag to edit wav tags and then loading to my phone. Kinda clunky...
  • Create New...