Related
I am running 3.70 rooted with Myn's ROM and the thing I am looking to do is increase performance. I'm the kind of person that likes to reformat my computer once a month or so... so when my phone starts to feel sluggish when opening up apps or scrolling through homepages it really bothers me. I have some ideas of my own that I need help solving/figuring out and am open to other suggestions.
First, I have used a task killer on and off and the two things I have learned from it is that A) 180+ MB of RAM is what I want to have available on my phone unless actively using an app and B) after I open an app it still uses up memory until I kill it with a task killer and that bugs me.
Second, should I do anything with auto start programs, etc?
Third, I have not done anything with overclocking. Any thoughts on that?
And finally, any other things that are useful for increasing performance?
lower your expectations, performance will increase lol
Experimenting with different kernels and overclocking will boost performance but can also lessen battery life. When overclocking, be sure to read as much as you can find on it. All of our phones respond differently. I've seen max speeds range from 1113mhz to 1267mhz. Always remember to NAND before messing with different kernels. IMO, SetCpu is the most commonly used app to manage clock speeds. Its a paid app available in the market.
Using a program like Autostarts wont necessarily boost performance but will increase battery life cuz certain apps you dont need running wont be allowed to start on their own.
Task killers are pretty much useless with Froyo since it only allows them to terminate background usage of the app. It wont completely kill the app. Android itself does a pretty good job of automatically killing apps that dont need to be running.
Since you're using Myn's, I'm sure many optimization/performance tweaks have already been made within the rom itself. I'm a Sense fan, but CM6 (AOSP based) is going to give you the absolute highest performance of any rom available to our phones. Sense roms will always be a little slower due to the fact that Sense eats up ALOT of memory.
Have you tried cachecleaner? Usually does the trick when my phone slows down
Sent from my PC36100 using XDA App
check out my tweaking thread You can find the link in my signature
Resurrect much?
Sent from my PC36100 using xda premium
I finally found a perfect ROM for my needs but I'm experiencing a few problems.
1. When syncing live feed on facebook for HTC sense, it just syncs forever. Really annoying, especially when auto-sync is enabled. I tried just turning live feed sync off, but it turned itself back on
2. Get soft reboots sometimes, with no specific reason.
3. Sometimes the statusbar image shifts 7-8 pixels to the right, leaving uncovered space on top left, reboot fixes it, but still, annoying.
4. On the messaging app, when I close the physical keyboard without leaving the conversation page, it leads to reloading of my homescreen and sometimes leads to bug, when launcher bar is on the wrong orientation. (this problem might be caused by the sense 3 lockscreen mod, it said somewhere that it modifies the messaging app)
5. How can I reduce the amount of my homescreens ? I use only 3 and I heard that it helps to free RAM
6. How can I format my partitions into ext4 ?
7. I heard of v6 supercharger script, can anyone help me with a step-to-step guide of how can I setup that and how will I benefit.
Been using this Rom for ages now and don't get these problems. Also, you shouldn't really need super charge to make it fast and smooth. Have you tried wiping and flashing again?
Sent from my HTC Vision using Tapatalk
I just did, let's see if it solves problems 2-4, number 1 is still there.
It is smooth but if the supercharger is going make it even better, why not ? Also I heard it extends battery life which is always good.
And I think I figured out the reason of live feed problem, I usually remove the friendstream stuff, and I think that may cause the trouble.
kkira13 said:
I finally found a perfect ROM for my needs but I'm experiencing a few problems.
1. When syncing live feed on facebook for HTC sense, it just syncs forever. Really annoying, especially when auto-sync is enabled. I tried just turning live feed sync off, but it turned itself back on
5. How can I reduce the amount of my homescreens ? I use only 3 and I heard that it helps to free RAM
6. How can I format my partitions into ext4 ?
7. I heard of v6 supercharger script, can anyone help me with a step-to-step guide of how can I setup that and how will I benefit.
Click to expand...
Click to collapse
1. I usually remove alot of apps and widgets that I don't use when on a Sense ROM. I found that getting rid of FB Chat makes this issue occur. Removing FriendStream widget might also do this too. Try restoring each app one at a time to pinpoint which one is causing the issue.
5. As far as i know, you can't reduce the number of homescreens on a Sense ROM unless the dev has made tweaks
6. Flash either 4EXT Recovery and change the partitions to ext4. Doing this does NOT erase any information on your partitions. Or you can grab SuperwipeG2+ext4 and this will format your phone to a clean slate and format the partitions to ext4 when when using CWM. This WILL erase everything on your phone.
7. I don't use supercharger, so I can't help you there.
I find when I oc too much I have gotten random reboots. Maybe lower oc a touch?
Sent from my HTC Desire Z using Tapatalk
Athrun88 thank you, great response. For 1 and 5 I came to same conclusions and you proved that I assumed right.
for 6 (ext partiotions) can you explain me how will I benefit from doing that ?
shortlived I didn't do any oc but I think it comes oc-ed so I'll try to lower CPU freq, thanks.
I do this when I use this rom:
Full wipe (system,data,cache,dalvik cache)
Flash rom
Flash unityv9 kernel
Mmsfix.zip
Once it boots I install oc/uvbeater2.apk (search google)
I set screen on profile to 1209/245 ondemand & screen off 500ish to lowest setting conservative
Then with 4ext recovery I set up a swap partition of 512mb
After that I run swap_enabler.sh (search google)
Sounds like a lot but it eliminated all my memory issues and laginess. No launcher restarts, performance/battery hits, or usability. As for v6 supercharger, I had nothing but problems, probably cause I never read everything
Sent from my HTC Vision using XDA App
Oh and statusbar... I just swipe up and down on it. Then it returns to normal. I still get that but not a deal breaker
Sent from my HTC Vision using XDA App
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
i have a feeling this phone is starting to show its age. it seems whenever i install more than 100 apps on this phone it just becomes laggy as hell. to the point where right now the keyboard doesn't even open until 10 seconds later and phone constantly make weird noises when using tune in radio or youtube. the phone is also so slow that it can't even run temple run 2 or any of the games that came out recently. im using xylon rom with trinity kernel for those wondering. i honestly cannot use this phone anymore without having to do a factory reset every month just to stop the lag.
this could be a sign that its time to get a new phone but for now is there anyway to improve performance at all? i already am using the fastest trinity kernel and i have tried multiple roms and all of them seems to lag after hitting 100 apps mark which is ridiculous.
Have you made sure that the phone is not running out of memory as that is what usually causes the slow problems...I too have a 100+ apps and little or no lag. Try a different kernel and Rom maybe u could also tweak the processor speeds and stuff to get your desired performance...
If I helped hit thx
«««««««CYANOGENMOD 10.1 and FRANCO KERNEL»»»»»»»»»
Flash stock factory ROM and do a full wipe.
If you want later then flash custom ROM which is "STABLE".
Then make sure you have enough free memory on your Nexus's internal memory to avoid the lags.
You actually can't improve your Nexus's performance any other way, tweaks speed up very much..
I have over 60 apps installed (usually apps that I need) and some games..
I have 1.4 GB free memory on My Nexus and I use some cleaner apps to get more free space and I don't have any lags..
I use stock ROM that I've modified and stock default kernel..
The hardware slows primarily because of software (apps). Once the hardware fails, it fails.
Check and reign in the number and frequency of apps that sync, update and or check in.
Are you syncing an email client and or keeping them on the device rather than say the Exchange server?
Sent from my Galaxy Nexus using xda premium
kudoboi said:
i have a feeling this phone is starting to show its age. it seems whenever i install more than 100 apps on this phone it just becomes laggy as hell. to the point where right now the keyboard doesn't even open until 10 seconds later and phone constantly make weird noises when using tune in radio or youtube. the phone is also so slow that it can't even run temple run 2 or any of the games that came out recently. im using xylon rom with trinity kernel for those wondering. i honestly cannot use this phone anymore without having to do a factory reset every month just to stop the lag.
this could be a sign that its time to get a new phone but for now is there anyway to improve performance at all? i already am using the fastest trinity kernel and i have tried multiple roms and all of them seems to lag after hitting 100 apps mark which is ridiculous.
Click to expand...
Click to collapse
I have 276 apps on my Nexus and (perceived) performance is better than ever using XENON HD Stable-4.0 and the Franco kernel r364. For the latest update of the ROM, I decided to risk a dirty flash. I seem to have gotten away with it. Performance "feels" excellent, whatever that is worth. My last factory reset was about 2 months ago.
The ROM and kernel have a variety of performance tweaks. I wish there was a way to benchmark performance in a controlled fashion. I hate feeling and perception in the performance department.
On the new ROM, WiFI performance is now solidly pegged at my account's limit of 30 MBs. It was all over the map before, although I realize that many factors affect the Speed Test app.
The "seeder" app helped a lot for my device in reducing lag. The overall community is sharply divided about the effectiveness of the seeder: YMMV. Its worth trying, though. I've been using it for about 6 weeks. Other than the Google Play Store updates, I don't have lag any more. Before the seeder, I felt like you -- the phone was almost unusable.
Regarding the device feeling dated, this ROM supports the expanded desktop and the pie. Wow, the phone feels new again. No kidding.
smtom said:
The hardware slows primarily because of software (apps). Once the hardware fails, it fails.
Check and reign in the number and frequency of apps that sync, update and or check in.
Are you syncing an email client and or keeping them on the device rather than say the Exchange server?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I also observed that the apps that run sync/update/check in were slowing down the phone. Check for apps that have daemons associated with them. Decide whether its worth having.
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
herqulees said:
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
AndyYan said:
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
I've already deleted every system app I'm comfortable removing using Root Uninstaller. After having everything I have to have installed on the phone, with as many apps set to not run in the background that I can and Greenify helping too, I tend to have 10-70MB of RAM free, it tends to be 15-35MB free though. I don't use task killers since all they do is play cat and mouse and waste battery, and tried a few auto start managers but can't really get into using it with how complicated they are. Right now the main thing I want to figure out is getting a swap partition up and running since that sounds the most promising with how little RAM this phone has.
Did a backup and switched to the nitest-0721 kernel and so far it's doing good. Disappointed the OC only goes up to 1.2GHz but it's better than nothing (don't understand kernels that limit how much you can OC when it's up to you to find how much your phone can OC), hopefully I can find a way to get it to go higher, and the "voodoo color" is weird but I can install a different version of the kernel to remove that if my eyes don't adjust first. Anyways... my free RAM now stays between 100-200MB, usually about 160MB, with 18% zRAM, purging of assets, and samepage merging enabled which is amazing. Apps are opening faster and don't stutter anywhere near as much as before, so I'm happy but will see how things go tonight when I go to work and am playing with it on and off, along with need to find a way to really overclock it.
herqulees said:
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
Try going with one of didhiy's nitest kernels and maybe a different AOSP ROM, like AOKP, PAC, etc. Or try out SuperNexus even. That's an extremely lightweight ROM with no customization options (Its straight up stock Android, just like a brand new Nexus phone), but its fast and quite stable from what I remember.
Sent from my LG-LS970 using xda app-developers app
Or find one of didhiy's nutest kernels, those have live oc, more free ram, and i believe it goes to 1.4 GHz. I'm not sure though. But it is less stable than nitest
Sent from my SPH-D700 using Tapatalk 2
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
herqulees said:
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
Click to expand...
Click to collapse
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
AndyYan said:
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Click to expand...
Click to collapse
I just seriously hate kernels that limit how high you can overclock instead of making OC options to unreachable levels letting you find your phones limits. People make kernels, roms, hacks, etc so we can get around limitations that the hardware vendors put up. So if we've managed to circumvent the manufacturers blocks why are the same people that got around them making their own blocks, they already put up silly warnings about anything you install/do could break your phone but if you're going to give that warning it needs to be true. Anyways ending my rant lol...
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
herqulees said:
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
Click to expand...
Click to collapse
Uh, AFAIK, isn't these frequency decided only when the kernel is COMPILED (from source code)? I don't exactly know...
Sent from Google Nexus 4 @ AOSPA 3+ 3.99