Develop Bugs

RAM Management

Memory (RAM) management made a big difference on my Evo. But when I try the standard tweaks on my Galaxy Nexus, it doesn't seem to do anyting.
System tuner pro:
Can move tweak sliders, but adjust minfree values do not make a difference in available memory.
Selecting "boot settings" crashes the app
Auto Memory Manager:
Can veiw OOM groupings, but cannot adjust values
Adjusting Min-frees does not seem to make a difference
V6 Supercharger:
Selecting min-frees does not work, will not display current min-frees
Neither "Bullet proof", nor "Hard to Kill" launcher settings work
Anyone have luck in good memory management? SeePU is constantly displaying low memory

Don't, just don't. Uninstall every memory management and task killer app you have and then reboot your phone, trust me, Android can handle memory on it's own - that's one of the functions of an operating system.

Manacit said:
Don't, just don't. Uninstall every memory management and task killer app you have and then reboot your phone, trust me, Android can handle memory on it's own - that's one of the functions of an operating system.
Click to expand...
Click to collapse
Well for some devices with low memory these things can be helpful. But yeah with 1 GB RAM on this phone you will probably do more harm than good with those apps and scripts.
As for why they don't work in this phone, try asking the developers who created them to update them for Android 4.0. A lot of things have changed.
Sent from my Galaxy Nexus using XDA App

I will post in the V6 thread as well about the issues running on this device.
As for why I want it to run on this device: It runs great off the bat, but quickly gets loaded down. Sure, android does a good job of killing apps on its own when needed, but I want that to happen in the background when the device is in my pocket, not when I pull it out and open a new application.
I had the same thing on my Galaxy Tab and managing the memory well works to keep it running lean.
And keep in mind I don't want an app killer, rather to tweak the internal values of the android memory management process:
OOM groupings - to control which applications are killed first in low memory situations, which ones are maintained, and which are never killed.
Minfrees - to control at which free memory levels each OOM grouping is selected for freeing up memory.
Check out the V6 thread for more info: http://forum.xda-developers.com/showthread.php?t=991276

How to increase HTC One X battery life

There is no doubt that HTC One X is the most powerful phone on the market yet, despite it's stock of amazing hardware features it also has a few lacks. And on of the biggest perhaps is the short battery life, but with a few tricks and modifications it is possible to overcome that and so increase the battery life of the best phone yet.
Well I found 6 tricks and extras that can really increase your battery life up to 20%:
1. KILL APPS USING TASK MANAGER
Notice or not but there are a lot of apps and services running in the background of your phone that suck a lot of battery and most of them are apps that you wouldn't need so killing those processes can increase your battery life.
To kill apps you have to access the task manager:
Press home icon>all apps>search for task manager and launch it.
Now you have the option of killing separate apps (press X on the process you want to end) or just ending the all by touching the stop all button.
2. Closing open Apps
A great feature in htc one x is also that you switch between open apps but it can also take a lot of battery depending on how many Apps you =have open.
How to close open Apps:
Touch the recent app button (in right to the home button)> now swipe the open Apps (the ones you want to close) to the top.
3.Disable Transition Animation
Transition Animation also take a lot of batter since the require more ram and disabling them can also increase your ram therewith your overall system performance.
How to Disable Transition Animation:
Go Settings>Display & gestures> uncheck the Animation bar
4. External Battery
Well there is always an option of getting an external portable battery which is quit inexpensive and can double your battery life.
5.System directory Modification
Just a few weeks ago a member (mike1986) posted about a file or directory displacement made by HTC that caused the short battery life. And now you can correct it and you could boost you battery life by up to 20%.
LINK TO mike1986 POST
6.Battery Save App
A battery save app could also be a life save as you can monitor exactly how much on what you're spending and then configure power save modes using apps such as Easy Battery Saver.
You can also turn off services such as 3g/WiFi/GPS to save battery consumption advanced users can also scale the CPU and more system operation with such brilliant app as JuiceDefender - battery saver.
RECOMMENDED BATTERY SAVER APPS:
*JuiceDefender - battery saver* Free
JuiceDefender Ultimate Cost Money
Easy Battery Saver Free
Conclusion:
Following those six step should improve your battery life a lot and should therewith resolve the major issue with the HTC One X.
:goodlease Comment and Thank if you think that this post was helpful.:laugh:​

Hi
HRandev said:
There is no doubt that HTC One X is the most powerful phone on the market yet, despite it's stock of amazing hardware features it also has a few lacks. And on of the biggest perhaps is the short battery life, but with a few tricks and modifications it is possible to overcome that and so increase the battery life of the best phone yet.
Well I found 5 tricks and extras that can really increase your battery life up to 20%:
1. KILL APPS USING TASK MANAGER
Notice or not but there are a lot of apps and services running in the background of your phone that suck a lot of battery and most of them are apps that you wouldn't need so killing those processes can increase your battery life.
To kill apps you have to access the task manager:
Press home icon>all apps>search for task manager and launch it.
Now you have the option of killing separate apps (press X on the process you want to end) or just ending the all by touching the stop all button.
2. Closing open Apps
A great feature in htc one x is also that you switch between open apps but it can also take a lot of battery depending on how many Apps you =have open.
How to close open Apps:
Touch the recent app button (in right to the home button)> now swipe the open Apps (the ones you want to close) to the top.
3.Disable Transition Animation
Transition Animation also take a lot of batter since the require more ram and disabling them can also increase your ram therewith your overall system performance.
How to Disable Transition Animation:
Go Settings>Display & gestures> uncheck the Animation bar
4. External Battery
Well there is always an option of getting an external portable battery which is quit inexpensive and can double your battery life.
5.System directory Modification
Just a few weeks ago a member (mike1986) posted about a file or directory displacement made by HTC that caused the short battery life. And now you can correct it and you could boost you battery life by up to 20%.
LINK TO mike1986 POST
Conclusion:
Following those five step should improve your battery life a lot and should therewith resolve the major issue with the HTC One X.
:goodlease Comment and Thank if you think that this post was helpful.:laugh:​
Click to expand...
Click to collapse
The biggest drain is the screen, so turn down the brightness.
Those other tips are probably more a placebo, and killing tasks is a bad idea on Android. Most of the apps are just loaded into memory but not actively running so not using power, and when your phone screen is off, nothing is running (unless you have a badly behaved application that is). Even if you have most of your memory empty of applications, those memory chips are still drawing the same power regardless, so it makes sense to keep applications in memory. Why? Because when you want to use the app again, the phone doesn't have to waste CPU cycles and power loading the application from the flash memory, then loading the applications saved state, so power is saved. If you never use the app again, and memory is short, it gets unloaded.
There is also the school of thought that if you shut down all background applications and so you lose functionality (background status updates, location services, push mail services, animations, weather displays etc), you then haven't got much of a smart phone!
The system directory modification related to an old version of the firmware, I doubt anyone is effect by that issue now.
Regards
Phil

It wouldn't effect your internal system apps
PhilipL said:
Hi
The biggest drain is the screen, so turn down the brightness.
Those other tips are probably more a placebo, and killing tasks is a bad idea on Android. Most of the apps are just loaded into memory but not actively running so not using power, and when your phone screen is off, nothing is running (unless you have a badly behaved application that is). Even if you have most of your memory empty of applications, those memory chips are still drawing the same power regardless, so it makes sense to keep applications in memory. Why? Because when you want to use the app again, the phone doesn't have to waste CPU cycles and power loading the application from the flash memory, then loading the applications saved state, so power is saved. If you never use the app again, and memory is short, it gets unloaded.
There is also the school of thought that if you shut down all background applications and so you lose functionality (background status updates, location services, push mail services, animations, weather displays etc), you then haven't got much of a smart phone!
The system directory modification related to an old version of the firmware, I doubt anyone is effect by that issue now.
Regards
Phil
Click to expand...
Click to collapse
I do appreciate your replay but it only shows you those task that are running separately (not internal system apps) and if you kill them it does make a difference in the overall performance. And some operations like navigation running in the background continuously uses GPS and even Data constantly, so if you end it, it does make a difference.
You are right with the screen brightness, I thought about it and came to a conclusion to just leave it at auto because no one would like a dim display.
So it wouldn't completely turn off your data or calls or corrupt your system since you wouldn't terminate any internal system apps
regards,
HRanDev

PhilipL said:
Hi
The biggest drain is the screen, so turn down the brightness.
Those other tips are probably more a placebo, and killing tasks is a bad idea on Android.
Click to expand...
Click to collapse
+1
And also control 3G/WiFi/BT radios as and when needed , there are battery saver apps like Juice defender that intelligently turn off 3G and data connections.
Advanced users can also play around with custom kernels, CPU speed settings and Kernel governors, etc.. (can help with custom ROMs)

Thanks for the tip, I added it to it.

Actually agree with PhilipL.
Killing or managing tasks in Android is a placebo - and is likely to do more harm (in terms of battery life) than good. Plenty of articles if you google saying task managers are a bad idea.
However, managing screen brightness and background services will help enormously.
Sent from my HTC One X using xda app-developers app

Battery/RAM/Speed Optimization Tips for Android Phones

I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THESE TIPS.
I've created a couple threads on the ZTE U950 and LG G2, and one problem is the battery life. The battery cannot come out of these devices and thus we cannot combat this with a bulkier, beefier replacement for heavy usage. Charging constantly is something I try to avoid, so these are a few simple tips that can help optimize your battery life (and that APPLY to ANY PHONE):
TIPS
BATTERY
1a) Buy and download CPU Sleeper (root required). There are two versions, one for dual-cores, and the other for quad-cores. Essentially, when a phone is "sleeping", it is actually still running all its cores, helping drain battery faster. This app turns off all but one core when it is "sleeping" so that your battery is not drained nearly as fast.
BATTERY
1b) To take this step a bit further you can download a free app called Multicore CPU Control. In this app you can control your other cores. You can setup profiles to turn on or off cores, and setup each core with different governors. On my LG G2, I setup a profile to only have one core running at 960MHz (2.2GHz originally) after using the steps from below. If you plan to only run one core, then you do not need to buy CPU Sleeper.
NOTES ON 1b: Multicore CPU Control is the name when installed, it is called CPU Performance Control Free on the Google Play Store (either name will work on Google Play). The program needs to be turned on after each boot. When first setting up a profile save it and edit it in order to manipulate the other cores available. The app does not always apply a profile even if it has already been selected. To turn on a profile, click on the profile desired and go to the CPU Monitor tab to check if it has been applied. If not, repeat the process until it does (it usually takes me about 3 times at most).
BATTERY/RAM
2) Download Greenify (root required), a great free app! Sometimes a user does not have a ROM with a kill all button, so pesky apps just stay on without consent. This app allows a user to turn off any app that may want to run in your background, and even shows you which apps are currently running. Apps like Facebook, Talkatone, etc. can all be stopped even if your "task killer" supposedly took care of them.
BATTERY
3a) Wakelock Detector-Save Battery is a free app that checks for apps that continue to work while the phone is "asleep". While Greenify will display the most troublesome apps, this app will help discover any other apps that are running without consent.
BATTERY/RAM
3b) If Greenify does not show the apps discovered in Wakelock Detector-Save Battery, then download Disable Services (root required). This free app allows a user to disable an entire service, or just parts of a service that are bothersome. Click on a service/app to find out what other services accompany it. Read the accompanying services and discern whether or not the service is needed. A good place to start in this app is to check any service/app that has a blue number next to it.
EXAMPLE 3b: I use the Outlook app a lot, but sometimes it gets annoying with updates for insignificant email. I can open Wakelock Detector-Save Battery and click the Outlook app. I turn off "AppWidgetUpdateService" to disable Outlook email updates. Not all services have obvious names, so be careful on system apps if performing trial-and-error.
BATTERY/RAM
3) Buy and download BetterBatteryStats (CPU Spy Reborn/Plus is FREE and only shows CPU states). This app tells me what CPU States are used the most often and is what I download first before my next step. A user can also determine battery-draining apps and turn those off. If turning off those apps is not possible through Settings>Apps just Greenify them!
BATTERY
4) Underclocking. This is an amazing step for saving battery! If you have ran BetterBatteryStats for at least a day, this will come in handy and is highly recommended. You can use numerous programs like SetCPU or Voltage Control to set the clock of the CPU. The key is to find a point that will still be responsive, yet lower than the maximum.
EXAMPLE 4: For this example I will be using my ZTE U950 and Voltage Control. According to BetterBatteryStats, my most used clock was at 1.2GHz and 860MHz. I left my minimum clock at the lowest possible setting, while my maximum clock I changed to 860MHz. I ran this for a few days and saw a noticeable difference in battery life. Another important part to this if choosing the right I/O Scheduler and CPU Governor. I found the default I/O Schedule ("cfq") to perform the best, despite "noop" being good for sluggish memory. "Powersave" is a good Governor at stock CPU speeds, but it will not get a user the savings of power that a step like this will. I tested with this Governor with this step and got horrible reaction times and would often need to restart the phone. The best results I have are with "ondemand" and "interactive". I am currently using "interactive" with a maximum clock of 475MHz! I arrived at that number after checking my BetterBatteryStats while running at 860MHz and found that to be the next most used clock. Now my battery is lasting about twice as long as it normally did! My phone's response time is a bit slower at this low clock speed, but that can combated...
BATTERY/RAM/SPEED
4b) (IF YOU HAVE INIT.D SKIP TO STEP 4c) My LG G2 is underclocked to 960MHz, as noted in step 1b. I am saving quite a bit of battery, but the UI response can lag a lot at times. The use of boot scripts can be helpful to compensate for this. However, my LG G2 does not have init.d support. There are numerous threads that explain how to get init.d support for a lacking Android phone. The simplest method is to install an app from Google Play. I use one called Init.d-Installer just because it forces the phone to reboot once it has installed; others do not seem to do anything to inform a user if they have received init.d support
BATTERY/RAM/SPEED
4c) Download a script called V6 SuperCharger. The thread may seem daunting, but it is fairly easy to install. Download the newest PDF and change it to TXT. Ensure you have init.d support, BusyBox installed (also in the thread if needed), and SuperSU. Run the script in a free app like SManager with SU permissions and follow the instructions. This script gives the ability to enhance speed and power. I install this in order to ensure my UI stays responsive, and LG G2 runs almost at stock speeds (alongside all my other enhancements)!
BATTERY
5) Undervolting (root required/custom kernel required). This is also a great way to save battery. I decrease the voltage in steps of 25 and test from there. If I find no quirks, I leave it. If I find sluggishness or have random phone reboots, I increase by increments of 25 (or 12.5) until I find something stable.
Most phones will not allow undervolting without a custom kernel. To see whether a phone can undervolt or not download, Sytem Tuner. There is a free and paid (Pro) version of this app, but the free one should be sufficient for what we want to do. After installing, open the app and click on the Voltage settings tile on the left-lower side of the screen. All the phone's CPU MHz steps and the amount of voltage applied to each step can be viewed. At the bottom of the screen are buttons to increase or decrease voltage in 12.5 increments (which will apply to all steps). If the -12.5 button is clicked and the values of all the steps drop, then a phone can undervolt. Additionally, System Tuner allows a phone to manually apply undervolting to each step if wanted.
To test undervolting, just push the decrease button until the phone freezes up. There is no harm to your phone or CPU as neither are being overpowered (just the opposite), and a reboot after freezing will reset the phone to default voltage settings. A - 75MHz drop is normal for a phone while remaining stable; and in a lot of cases -100MHz is achievable.
NOTE: Tips #4 & #5 also can be applied to GPUs.
NOTE 2: One thing that should be mentioned is to be careful about putting more than one app that controls CPU clocks. They can read differently and trump the other when used in combination. Instead, install and use one at a time to get more accurate readings. The same should apply to undervolting apps.
BATTERY/RAM
6) A user can change the Dalvik cache a bit to see if that helps optimize RAM, and possibly battery. I did quite a few tests for these to see how they performed. I think the only reason I noticed any changes immediately is because of how far underclocked my CPU is. Anyways, the best results I was able to get with my ZTE U950 was as follows:
124m - dalvik.vm.heapsize (2nd one, not 1st)
8m - dalvik.vm.heapstartsize
For other phones, these are the items to trial-and-error with:
davilk.vm.heapsize (may be more than one at different values)
davilk.vm.heapstartsize
davilk.vm.heapgrowthlimit (may be more than one at different values)
A user can change these settings by downloading an app like Build.Prop from Google Play. I did notice my battery seemed to drain slower with these changed. The RAM was the best optimized for the self-made tests I performed and was nearly the best in all the tests I had ran. A user may or may not notice any differences unless they multitask a lot.
BATTERY/RAM/SPEED
7) All other well-known methods apply as well:
A. Battery Saver apps/settings
B. Battery Calibration apps
C. Refrain from the use of widgets
D. Automatic Brightness apps/settings
E. Small Screen Times before Screen Sleep
F. Turn Off WiFi and/or Data when not needed
G. Task Killers apps/settings

dev options for graphics apps question

Having been talking to various people about various art apps. The concensus seems to bee that beyond 2000 x 2000 most devices suffer from lag and performance issues with drawing programmes. My assumption is that this is due to both processor and RAM demand but have wondered if playing with some of the settings in the dev options would help with this.
I know that android is designed to ballance apps in the background on the fly, but when your main use it to use just the one app, would playing with the "limit background processes", "force gpu rendering" and other options I perhaps have not considered help with the performance of the app in question (even if its at the cost of having a slower tablet in general due to having to load up processes on the fly rather than having them stored in RAM)?
Would this also help with resource intensive games?
I already turn all the animation options off, have a plain background and limit the number of widgets on my homescreens in order to free up as much as possible for my art apps in question.
I also use Greenify to limit apps opening on their own accord and use a gaming booster than shuts down other background apps and stops them opening when said art apps are in use.
I used to OC, but have gone back to 1600mhz and 533mhz for the CPU and GPU respectively having had concerns with how hot my tablet gets in the edge of the screen under load.

hertsjoatmon said:
Having been talking to various people about various art apps. The concensus seems to bee that beyond 2000 x 2000 most devices suffer from lag and performance issues with drawing programmes. My assumption is that this is due to both processor and RAM demand but have wondered if playing with some of the settings in the dev options would help with this.
I know that android is designed to ballance apps in the background on the fly, but when your main use it to use just the one app, would playing with the "limit background processes", "force gpu rendering" and other options I perhaps have not considered help with the performance of the app in question (even if its at the cost of having a slower tablet in general due to having to load up processes on the fly rather than having them stored in RAM)?
Would this also help with resource intensive games?
I already turn all the animation options off, have a plain background and limit the number of widgets on my homescreens in order to free up as much as possible for my art apps in question.
I also use Greenify to limit apps opening on their own accord and use a gaming booster than shuts down other background apps and stops them opening when said art apps are in use.
I used to OC, but have gone back to 1600mhz and 533mhz for the CPU and GPU respectively having had concerns with how hot my tablet gets in the edge of the screen under load.
Click to expand...
Click to collapse
I don't use any apps for drawing and rendering. But, within the last month, I have noticed a huge improvement in performance swapping out my class 10 SD card for a professional quality 633x SD card. I would think any card capable of both 65+ MB/s read and write should help with bottle necks. Though you want to set your app to use the SD card for saving, as it will utilize caching to SD card. I have setup my device to point to SD card for most all app saves and caching. Some apps will use system cache, so unless you are able to tweak further, there is no way to unlimit stock caching. Though I do have trickster mod (Though it is very limited with stock ROM), and found bumping from 128 read ahead cache to 256 to 384, as it seems best with how I utilized my ultra fast SD card. Also you may set the Governor as well, but I have a feeling that is pretty much the same as what you are doing in Greenify. As for antivirus apps, they all have some ways of checking what is going on. If you can temporarally disable and test it may help.

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.