I just upgrade my cappy from Helly Bean 0813 to 0820. I noticed sometime my memory setting is 375M but I set to XL, so it must 388-390M. After a reboot, it back to 388M, why? I use Devil Kernel Config 0.9. It also happened in build 0813.
Related
I would like to know how I can check if the phone is overclocked? I used the same settings I found in the Suckerpunch #51 Kernel, -100 pretty much everywhere. Stable, Quadrant score is about 1600 consistently...
How can I check how much I'm running at? Also using Serendipity and Suckerpunch does that mean I'm running EXT4?
I'm pretty new to this, I installed this all last night for the first time.
Any help would be appreciate.
T.
Sorry for the double post, but how can i check my file system and how can I get EXT4 - All files if I don't already have it.
Thanks,
I assume your using voltage control if so go into it select the mhz you want to run at from the drop down then there is a tab at the bottom that says select states un check every mhz above the mhz you want to use example: you want 600mhz then only 400, 200, 100 checked the rest all unchecked.
As for ext 4 boot into cwm goto speedmod then lagfix look at the bottom if u see ext4 at the bottom for file systems then lagfix enabled if u don't then u need to enable it in that menu. only about half the file systems will say ext4 if lagfix is enabled
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV
I'm currently running Serendipity latest release with SuckerPunch #51 Kernel.
When you say boot into CWM and go to Speedmod then lagfix, that means i need to change kernels right?
my settings for voltage control are not higher than 1200 and my states checked are 7 states under that like suggested in the Suckerpunch #51 post.
Nevermind my friend, I believe I am in the process of updating to EXT4
"keywords are I believe "
Although right now after doing the lagfix like you mentioned from CWM and enabling EXT4 on all data and systems, I try and run Voltage and i get a message I am not rooted.
Is that a problem? am I doing something wrong?
Edit again I apologize I'm rooted again through CWM.
Thing i still don't understand is how do I bring my OC up to 1200 -- or even better how can I confirm I am Overclocked?
Lol very new to this heh? Go into cwm goto backup and restore and make a backup for me please lol. That way if you screw up you can go into cwm and restore. Now for voltage control id recommend underclocking to 800 because it will help with battery and you won't notice a difference in performance unless you run benchmarks which mean nothing other than giving you.some numbers to show off. Now after you select what you want in voltage control click options button and apply boot settings then exit and thats it. You can get a system info app from market or run linpack and it will show you your clock speed in the results.
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV
Thank you so much - everything seems to running like you said.
File Extensions are EXT4 now, lagfix is enabled, rom is running beautifully, kernel seems stable after 60 runs through stability test.
I think I'm good
I appreciate your input.
np like I said too if your battery life is an issue try underclocking because I run st 800mgz no problem
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV
Updated my SD card to CM7.0.3 and want to use an overclock kernel.
Which one is best to use from the downloads available here do you just use the latest 040411 or are some of the test builds good?
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
findmike said:
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
Click to expand...
Click to collapse
how is the battery usage when overclocked?
When I first set up my SD card the following instructions were in the thread concerning overclocking
5a. *Optional* If you want to run an overclock kernel you need to choose and download a compatible kernel for SD (not eMMC).
5b. Move the uImage file from the SD card to your pc as a backup.
5c. Rename the oc kernel you have downloaded uImage copy it to the SD card.
Can I simply take the zip file for the 042411 kernel open it and swap the uImage files. I saw in another thread about flashing it.
Had lots of trouble getting the 7.0.3 update to take, timing the hold the n and power buttons trick.
Also I saw something about using setcpu to overclock, can someone fill me in on that, is it software or somewhere in the CM7 settings?
s52m3 said:
how is the battery usage when overclocked?
Click to expand...
Click to collapse
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
RASTAVIPER said:
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
Click to expand...
Click to collapse
Are you talking about this app
https://market.android.com/details?id=com.teamwin.kernelmanager.free&feature=search_result
Battery life seems to be pretty good right now but I understand the latest CM builds have some fixes that help increase battery life. I don't think the overclock really effects battery life all that much since the vast majority of the time it doesn't need to kick into high speed.
For the install of the kernel, I normally just flash that when I flash the OS and Gapps. If you are running CM7 off your SD card, I can't help much there except to say that it's SOOOO much easier to run off eMMC since I can just use the built in Rom Manager App to jump into Rom Manager and update things without having to have a bootable card or modifying any files.
Regardless of SD / eMMC install, you don't need to use SetCPU with CM7. If you get the kernel installed, just go into Settings / CyanogenMod settings / Performance / CPU settings and you can change. Most people use the OnDemand performance governor with 1300 max and 300 min and set on boot checked.
I leave Set on Boot off in case something goes goofy. I just reset the overclock to 1300MHz when ever I reboot with a new build.
I could never get the 424 OC to load on my Nook (always got the "expected ) error) so I just swap the OC kernel and system folder into each new build. It's a few extra steps but at least it works.
I'm running N67 at 1300MHz from a Sandisk Class 4 16GB card. Works great!
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
GTT1 said:
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
Click to expand...
Click to collapse
You're running CM7 off an SD card, unless you want to mess up whatever you have on internal eMMC, don't go changing scripts or flashing things which don't apply to your install. Whichever way you got your CM7 installed, stick to the original instructions and follow up on the original threads instead of grabbing bits and pieces here and there. You'd save yourself and others a lot of confusion.
hey,
I installed CM10 stable on my i9000. Since the internal storage in my sgs is broken I had to do the mmc swap. So I did it but it turns out that the swap was not working with a kernel that comes with CM10. So I had to update the kernel to Semaphore 2.6.6. Now changes I did in vold.fstab are being picked up. Is that normal that the mmc swap is not working out of the box with CM10 kernel ?
I do some development on my galaxy and it's almost impossible to do it without a logger working. The logger is ondemand module for Semaphore. I swithed the Logger module on in the Semaphore Manager but it's still not working.
From the console via abg I run
Code:
130|[email protected]:/res/scripts # ./S30enable_logger
cp: can't stat '/system/lib/modules/logger.ko': No such file or directory
What am I doing wrong ? How to enable any logger in CM10 with the sdcard swap ?
EDITED:
I fixed my problem installing CM10.1 + Semaphore 2.9.2
Logger module works for me.
Model: GT-I8910
Android version: 4.3.1 JB
Baseband: I8190XXAMG4
Kernel: 3.0.101-novafusion+ [email protected] #1 Tue Oct 21 ...
CM-Version: 10.2-20141021-UNOFFICIAL-golden
Build: cm_golden-userdebug 4.3.1 JLS36I 6ad612915a test-keys
SELinux Status: deactivated
As the title say everything I encountered an annoying bug, which already affected CM10.2 Rom and my last Carbon ROM. By default 'Use only 2G network' is unticked. I use to mark it active, so i can save up some battery life. But it always switches back to default after a restart. This means changes seem to not being saved in the cache or whatever. Maybe this problem occurs due to errors in mounting the cache partition? I've nothing changed in partitions when i was installing CM. Hm...
So, I haven't yet found any real discussion about that specific little thing. So can anybody tell me if this has a solution to fix or does everyone have to cope with this as there is no way around!?
I have flashed various versions of resurrection remix on my device. I use Elementalx kernel. Every time I open the EX kernel manager and try to edit something it tells me 'frequencies and cores are controlled by system processes. These settings may not persist.' if I try to change anything, it immediately reverts back to its previous state. EX kernel manager is the only kernel managing app on my phone. I am trying to edit kernel settings because I have noticed that some of my cores will constantly run in the high 1000s and never slow down, even when nothing is running.
Please help.