Develop Bugs

[Q] [NbQ]app|rom|battery

t989 and other large screen devices getting heated up draining battery life is a common sight for the stock rom users. Many blame the bloatware on it, be it samsung, htc, verizon, t-mob etc etc.
However, we install a lot of apps and maybe these are overwhelming in terms of performance but the price we pay is the battery life most of the times. These third party apps can be anything from launchers to widgets to texting apps.
A lot of these apps run in the background and can be categorized as service process, background process, and empty process. This category does not seem to follow a rule in terms of memory consumption.
Why am i saying this?
I observed that installing third party apps which consume a lot of memory(monitoring using task managers/android assistant etc), really drains the battery out of your phone.
I agree there are other several reasons why the battery life could be short.
Major Physical limitations
- Larger display (brighter it is the faster it drains)
- Staying in low network coverage area for longer times
Usage
- Watching videos ( screen is always on)
- Streaming music (always trying to connect to the internet through data)
Software
- rich UI like lot of color rich widgets
- frequent auto updates
- more than once launchers running in parallel
- apps running in background.
But my question is how can i draw a line for an application to use a certain amount of memory. For example a texting app should not take more than X MB of memory, or a launcher is a good launcher if it takes less than Y MB memory.
How do i judge this x and y? What are the best tools you have used?
Please advice
On these notes a BIG thank you to the devs who try to minimize these limitations as much as possible by building kernels(memory mgmt, overclocking), modems(better handling of low coverage areas),radios and of course wonderful ROMS(for better looking, saving user operations, bloat free).

What is ART?..you may ask. (4.4 Art vs. Dalvik )

I DO NOT take any credit for the information provided. Just helpful information.
What Is ART?
ART, which stands for Android Runtime, handles app execution in a fundamentally different way from Dalvik. The current runtime relies on a Just-In-Time (JIT) compiler to interpret bytecode, a generic version of the original application code. In a manner of speaking, apps are only partially compiled by developers, then the resulting code must go through an interpreter on a user's device each and every time it is run. The process involves a lot of overhead and isn't particularly efficient, but the mechanism makes it easy for apps to run on a variety of hardware and architectures. ART is set to change this process by pre-compiling that bytecode into machine language when apps are first installed, turning them into truly native apps. This process is called Ahead-Of-Time (AOT) compilation. By removing the need to spin up a new virtual machine or run interpreted code, startup times can be cut down immensely and ongoing execution will become faster, as well.
At present, Google is treating ART as an experimental preview, something for developers and hardware partners to try out. Google's own introduction of ART clearly warns that changing the default runtime can risk breaking apps and causing system instability. ART may not be completely ready for prime time, but the Android team obviously feels like it should see the light of day. If you're interested in trying out ART for yourself, go to Settings -> Developer options -> Select runtime. Activating it requires a restart to switch from libdvm.so to libart.so, but be prepared to wait about 10 minutes on the first boot-up while your installed apps are prepared for the new runtime. Warning: Do not try this with the Paranoid Android (or other AOSP) build right now. There is an incompatibility with the current gapps package that causes rapid crashing, making the interface unusable.
How Much Better Is It?
For now, the potential gains in efficiency are difficult to gauge based on the version of ART currently shipping with KitKat, so it isn't representative of what will be possible once it has been extensively optimized. Thus far, estimates and some benchmarks suggest that the new runtime is already capable of cutting execution time in half for most applications. This means that long-running, processor-intensive tasks will be able to finish faster, allowing the system to idle more often and for longer. Regular applications will also benefit from smoother animations and more instantaneous responses to touch and other sensor data. Additionally, now that the typical device contains a quad-core (or greater) processor, many situations will call for activating fewer cores, and it may be possible to make even better use of the lower-powered cores in ARM's big.LITTLE architecture. How much this improves battery life and performance will vary quite a bit based on usage scenarios and hardware, but the results could be substantial.
What Are The Compromises?
There are a couple of drawbacks to using AOT compilation, but they are negligible compared to the advantages. To begin with, fully compiled machine code will usually consume more storage space than that of bytecode. This is because each symbol in bytecode is representative of several instructions in machine code. Of course, the increase in size isn't going to be particularly significant, not usually more than 10%-20% larger. That might sound like a lot when APKs can get pretty large, but the executable code only makes up a fraction of the size in most apps. For example, the latest Google+ APK with the new video editing features is 28.3 MB, but the code is only 6.9 MB. The other likely notable drawback will come in the form of a longer install time for apps - the side effect of performing the AOT compilation. How much longer? Well, it depends on the app; small utilities probably won't even be noticed, but the more complex apps like Facebook and Google+ are going to keep you waiting. A few apps at a time probably won't bother you, but converting more than 100 apps when you first switch to ART is a serious test of patience. This isn't entirely bad, as it allows the AOT compiler to work a little harder to find even more optimizations than the JIT compiler ever had the opportunity to look for. All in all, these are sacrifices I'm perfectly happy to make if it will bring an otherwise more fluid experience and increased battery life.
Overall, ART sounds like a pretty amazing project, one that I hope to see as a regular part of Android sooner rather than later. The improvements are likely to be pretty amazing while the drawbacks should be virtually undetectable. There is a lot more than I could cover in just this post alone, including details on how it works, benchmarks, and a lot more. I'll be diving quite a bit deeper into ART over the next few days, so keep an eye out!
Special thanks to Bart Tiemersma for his contributions!
Credits : http://www.androidpolice.com/2013/1...-in-secret-for-over-2-years-debuts-in-kitkat/
Sent from my LG-LS970 using XDA Premium 4 mobile app

How can increase the performance and battery life for Note Pro

HI ALL,
I will root my device , but I want to know how to increase its performance and speed and reduce RAM usage?
and what is the best browser for Android for fast browsing and low memory usage?

Most of the speed increasing and RAM decreasing can be done without root. Replacing Touchwiz with Apex or Nova Launcher is the first step that makes the most difference. Disable most of the bloatware and turn down animations in developer options.

This post probably belongs in the Q&A section, not the software one.
Reduction in RAM usage doesn't necessarily equate to performance boost. Android memory management does a good job of keeping things running smoothly so the goal of debloating should not be to free up RAM. To maximize performance with regards to memory usage with Android what you'll want to do is debloat your device to the point that applications that you'll never use are no longer loading into memory automatically (either as active applications or cached) which will allow other frequently used applications a chance to load into RAM/cache for quick response times. Running memory management software is also counter productive as it will battle against Android's own memory management and kill background applications that you may want cached for quicker response when needed.
Personally I WANT RAM to fill up because if I'm jumping from application to application I don't want to wait for things to load from storage into RAM. I also refrain from cache cleaning frequently because I have a particular routine when I use my device (frequenting particular websites and using particular applications daily) so clearing cache frequently will only force my device to have to re-cache things unnecessarily.
Getting down to the nitty gritty of how to debloat, the approach I took for my device is to work with a few applications; SystemPanelLite Task Manager, Greenify, Boot Manager and Titanium Backup. I would clean boot my device and let it sit for a while (several minutes) to cache applications as it saw fit. I'd then pop into the system panel lite application and look at what was loaded into both active processes and cached. I'd evaluate each entry to determine for myself whether or not I wanted that application to load automatically or not OR NEVER. If the answer was never then I'd use Titanium Backup to freeze the application (of course for each app I'd do my research to see if it was serving an important function). If the answer was that I needed the application but not all of the time then I'd look into Greenifying it and also considered disabling it from starting at boot using boot manager.
I'd do the above iteratively until all I saw in RAM or cached were applications and services that I felt were important. Never during this process did I care how low memory usage was since the goal is to preload as much of the important stuff as possible.
In the end I ended up freezing a ton of Samsung apps, especially after uninstalling applications that relied on their own app store like Hancom.
Of course a quicker way to reduce bloat is to go to a ROM that someone else has debloated and start there as a base. I began my own debloating process early last year though so starting again on a ROM even if it already is debloated to a certain extent doesn't seem worth it for me at this time (but if a lollipop update rolls out and a ROM developer updates to that then I'll surely try it).
Sent from my SM-P900 using Tapatalk

ShadowLea said:
Most of the speed increasing and RAM decreasing can be done without root. Replacing Touchwiz with Apex or Nova Launcher is the first step that makes the most difference. Disable most of the bloatware and turn down animations in developer options.
Click to expand...
Click to collapse
thanks a lot man , I used nove launcher and its v nice , I guess need to root so I can freeze more apps as not all can be disabled using offical rom
muzzy996 said:
This post probably belongs in the Q&A section, not the software one.
Reduction in RAM usage doesn't necessarily equate to performance boost. Android memory management does a good job of keeping things running smoothly so the goal of debloating should not be to free up RAM. To maximize performance with regards to memory usage with Android what you'll want to do is debloat your device to the point that applications that you'll never use are no longer loading into memory automatically (either as active applications or cached) which will allow other frequently used applications a chance to load into RAM/cache for quick response times. Running memory management software is also counter productive as it will battle against Android's own memory management and kill background applications that you may want cached for quicker response when needed.
Personally I WANT RAM to fill up because if I'm jumping from application to application I don't want to wait for things to load from storage into RAM. I also refrain from cache cleaning frequently because I have a particular routine when I use my device (frequenting particular websites and using particular applications daily) so clearing cache frequently will only force my device to have to re-cache things unnecessarily.
Getting down to the nitty gritty of how to debloat, the approach I took for my device is to work with a few applications; SystemPanelLite Task Manager, Greenify, Boot Manager and Titanium Backup. I would clean boot my device and let it sit for a while (several minutes) to cache applications as it saw fit. I'd then pop into the system panel lite application and look at what was loaded into both active processes and cached. I'd evaluate each entry to determine for myself whether or not I wanted that application to load automatically or not OR NEVER. If the answer was never then I'd use Titanium Backup to freeze the application (of course for each app I'd do my research to see if it was serving an important function). If the answer was that I needed the application but not all of the time then I'd look into Greenifying it and also considered disabling it from starting at boot using boot manager.
I'd do the above iteratively until all I saw in RAM or cached were applications and services that I felt were important. Never during this process did I care how low memory usage was since the goal is to preload as much of the important stuff as possible.
In the end I ended up freezing a ton of Samsung apps, especially after uninstalling applications that relied on their own app store like Hancom.
Of course a quicker way to reduce bloat is to go to a ROM that someone else has debloated and start there as a base. I began my own debloating process early last year though so starting again on a ROM even if it already is debloated to a certain extent doesn't seem worth it for me at this time (but if a lollipop update rolls out and a ROM developer updates to that then I'll surely try it).
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Really helpfull man thanks a lot for all the information u shared, am ok with but guess will need to do more research for greenify cuz I didnt use it at all, secondly what office u used after uniinstalling hancom?

I'm currently using Microsoft's Word/Excel Preview apps and have an Office 365 account to enable editing. I've just started (1 month trial) so I haven't really gotten a lot of use out of the software yet.
I can't speak for anyone else but myself but my reason for dropping Hancom was twofold; 1) it did not support the review/commenting features that I needed in Word files and 2) it often required updates at inopportune times. My needs are quite specific, my tablet is a reference and note taking device for meetings and is never used for production type work. As such, I need the ability to take email attachments, open them for review and comment and then send the comments back out as email attachments. The limitations of Hancom when it comes to track changes were a deal breaker for me since I could not see the history of development of reports/documents.
Microsoft's mobile version of Word implements the best support of track changes/comments that I've found to date, so I'm forced to pay the premium of a 365 subscription on this device to get what I need.

muzzy996 said:
I'm currently using Microsoft's Word/Excel Preview apps and have an Office 365 account to enable editing. I've just started (1 month trial) so I haven't really gotten a lot of use out of the software yet.
I can't speak for anyone else but myself but my reason for dropping Hancom was twofold; 1) it did not support the review/commenting features that I needed in Word files and 2) it often required updates at inopportune times. My needs are quite specific, my tablet is a reference and note taking device for meetings and is never used for production type work. As such, I need the ability to take email attachments, open them for review and comment and then send the comments back out as email attachments. The limitations of Hancom when it comes to track changes were a deal breaker for me since I could not see the history of development of reports/documents.
Microsoft's mobile version of Word implements the best support of track changes/comments that I've found to date, so I'm forced to pay the premium of a 365 subscription on this device to get what I need.
Click to expand...
Click to collapse
thanks for reply and sorry for late , hoping the android 5 be great

Install cm12 lollipop ROM. Drastic improvement in browser performance and gaming. For example, Asphalt 8 is extremely slow on stock, even overclocked. On cm12 it runs perfectly with max graphics settings. Unfortunately you lose all the cool touchwiz features like multi window. For me, the performance improvement is enough that it's worth the lost features. I'm anxiously waiting for the official lollipop update.

Kernel profiles converted for Moto E4

Hey guys, this will be my first major post on XDA. I've been scouring through the forums looking for ways to improve on our restricted stock kernel and ran across a few very useful threads. In the Nexus 5X and 6P forums they've created kernel profile scripts that tune the Interactive governor present in all Android kernels. I took the courtesy of going through the threads and compiling a list of all the noteworthy profiles I could find. Huge shoutout goes out to @soniCron, @phantom146, and @Alcolawl for creating the basis behind the governor tuning and scripts to implement them. I converted all the profiles to use the LITTLE cluster settings for our devices since they are a bit lower spec, and taking the EXKM designated profiles and converting them into bash scripts that we can use in a terminal emulator. I gathered as much info as I could on each profile and it's original author. All the profiles scripting layout was customized by myself to look more uniform and stylish.
The original thread can be found here: https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
And the revamped updated thread is here: https://forum.xda-developers.com/nexus-6p/general/guide-advanced-interactive-governor-t3290605
You need to remove the ".txt" extension at the end of the file when you download it, and then you can run it from a terminal emulator directly using source "." or "bash". You can also easily execute the scripts from a file explorer that supports source execution (such as MiXplorer or FX File explorer), then you can simply select the ".sh" file and select "execute" in the explorer. Its recommended to use Kernel Adiutor to tune the variables of the governor if you find you need to.
Feel free to try them out and leave feedback! I can't give any technical help with the profiles as they are not mine. My best advice would be to try them all for at least a full charge cycle each, and then refer to the threads above to tune the one that best suits you until it's perfect. Good luck!
_______________________________________________
******Disclaimer: I am not responsible for you nuking your phones or any other damage caused by using these scripts. Just a friendly reminder.******
AmanuensisOne - @RogerF81: It's mainly based on the StableV2 settings and on EclipseR2, but with a bit smoother experience than with the EclipseR2 profile. It also goes further and tweaks more kernel settings in proc/sys/kernel and sys/module, as well as readahead cache, I/O schedulers, net TCP settings, swappiness, Low Memory Killer parameters, and more Virtual Memory tweaks. This is more of an all-in-one, flash and forget script for users who want a simple way to tweak most major areas of the kernel settings.
Blazer_V4 - @sireangelus: Based on Ghostpepper and Amanuensis, with better battery life for everyday tasks like scrolling and texting. Does not utilize Input Boost and also tweaks some proc/sys/kernel settings as well as Low Memory Killer parameters.
DarkSpiceR7.5 - @xSilas43: Based upon the Ghostpepper settings with some added tweaks to further optimize the battery life and performance of the governer. With revisions to mainly the timer rate and min sample time with the addition of input boost @672mhz for 40ms, this irons out some of the UX issues people may have while also encourages the CPU to use lower clock rates.
DeusEx Revolution - @xperator: Based on AmaneunsisOne and BlackPepper, a bit different than the original DeusEx. More performance oriented. Great for gaming. Almost no lags.
DragonFly @xperator : A profile based on DarkSpiceR7.5 and EclipseR3. It's similar to Butterfly profile meaning its aimed for performance and responsiveness but its snappier and faster than Butterfly. It jumps to mid frequencies all the time even for small tasks. You shouldn't expect great battery life! Even though It should be more battery friendly than Butterfly.
Excalibur - @xperator: Based on DragonFly and GhostPepper. It's almost fast as DragonFly and it has great battery life.
GhostPepper - @soniCron: A medley of Silverfish, MadDog and the Stable settings with a few additional but crucial tweaks aimed at giving extremely smooth performance in all situations, even while multitasking, without sacrificing the battery life as experienced with MadDog.
GlassCannon - @phantom146: Provides the smoothest interface, great performance while bestowing the lowest frequencies available. Ramping up quickly to maximize "inputs" from I/O overheads then immediately ramping down once tasks are done. The perfect balance between lowering down your frequency, and finishing up tasks quickly.
Hawktail_v1.2 - @Alcolawl: An Interactive Governor profile focused on fluidity and UX. Butter smooth in all situations. Minimal heat during web browsing and heavy texting sessions and gamers are praising this profile as well. Great SOT and battery life. The complete package and new candidate for the 'Stable v3.0' Settings.
MadDog - @Alcolawl: Using a new approach, this profile distributes workloads evenly. Drops CPU frequencies as quickly as possible in all circumstances. Performs quite well albeit inconsistently at times.
Saber V2 - @xperator: Designed to work without InputBoost. Mostly no lags/heat issues. Suitable for heavy texting users. Probably not good for gaming. Based on DeusEx family.

First "share my work" post and ya jabbed it in there 4 times, lol. Nice to take some initiative though bro. I know some folks will love it.

madbat99 said:
Most post and ya jabbed it in there 4 times, lol. Nice to take some initiative though bro. I know some folks will love it.
Click to expand...
Click to collapse
I figured somebody else would want to try these out like I did, so I did what XDA was made for and spread my knowledge and I had some issues with posting the OP but I deleted the other 3 so all should be good now. I appreciate your words of encouragement man
Sent from my perry using XDA Labs

Hey, quick update. 3 of the profiles had a few minor typos that I ironed out real quick, and I'm not sure how to edit the attachments in the OP lol. So here's those profiles for anyone who wants them! They are the Blazer, Hawktail and MadDog profiles
Sent from my perry using XDA Labs

@RebelLion_ You have to change attachments on the xda site with a browser. Go to the control panel. Options are there.

Options, then scrool down to attachments.

Android 14 Dev Preview Discussion

*I understand it is just a developer preview*
*I realize I put this in the wrong thread, my apologies. Please don't hound me *
The fact that it is just a dev Preview is why I'm posting this thread, the performance boost and battery management is on another level compared to any previous versions of Android, or any other custom ROM.
I get at least an extra 2 and a half hours of screen on time (without heavy gaming just average use) and the performance is always buttery smooth unless you drop down to less than 10% battery. Applications feel snappier on open and there is little to no performance drop or increase in load times having 20 apps opened in the background.
One thing that does bother me is the enhanced security measures that prevent installing apk files downloaded from the internet. But there is also more support for applications downloaded from 3rd party app stores.
If anyone takes as much interest as me in trying out different and new firmware, I highly recommend trying out the 2nd dev Preview of Android 14.