Do you have any ideas for finding out why the phone's battery will be too hot?
I implement the PWA site with React and Firebase (firestore). And I'm running into the above problem. To find out about it, I watch the following tools.
Chrome's memory tab
performance's memory tab
Please tell me other ways to find out why the battery is hot.
There are many reasons why your phone runs hot and we are unable to deduce which is the main cause with the data provided. But, some reasons why your phone runs hot may be old hardware, deteriorated battery, the cpu consumption of your page is too high, there is a lot of data transfers happening in the background and many more. Sometimes it might not be even your page that is causing your phone to run hot.
Related
Some sites opened in Firefox take 90% of CPU usage.
Is there some diagnostic utility or plugin to know what these sites are?
If site is known, is it possible to know what script, plugin or something else is reason of 90% CPU usage?
There are also many other issues that can cause high CPU usage outside of Firefox itself. I usually find this type of problem has to do with available memory. If you don't have much available memory left, then the CPU usage is caused by the OS thrashing (i.e. moving pages between virtual and real memory). What I do is to kill Firefox / Chrome with the task manager, and then have Firefox / Chrome restore the pages. Then I clean up the number of tabs I have open. Another thing that can cause CPU/memory usage issues are badly designed plug-ins. Disable them and see if you still have an problem.
I, and a few other of my Android app users, run a Galaxy Nexus. Most of us find the app to be blazing fast, but a couple are reporting that it is unusably slow also on a Galaxy Nexus. I'm shocked to hear them tell me that the buttons, scrolling, etc. are all slow. The main view of the app is a ListView containing many images, textviews, etc. In fact, you can check out the app for free on Google Play if you feel like digging deeper. I'm trying to compile a checklist of what might cause this issue.
Here's what I have so far:
Low memory
Low disk space
Uncaught errors
Rooted device (?)
Any other ideas?
More importantly, is there any way to detect (or even adjust for!) potential problems?
Some other things:
CPU Usage (monitor via an app like WatchDog (it's free)); it mightn't be your app that's the problem
Android version.
Connection speed (Wi-Fi vs 4G vs 3G vs 1x)
Carrier (since they like to flash their own custom ROMs)
AFAIK Android version and connection speed are exposed by the SDK, not sure about CPU usage or carrier.
Of the errors you listed, I think that low memory would be the most likely factor.
If I were you, I'd create a function that would collect as much of this information as possible and send it to your email (or someplace). Then, have some way for the user to call this function (e.g. in the settings menu or someplace like that).
Granted this is all just intuition as an end-user, I have little experience debugging deployed apps from the coding side.
I'm currently having a hard time driving down the peak memory consumption of my background agent below the 6MB limit. Are there any recommendations for WP7 capable memory profilers. I am not even asking for something along the lines of dotTrace but basically anything that offers some insight about what's going on.
The Windows Phone SDK comes with a profiler for both memory consumption, and other things, that's available in Visual Studio after installation of the SDK.
You can read more about it on MSDN
Also, try look isolated at the background agent code, and move it to a separate application, where you run it in the foreground. That could possible make it easier for you to nail where the problem is.
Some computers (e.g. Dell, Vaio) come with software that prevents a battery from charging.
This functionality allows me to use my laptop with battery (protected from power outage) and keep my battery from charging until it's down to, at most, 50% battery/charge remaining.
I want do write some code to automate this task.
I searched Dell Support Center for a solution, and I searched Google, too - no luck with either.
I thought about downloading the program and debugging it, but I couldn't find it.
Has anyone ever seen something like this?
Thanks
PS: I want to do this on a Dell Inspiron, and the code can be in C++/C# (or something)
I've never heard of a program that disables battery charging. (Why on earth would you want this?) If such programs exist, I imagine that they interact with the firmware or hardware at a very primitive level.
One thing you can try is a busy loop (burning power like mad) that checks the battery level and sleeps for a bit once it gets down to the target level. This won't do good things to the cpu temperature, however.
Some laptops come with battery charge limiting functionality - it is not via software though, but via firmware plus dedicated internal hardware I guess. Some Lenovo and Acer have such capability. The logic is not in software as the charge limiter kicks in even when the laptop is off.
The reason is that battery degrade when kept at 100% - as it is the case with laptops that are always plugged in. The new Acer Swift would limit at 80%, some Lenovo let one input a particular value.
If interested I can provide you with the software side - it works on Windows and Linux but can easily be available on MacOS. It works in conjunction with external hardware - i.e. a homeplug.
The code works but it's by no means production ready. It would need a bit of tweaking for a particular operating system and homeplug. Let know if interested.
Available on github: Charge Limiter
There are a few things that I don't understand about iOS memory management.
I wanted to know how much memory typically an iPhone app takes while running on device (Is there any fix number like 10MB?)
If an app includes lot of large images what is the impact on the memory? Do they only impact memory when they are loaded?
How does iOS manage the memory when there are multiple apps running?
Please help me understand these concepts.
There isn't a stated or fixed amount of memory available to apps on iOS devices.
That said, there are game apps that are reported to use over 55MB of memory, however the OS is also reported to kill these games some significant percentage of the time if not run right after a device reset.
If you use 22MB of memory or less, the OS could still kill your app because there wasn't enough available memory, but it would also have to kill a massive percentage of other apps in the app store, so you would be in very good company.
When any app (foreground or background) requests enough memory to start depleting the memory pool sufficiently, memory warnings are sent to other apps. If the memory pool gets small enough, apps are killed, including possibly the foreground app if it's a big memory hog.
Q1) There isn't a fixed value, of course. Every application (and application instance) will use a different amount of memory depending on it's task(s). There is a maximum, however. Reaching this maximum will trigger a memory warning and the OS may kill it.
Q2) Images: Depends on how many you are showing at once, or through animations.
Q3) The application in the foreground gets the most memory allocated to it. Applications in the background can request memory to perform background tasks.
Good article for best practices:
http://inessential.com/2010/06/28/how_i_manage_memory