Related
So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...
Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.
Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.
I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.
so nothing on the OC for 2.1 yet?
bump
I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.
on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying
O.S.K. byebye command is msmvkeyb_toggle=off
OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.
How to maximize battery life without affecting functionality? I think the answer for this question is different for most of you. It depends on how you plan to use your device, even when it’s not turned on. Keynote is that you have to get the right tools and be creative. To give you a head start, I will dump my configuration in this thread. I am able to get up to 48 hours on one charge using this configuration. If used more intensive, your results may differ from mine though.
My configuration
HTC Desire
DeFroST 2.4d
DeFroST 2.4d"]DeFroST 2.4 SVS 1267Mhz kernel
SetCPU
Setting Profiles
DeFroST 2.4d
I will stick to this ROM for this guide but I’m sure the following applies to your custom ROM as well. DeFroST is my personal favorite and I would like to use this opportunity to thank RichardTrip for all the time he puts into this ROM.
DeFroST 2.4 SVS 1267Mhz kernel
DeFroST 2.4 HAVS max 998MHz 800mV (max 998MHz) might be better at saving more energy. But my decision to pick the SVS 1267Mhz has couple of causes.
I don’t have a CPU that can run at 800mV
I’m not patient, I love to go to max speed when it’s available
I found that with my current settings, battery life is good even with the SVS kernel
As I said, it’s totally up to personal preference. If you feel you need it, flash it! There’s a 925mV kernel out there as well if you have the same issue I do with 800mV (running unstable).
SetCPU
Freely available to any XDA user. A lightweight tool that offers all the functionality we need. Other then setting the default speed, it allows us to use profiles based on things like battery charge and temperature.
Main
Profiles
In my configuration, the phone runs at full speed when the battery capacity >= 75% or if it’s charging. Then when the phone discharges, it gradually scales down the max CPU speed. More important though, I found that I don’t need to have the device running at max speed, seeping energy, when I’m not actively using it. When my display turns of, my max CPU speed will be set to 245Mhz. This is perhaps the most important setting in this configuration.
Setting Profiles
No, not Juice Defender. I don’t know why so many seem to prefer Juice Defender. It cannot be customised the way I like it and the UI gives me a headache. But then again, that’s my opinion, maybe I’m wrong
Setting profiles is once again a lightweight tool that lets you define rules by means of logic. It works like this (example):
Create a profile that enables WiFi
Create a rule Activate WiFi when the condition battery is plugged to any charger is met
I figured that I do not want to receive mail, connect to bluetooth or WiFi when I’m asleep. Also, I don’t need a constant e-mail sync at daytime. 50% sync activity is enough for me. For now, that’ll do.
Profiles
Rules
I have a lot of ideas that can still be implemented. The devs at probeez.com are working hard to implement new functionality into their app. One idea I had was to revert to 2G when the display is turned off. However, the condition display off and the action revert to 2G are not available yet.
If you agree, please let the devs know what functionality needs to be added to make their software even better. Vote on this site.
The 2G functionality has already been planned. My other suggestion, the display state, doesn’t have enough votes yet. You can find it here.
The good thing about this tool is that it will be highly customisable when more and more options are added. This fits the idea of choosing your own energy efficient settings I’m trying to promote with this topic.
Conclusion
I could elaborate my choices, but my point is to give you tips about how to address energy saving. Read this manual and be creative. Copy some of the ideas, change others. Maybe come up with new ideas so brilliant that I should add them to this post .
I’ll try to keep updating this topic with the input from you and the newly available functions in the apps.
Other Recommendations
Manual control of brightness
How could I forget? My own brightness setting is always at the lowest. Unless I'm in a very bright environment (like in the sun) and I cannot see anything on my screen. Auto brightness tends to be to bright in general. The Power Control widget can assist you in quickly switching brightness.
-prove
Use a plain black wallpaper
Although this goes further them some of you want to go, using a plain black wallpaper can save battery usage.
AMOLED: Black wallpaper = Battery saving (experiment result)
-b3ndik
great guide, will try this after I get some sleep!
I would recomend using manual control of display brightness!
prove said:
I would recomend using manual control of display brightness!
Click to expand...
Click to collapse
Added. Thank you.
Although there is not a huge improvement, I'd recommend you to have a plain black wallpaper. It actually saves a few percentages, if you do a quick search around the forum you will find the thread.
b3ndik said:
Although there is not a huge improvement, I'd recommend you to have a plain black wallpaper. It actually saves a few percentages, if you do a quick search around the forum you will find the thread.
Click to expand...
Click to collapse
Added to recommendations, thank you.
Personally I think this goes a bit to far for me. I like active backgrounds, like the one that reflects weather and daytime. However, it's a good idea. If someone can find the link to the detailed topic, I'll add it.
here is the link to the topic. The thread includes tests and results.
http://forum.xda-developers.com/showthread.php?t=660853
is it safe to assume that the profiles that let you enable or disable wifi are in the full paid version ?
*edit*
scratch that, just found 'setting profiles' on the market.
i did lose 2% battery life with just 5 minutes surfing ealier on ..
I have never used any additional program to control power apart from the default Android power widget. I would normally do this to preserve energy no matter which ROM or even which phone I have. It's all common sense:
- turn "2G only mode" and switch on 3G hen I actually need it (e.g. browsing heavy webpages). If you turn off the images in websites even GPRS usually does the job well.
- NEVER use 3G for regular voicecalls. It's a completely senseless way of draining battery fast.
- completely switch off any automatic syncronizations (Gmail, Facebook, Weather, etc.) and syncronize individual accounts only when I actually need it. Simply untick the "automatic synchronization" in the accounts and sync settings.
- of course wi-fi, gps are permanently off and I turn them on manually only when I need them.
- keep the display as dark as possible and no brighter than needed.
- use a solid black wallpaper which saves energy on AMOLED screens (won't make difference on regular TFT LCD). A bright wallpaper may significantly increase energy consumptions.
- forget any "Live" wallpapers.
I have read that killing tasks does not make much difference on Android 2.1 onwards. I still keep killing tasks just as a habit.
This way it adds up a bit of extra manual job but I think it's better than any of those "power control" programs that do the same thing just not as accurately as one can do manually.
well i left my phone on charge overnight and unplugged it at 8am this morning on 100% battery.
6 hours later and it's on 96% - although to be fair that's with near zero usage.
thanks for this topic, very helpfull
on this screenshot, what contains the first line with priority of 100?
http://forum.xda-developers.com/attachment.php?attachmentid=365973&stc=1&d=1279958467
thanks !
I have just implemented everything you recommended, so lets see how tomorrow goes (I can't be bothered to go drive out of my local cell towers ranges right now to see if my WiFi turns off ).
With regards to Disabling Sync, if I set it for 4 minutes out of 5 minutes (4/5) then Sync is only enabled for 1 minute out of every 5 minutes, right?
Having previously used JuiceDefender, I thought I'd give Setting Profiles a bash. First stumbling block is lack of toggling for mobile data - is that right, or have I missed something?
I know, many people here want to have Android 4.x.x on their phones, but unfortunately, because of low-end processor as well as less RAM, these CM10/CM10.1 ROMs are laggy and slow. I am also one of them, but, after using these type of roms since 4 months, I have now got a perfect idea of using them. So, I am sharing the way I use these roms. Many people told that this also helps for CM7 users. So, now I have declared this thread as UNIVERSAL PERFORMANCE THREAD. This method can be used on - Stock | CM7/9/10/10.1.
NOTE : This thread is mainly from galaxy mini forums. But, I have posted it here also, so that Gio users also get its benefits.
NOTE : This method is same for PAC ROMS.. because they are based on CM. So, you can use this on PAC ROMs also.
♦ FINDING STABLE VERSION :
First of all, you will need to find a good stable version of any CM7\CM9\CM10\CM10.1 ROM. Find stable version by asking in general discussion thread of those particular ROM and then download that version. But, do not flash now.. Follow next step.
Note : For CM7 users - Official CM7 is best, but if you want you can try it on custom roms also. If you are using CM7 custom or stock based custom rom, then for scripts n tweaks to work, you must delete all the scripts from init.d so that scripts will not get overridden.
♦ SLIMMING THE ROM :
Slimming means making rom size less by removing unwanted and unnecessary applications from system/app. It reduces system memory use. Here is a chart of cm10.1 apps which are safe to remove - LINK
With reference to that chart you should remove following apps with adding alternatives to them.
Note: Left side apps are to be removed and right side apps are alternatives.
● LatinIME.apk - WP7 Keyboard App
● Browser.apk - Holo Web Browser
● CMFileManager.apk - Root Explorer File Manager
● Trebuchet.apk - Holo Launcher
NOTE: On CM7, default ADW is good, but you can also use Holo Launcher.
Other apps that can be removed without alternatives-
● CalendarProvider.apk - One of the big RAM consuming apps. This app start anytime, you do anything, so it will be a big save of memory removing this app. But, you will get problems with calendar sync..
● GoogleCalendarSyncAdapter.apk - Reomove this only if you do not sync calendar.
● Email.apk - If not in use.
● Gmail.apk - If not in use.
● Talk.apk - If not in use.
● GoogleBackupTransport.apk - It is used in google backups, remove on your own risk. (Not a risk, i always remove it.)
● ChromeBookmarkSyncAdapter - No use.
● HTMLViewer.apk - Never needed.
● UserDictionaryProvider.apk - It is useless without LatinIME.apk.
● VisualizationWallpapers.apk - Wallpapers app. Remove it always.
● CMWallpapers - Remove it always.
● VoiceDialer.apk - Do you really use it?
● LiveWallpapers.apk - Dont you care for your battery?
● QuickSearchBox.apk - If you dont use.
● PicoTTS.apk - Text to speech function.
NOTE: Alternative apps should always be installed in system/app only. For that, I recommend you to remove these apps drectly from rom's zip before flashing.
♦ USE OF SCRIPTS N TWEAKS :
Many people use hard scripts n many tweaks to get good performance. But, it is totally wrong.
Highly recommended to use Activo Speeder. It is the best script for performance. Dont use anyother thing with it- such as ram manager, seeder or anyother script.
(Note: If the above script doesnt work on your device then please find another good script and flash it.)
IT IS RECOMMENDED TO USE SUPERCHARGER ON ICS\JB :
After testing a lot, I found that SuperCharger is the best script which can be used with any ROM to get more performance and for perfect RAM Management. Here are some steps on how to use SuperCharger -
● Here is the original thread for SuperCharger script.
● Script can be downloaded from this download page.
● Download latest script as well as starter package if needed (Read Original Thread).
● Now, for 4.x.x ROMs, you do not need to do anything with services.jar. But, for below 4.x.x, services.jar needs to be patched to get SuperCharger Memory Management working.
● Now, copy script to SDcard and run it with Script Manager as root. For more detailed guide plz prefer the original supercharger thread.
● Now, you are running the script. You will find many options and info on screen. Read it all and choose what you want.
NEW DISCOVERY : SUPERCHARGER + CROSSBREEDER = ULTIMATE PERFORMANCE WITH MAX ENTROPY ! - by Dark Passenger
● LINK FOR THE POST.
Here are some tweaks-
In Build.prop -
●
Code:
ro.ril.disable.power.collapse=0
and change the value from 0 to 1. (Add the line with proper value if does not exist)
This one is for battery saving.
●
Code:
dalvik.vm.heapgrowthlimit=48m
If it already exists then just match the values.
This is a VM Heap management for RAM.
●
Code:
ro.ext4fs = 1
Improves EXT4 performance.
● IMP :
Add following lines below "# Other" in build.prop
Code:
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
(If exists, just change the values as above).
(Note: This one will remove location feature increasing performance freeing up more RAM. This frees up to 30mb of RAM)
And now remove NetworkLocation.apk from system/app as well as com.android.location.provider.jar from /system/framework.
For further build.prop tweaking, you can use this great guide -> Click Here. Thanks to Dark Passenger for some build.prop tweaks.
This much tweaking and scripting is enough. DONT USE TOO MUCH TWEAKS N SCRIPTS.
♦ BASIC APPS TO USE :
Your rom's performance also depends on the apps which you use. Always look for apps' memory usage and if the app consumes more ram then try to find an alternative app for it. Here are some basic apps which you should use (i always use them).
● Use Root Explorer as file manager, Holo Launcher as Launcher.
● Use Cache Cleaner App. It is must. Clean cache once a day.
● Use Root Cleaner App. A must have app. Do "Quick Cleaning" twice a day. It will regulate your performance.
You can also freeze the apps you are not using at that time, such as DSPManager (Unfreeze it only at the time of listening songs)
Freezing Google Apps will be a great way to reduce RAM consumption.
● Use this amazing app - Autostarts. This app controls the apps that start automatically in your phone. If you want settings which I use then PM me. I will tell you, how to use this app.
CLICK HERE FOR AUTOSTART APP SETTINGS
● ABOUT TASK KILLERS :
Using task killer is good but, it is also bad. Task killing is actually meaningless. Some apps never really get killed. They start again n again. So, use Autostarts instead task killers. But, here is a nice app for killing processes and freeing RAM. This is the original app. I have themed it to look good. Download it here.
Use it as a task killer, press menu button and include system processes and then start killing processes which are useless.
● Try to use apps as system apps.
● If you are using UC Browser then in its settings, check "Clear Data on Exit". If did, you will see UC will take less than 10mb but, if you wont do this, UC will take more than 15mb.
♦ IMPORTANT TIPS AND SETTINGS :
● Always flash rom with a clean wipe and proper flashing method.
● Do not flash gapps again if they are included in the rom.
● Do not flash internal memory scripts as they reduce performance.
● Use Adrenaline Boost. Boost once or twice a day. Boosting much will increase battery consumption.
● Use Root Cleaner app and freeze the apps which you are not using at that time. Freeze Google Play Store, Google Services Framework and other google apps which are always on. Unfreeze them when you want.
● The apps used for Backup purposes should not be installed always. Keep them in your sdcard and install them when you want and uninstall when done with them.
● Basic apps should always be in system/app.
● In Developer Options -
Set all animations scale to .5x
Set Background Process Limit to "Atmost 4 processes", if issues occur then set it back to "Standard Limit".
Enable "Kill App Back Button". Always use this feature to come out of the apps which do not really exit on pressing just back button.
● Do not expect much from our phone as it is not a high-end phone. Dont expect good battery life but, still to gain good battery life. Keep RAM free by using the ProcessKiller app as told above. I always get 170 mb RAM free.
● Do not charge battery until it gets discharged upto 10% or less. While charging do not remove it till it reaches 100% and 20 mins above that.
● Calibrate battery when needed.
● Avoid use of apps which are always running either in background or foreground.
● Press thanks. .
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS.
Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
StiQuezNL said:
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS. Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
Click to expand...
Click to collapse
As I hv mentioned in the title.. this method is for all ROMs.. It is not needed that you should be running JB only.. it is for all...
Noobwithdumbquestions said:
this made everything a lot more laggy and gmail stopped syncing... Also takes about 3 times as long to boot.
No offence, but this is pretty terrible. And after doing some actual research a lot of the "tweaks" you talk about here are never proven effective and frowned upon by actual experts. Even in the article you linked the writer says that something like dalvik heapsize is not something you should or have to change.
I would advice anyone to NOT waste any time on this.
ps: the last part (under tips and settings) is actually some good advice, although the background process limit is not saved in CM10 (and the max.mem tweak doesnt work), so you'll need to do that everytime at startup
Click to expand...
Click to collapse
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
tcris45 said:
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Click to expand...
Click to collapse
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
FlemishDroid said:
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
Click to expand...
Click to collapse
Yeah services.jar needs to be patched on ics and jellybean only. I didnt knew that official cm7 is not there for gio.. I dont own this device. sorry.
Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Dark Passenger said:
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Click to expand...
Click to collapse
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize - BUSTED,
Click to expand...
Click to collapse
This is one property that has cropped up recently in various build.prop recommendations for ICS. Typical suggested values range from “48m” all the way up to “256m”, likely motivated by the common misconception that more is better. The real purpose of this property is much less obvious than one might initially guess. It is also another one you should probably avoid changing.
Click to expand...
Click to collapse
Should you change this setting? Probably not.
Click to expand...
Click to collapse
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
OJ said:
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
Click to expand...
Click to collapse
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Noobwithdumbquestions said:
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
Click to expand...
Click to collapse
the ro.power.disable.ril actually causes the phones radio to go to sleep so if your mobile data is off there is no reason to switch on rather the wifi might switch off(devs already stated so) and again switch back on once you get out of deep sleep.
its a good thing that you are coming back to provide a feedback and is appreciated(at least should be).
the change for dalvik.vm larger than 48 only allows the heap to grow to that value then split into a new heap since we can't/shouldn't/don't use apps with such a large memory footprint the chances of a split occurring post 48mb(gb and below) and 64mb(ics and above) is highly unlikely hence the changing the value to a larger quantity will make no difference.
PS personally even i dont like activo mainly cause i dont know how it works rather i use supercharger and its a much better option in my opinion.
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Click to expand...
Click to collapse
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
In fit's thread, Dark Passenger also wanted to express his ideas and wanted to help me. And I was happy about that. Because the way he helped me was like he really wanted to help. But, you was not polite as him.
You can ask Dark Passenger, there is a lot of information in the thread provided by him and I used that. And he never complained like you.
@Dark Passenger, please explain him.
OJ said:
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
Click to expand...
Click to collapse
Yeah, I was frustrated and my first response was not really fair. I agree.
Noobwithdumbquestions said:
Yeah, I was frustrated and my first response was not really fair. I agree.
Click to expand...
Click to collapse
When you use ics or jelly bean you need supercharger script and a patched services.jar (it's easy to do) because any other script don't works 100 % on it.
Sent from my GT-5660 using xda premium
I have upgraded my Galaxy W to Jelly Bean using Custom Room (4.2.2) Cyanogenmod 10.1 alpha 2. maybe later alpha 3.
Everything runs well. but why my phone's battery drains so fast? and please help me HOW TO SOLVE IT AND MAKE IT LAST LONG TIME???
THANKS VERY MUCH....
Backup your apps, factory reset your phone. If battery drain problem persists, install Greenify or deep Sleep battery saver from Google Play to better manage battery resources.
Lim Wee Huat said:
Backup your apps, factory reset your phone. If battery drain problem persists, install Greenify or deep Sleep battery saver from Google Play to better manage battery resources.
Click to expand...
Click to collapse
Thank you for your suggestion... I will try....
Electro Tobib Muhajir said:
Thank you for your suggestion... I will try....
Click to expand...
Click to collapse
when you just flashed the battery will definitely be shorter. Let it recharge for a few cycles before determining whether its good or bad battery life. Keep in mind however that even at full potential, the battery will not last for more than 2 days even at light usage.
if battery life is more important to you compared to "the newest OS" and whatever extra features it brings with it, then I highly recommend installing acro's CM9 RC2 (yes it is ICS) as the 2.x.x kernel is far better at battery life than 3.x.x (i'm currently testing it and I can already feel the difference! I believe I can reach 2.5 days at modest usage but I will have to update you on that after my first few discharge cycle for battery to reach potential after flashing new rom). I do, however notice a few annoyances with RC2 (not sure if its really the ROM, or the custom kernel i'm using, or Nova Launcher is to be blamed), so if it continues to bug me I may just switch back out to latest ICS =p.
If keeping with the latest JB is important for u, best thing you could do is download a custom kernel for it that supports UV(undervolting), then get IncrediControl and tune down your UV based on some voltage tables you can find in FAQ. This alone won't bring you a HUGE improvement in battery life but its definitely an observable difference. On top of UV, try to UC(underclock) your CPU to 1GHz. Most daily functions, apps and games (depending on how intensive it is) will work perfectly smooth even at 1GHz. IMO, the most important point of UCing is you will notice a very significant difference in the heat of your battery (ie backcover of your phone). Heat is generally bad for the battery (shorter life + faster draining) so UC is definitely a good thing to do =). Of course, on top of all those, get greenify and wakelock detector(WLD) from market to control your not-so-frequently-used apps. Use WLD to track down what is keeping your phone awake (hence drain more battery) and use greenify to hibernate all the not-so-frequently-used apps you have (example of things you DON'T want to greenify: whatsapp and gmail as you don't want to kill these 2 programs when you lock your screen. You want to continue receiving whatsapp messages and gmail when you locked your screen right? XD! Examples of things you SHOULD greenify: games, music player. Maybe some of the games or other apps may keep a background service active, secretly using your battery even though the last time you used it was 2 days ago!)
Finally, if your wonder is about 1-1.5 years old, chances are your battery is already bloated (perhaps you can feel your battery through the backcover of your phone even!) A bloated battery is a dangerous and short-capacity battery. Even with the best rom you may only push through a day from 100-0%. If your battery still looks fine but your phone is nearing its birthday, go ahead and do some online shopping (ebay or local equivalent, like malaysia we have Lelong.com.my) and get a battery for your phone. Its usually much cheaper than buying from telephone shops.
EDIT: Adding on to all of that, choosing a good governor+i/o scheduler combo is important as well. If our phone is similar with the S+, smartassv2+sio(i've used this, its quite smooth and battery is good) OR OnDemand+noop is thought to be very good in terms of battery life and responsiveness. Lulzactive is also very good but its not so easy to tune it so i usually would stay away from it. Do bear in mind that although the former 2 combo is good, it still highly depends on how you use your phone so there will not be a universally best governor+io combo. Both of those suggested by me are supposingly best in responsiveness as well as deepsleep battery conserving (only if the assumption that our roms work the same as the roms tested in S+, which MAY NOT be true).
TL;DR? try smartassv2+sio (u may change this using IncrediControl, get from playstore). Then if you are not satisfied with your current performance/battery life, you may continue experimenting by changing governor and i/o scheduler one at a time. If you are doing the testing, make sure to have some way to record your tests if not you will 100% be deceived by placebo!(with actual numbers you will clearly see whether your feeling is placebo or if there really is an improvement)
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
oribunokiyuusou said:
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
Click to expand...
Click to collapse
Sounds like your battery is bloated. Can u show me a screenshot of your battery graph and app usage?
oribunokiyuusou said:
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
Click to expand...
Click to collapse
that 20% is not actually the 20% of the battery juice. It is 20% of whatever amount of battery is drained due to the display being ON. Like if your battery is used from 100% to 90%, then only 2% is used by the display.
I am not sure if I could explain what I mean.
EDIT: Hmmm maybe I misunderstood what you said... If that is the case, disregard.
And also my galaxy W will use all of its battery charge when the display is constantly ON for about 3-5 hours.
Actually, I've figured out what it was. It was Google Now. Chewing away at the battery without saying a word anywhere in the battery screen. I am now back to my old 3 days battery.
you need to install cpu spay from google play and you need look deep sleep time.
this reaction is typical if your coming from a stock or at least cm9.
there has been a lot of arguments about battery life of cm10 and above.
in my opinion, there really is a difference, i mean cm10+ drains battery faster.
and the reason being is of course the features there is in cm10++.
if you're after battery life, stay with stock or cm9 (for now).
but if you feel like your in with cm10+ and you don't want to go back like me, then may want to try these tricks:
1) using Titanium Backup, freeze the apps that you don't really use.
- in my phone i froze pico tts, voice search, talk back, etc. (i even froze google search )
2) i use an app called "autostarts", it can disable auto starting of app including those of the system.
- in my phone, i disabled google maps in every activity. ex. after startup, connectivity changed, wifi connected, widget updating
3) disable system settings which also contribute to battery draining.
- disable location service when your not using it
- disable automatic backup/restore
- disable haptic feedback
- disable autosync
- disable the top battery drainers when not in use (wifi, mobile data, gps, bluetooth)
- and many more just explore
4) do not use so many widgets (my home screen has 0 widget)
5) do not use live wallpaper
6) charge only using the original charger, not from other phone/brand, not from a usb port
- the best way to charge is to avoid using the phone until it's fully charged
7) finally, install only apps that you really need. just keep a backup of your not so often used apps and install only when you need them
If you think about it, everything i wrote above contradicts with the original concept of Android.
But that's life, sometimes you have to trade something in order to achieve another.
Our phone was baked as Gingerbread, now we want to make it taste like Jellybean.
We have all the ingredients, but we don't have a jelly bean pan to make the candy molds.
So we improvise, we work around, we do some shortcuts, we make alternatives, certainly it will cost something.
egagah said:
when you just flashed the battery will definitely be shorter. Let it recharge for a few cycles before determining whether its good or bad battery life. Keep in mind however that even at full potential, the battery will not last for more than 2 days even at light usage.
if battery life is more important to you compared to "the newest OS" and whatever extra features it brings with it, then I highly recommend installing acro's CM9 RC2 (yes it is ICS) as the 2.x.x kernel is far better at battery life than 3.x.x (i'm currently testing it and I can already feel the difference! I believe I can reach 2.5 days at modest usage but I will have to update you on that after my first few discharge cycle for battery to reach potential after flashing new rom). I do, however notice a few annoyances with RC2 (not sure if its really the ROM, or the custom kernel i'm using, or Nova Launcher is to be blamed), so if it continues to bug me I may just switch back out to latest ICS =p.
If keeping with the latest JB is important for u, best thing you could do is download a custom kernel for it that supports UV(undervolting), then get IncrediControl and tune down your UV based on some voltage tables you can find in FAQ. This alone won't bring you a HUGE improvement in battery life but its definitely an observable difference. On top of UV, try to UC(underclock) your CPU to 1GHz. Most daily functions, apps and games (depending on how intensive it is) will work perfectly smooth even at 1GHz. IMO, the most important point of UCing is you will notice a very significant difference in the heat of your battery (ie backcover of your phone). Heat is generally bad for the battery (shorter life + faster draining) so UC is definitely a good thing to do =). Of course, on top of all those, get greenify and wakelock detector(WLD) from market to control your not-so-frequently-used apps. Use WLD to track down what is keeping your phone awake (hence drain more battery) and use greenify to hibernate all the not-so-frequently-used apps you have (example of things you DON'T want to greenify: whatsapp and gmail as you don't want to kill these 2 programs when you lock your screen. You want to continue receiving whatsapp messages and gmail when you locked your screen right? XD! Examples of things you SHOULD greenify: games, music player. Maybe some of the games or other apps may keep a background service active, secretly using your battery even though the last time you used it was 2 days ago!)
Finally, if your wonder is about 1-1.5 years old, chances are your battery is already bloated (perhaps you can feel your battery through the backcover of your phone even!) A bloated battery is a dangerous and short-capacity battery. Even with the best rom you may only push through a day from 100-0%. If your battery still looks fine but your phone is nearing its birthday, go ahead and do some online shopping (ebay or local equivalent, like malaysia we have Lelong.com.my) and get a battery for your phone. Its usually much cheaper than buying from telephone shops.
EDIT: Adding on to all of that, choosing a good governor+i/o scheduler combo is important as well. If our phone is similar with the S+, smartassv2+sio(i've used this, its quite smooth and battery is good) OR OnDemand+noop is thought to be very good in terms of battery life and responsiveness. Lulzactive is also very good but its not so easy to tune it so i usually would stay away from it. Do bear in mind that although the former 2 combo is good, it still highly depends on how you use your phone so there will not be a universally best governor+io combo. Both of those suggested by me are supposingly best in responsiveness as well as deepsleep battery conserving (only if the assumption that our roms work the same as the roms tested in S+, which MAY NOT be true).
TL;DR? try smartassv2+sio (u may change this using IncrediControl, get from playstore). Then if you are not satisfied with your current performance/battery life, you may continue experimenting by changing governor and i/o scheduler one at a time. If you are doing the testing, make sure to have some way to record your tests if not you will 100% be deceived by placebo!(with actual numbers you will clearly see whether your feeling is placebo or if there really is an improvement)
Click to expand...
Click to collapse
thanks a lot. that's very helpful for me..
klacenas said:
this reaction is typical if your coming from a stock or at least cm9.
there has been a lot of arguments about battery life of cm10 and above.
in my opinion, there really is a difference, i mean cm10+ drains battery faster.
and the reason being is of course the features there is in cm10++.
if you're after battery life, stay with stock or cm9 (for now).
but if you feel like your in with cm10+ and you don't want to go back like me, then may want to try these tricks:
1) using Titanium Backup, freeze the apps that you don't really use.
- in my phone i froze pico tts, voice search, talk back, etc. (i even froze google search )
2) i use an app called "autostarts", it can disable auto starting of app including those of the system.
- in my phone, i disabled google maps in every activity. ex. after startup, connectivity changed, wifi connected, widget updating
3) disable system settings which also contribute to battery draining.
- disable location service when your not using it
- disable automatic backup/restore
- disable haptic feedback
- disable autosync
- disable the top battery drainers when not in use (wifi, mobile data, gps, bluetooth)
- and many more just explore
4) do not use so many widgets (my home screen has 0 widget)
5) do not use live wallpaper
6) charge only using the original charger, not from other phone/brand, not from a usb port
- the best way to charge is to avoid using the phone until it's fully charged
7) finally, install only apps that you really need. just keep a backup of your not so often used apps and install only when you need them
If you think about it, everything i wrote above contradicts with the original concept of Android.
But that's life, sometimes you have to trade something in order to achieve another.
Our phone was baked as Gingerbread, now we want to make it taste like Jellybean.
We have all the ingredients, but we don't have a jelly bean pan to make the candy molds.
So we improvise, we work around, we do some shortcuts, we make alternatives, certainly it will cost something.
Click to expand...
Click to collapse
yups...nice suggestion... thanks very much...:good::good::good:
Lim Wee Huat said:
Backup your apps, factory reset your phone. If battery drain problem persists, install Greenify or deep Sleep battery saver from Google Play to better manage battery resources.
Click to expand...
Click to collapse
THANKS...
oribunokiyuusou said:
I'm having some seeeeerious battery issues with alpha3. With just 15 minutes screen usage in a day, battery settings says my screen used up more than 20% of the battery! This just for consulting the time and the weather.
Click to expand...
Click to collapse
me too.... more than 20%, whereas my battery is in sleep screen and in the lowest brightness
Me too
Sent from my GT-I8150 using xda app-developers app
smeone here is right about cm9 rc2 i just flashed it and used a while.. battery seems to be 2x longer than 4.4 kitkat
here is there link
http://mygalaxywonder.blogspot.sg/2012/09/cyanogenmod-9-cm9-alpha-build-8-for.html
Magpir said:
smeone here is right about cm9 rc2 i just flashed it and used a while.. battery seems to be 2x longer than 4.4 kitkat
here is there link
http://mygalaxywonder.blogspot.sg/2012/09/cyanogenmod-9-cm9-alpha-build-8-for.html
Click to expand...
Click to collapse
No....no....no....
That link will redirect you to a website that has kanged Arco's hard work and NOT given due credit....
Here is the correct, original link....
http://forum.xda-developers.com/showthread.php?t=1576874
........right here on XDA...
This might be my S2, or it might be my W...but it's definitely CM
I'm looking for a recommendation on a rom + kernel combination that could make gaming smoother, would be my number 1 priority. Preferably with minimal bloat (for me, viper rom has too many things I just don't want and I don't like it being there, it's a psychological thing). I don't mind sacrificing battery life if it means smoother gaming, but I of course wouldn't want my device to needlessly run at 100% when it's not really needed.
I'm also looking for 3 specific features:
1. I'm looking for an app maybe that automatically stops my screen from going to sleep when there's a game in focus.
2. Something which disables auto-brightness when a game is in focus.
3. Something to make sure a game won't close? Like, mark it as important and leave it in background. Even so I won't accidentally close it when I "clear all" in task manager.
There has to be an app that can handle those things automatically I hope
Anything else you might suggest would be nice to hear!
thatnitai said:
I'm looking for a recommendation on a rom + kernel combination that could make gaming smoother, would be my number 1 priority. Preferably with minimal bloat (for me, viper rom has too many things I just don't want and I don't like it being there, it's a psychological thing). I don't mind sacrificing battery life if it means smoother gaming, but I of course wouldn't want my device to needlessly run at 100% when it's not really needed.
I'm also looking for 3 specific features:
1. I'm looking for an app maybe that automatically stops my screen from going to sleep when there's a game in focus.
2. Something which disables auto-brightness when a game is in focus.
3. Something to make sure a game won't close? Like, mark it as important and leave it in background. Even so I won't accidentally close it when I "clear all" in task manager.
There has to be an app that can handle those things automatically I hope
Anything else you might suggest would be nice to hear!
Click to expand...
Click to collapse
Too many things. lol
Whatever ROM you decide to settle on, @ivicask's PnP & Thermals tweak will help with your gaming. Flash the mod in recovery, and select the performance profile in Aroma.
You can download it from the thread in this link.
thatnitai said:
I'm looking for a recommendation on a rom + kernel combination that could make gaming smoother, would be my number 1 priority. Preferably with minimal bloat (for me, viper rom has too many things I just don't want and I don't like it being there, it's a psychological thing). I don't mind sacrificing battery life if it means smoother gaming, but I of course wouldn't want my device to needlessly run at 100% when it's not really needed.
I'm also looking for 3 specific features:
1. I'm looking for an app maybe that automatically stops my screen from going to sleep when there's a game in focus.
2. Something which disables auto-brightness when a game is in focus.
3. Something to make sure a game won't close? Like, mark it as important and leave it in background. Even so I won't accidentally close it when I "clear all" in task manager.
There has to be an app that can handle those things automatically I hope
Anything else you might suggest would be nice to hear!
Click to expand...
Click to collapse
Maybe try Tasker app, and Btw Viper rom is actualy most debloated rom, and aroma installer allows you to pretty much remove anything you want.
EDIT:And also, gaming is just fine on this phone since Android 7 update, your overthinking it, all games run perfectly fine at 60fps AFIKl