yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] reaeg:
Or try page 6, post #53. Conservative scales perfectly on mine.

I'm glad you maintain it. Mine works perfectly at 1.3 even with a solid UV, Samsung was very conservative with these chips.

Maybe I use my phone harder than most but that extra 30% makes a huge difference; it's amazing for demanding websites and the effect on the battery is small under moderate use.
[Verizon Droid Charge] KaneD20:
Yeah, mine is set to conservative too. Its the only way I can get the processor to go between the selected speeds. The main thing I've found if you want to overclock is that (when using SetCPU) the highest speed desired needs to be selected and 1000MHz HAS to be UNSELECTED in order for the CPU to get above 1000MHz. For me, this set up has been ULTRA stable. No crashes (as long as there are NO profiles set). :)
[Verizon Droid Charge] ssmaster:
I changed the battery in my wifes phone to charge it, and now I got constant force closes with amazon app store, amazon mp3, flex t9 keyboard (installed from amazon appstore) titanium backup etc; CNN force closed when I tried to run it. I deleted all those apps and reinstalled them and everything seems better. Also the touchwiz launcher lost all her icons and reverted back to stock. And she is telling me some of her contacts are missing.

This is all on the stock software, no custom rom & rooted. The only thing I can think of is I converted from imnuts kernel non-voodoo to voodoo and I didn't flash the SD card fix afterwards. This was about 5 days ago... How can I stop this from happening again, I probably won't be near her to fix this the next time it happens.
[Verizon Droid Charge] neyenlives:
I use your OC kernel because it gives me voltage control, but not overclocking. If the non-oc kernel had more control I would use it.
[Verizon Droid Charge] reaeg:
With Voltage Control, you can have 1000 set as well.
[Verizon Droid Charge] Justinsimison:
Conclusion

After three weeks of playing with the OC kernel, I flashed to the non-OC kernel for a week, then back again. I have a few conclusions:

1. When I first flashed to the non-OC kernel, I remember thinking that I didn't see much of a downgrade in performance. Well, after a week, that's just not true. There is dramatically less lag when overclocking. If you never try overclocking, maybe it wouldn't be a big deal. But, once you see how good the phone can be, I don't know how you go back.

2. The overclocking voltage settings that I'm currently using (listed below) are actually more stable than the non-OC kernel which crashed my phone twice in a one week period.

3. There is absolutely no battery difference whatsoever. It's exactly the same. The screen is what kills this battery, and nothing else seems to make much of a difference. In non-4G areas I guess it does a little better, but not significantly.

4. 1400 needs to be disabled (at least in SetCPU) because it's underpowered and there's no way to increase it.

5. 900 is unstable and shouldn't be used.

I can't speak for anyone else, but this has worked really well for me. It hasn't crashed once.

I use SetCPU with the stock Froyo ROM. It's set up as follows:

Conservative mode:

1300 (-50)

800 (-100)

600 (-75)

400 (-100)

200 (-125)

100 (-150)

I have profiles set for:

Temp >50 degrees C (100-800)

Battery <10% (100-800)

Charging USB (400-800)

Screen Off (100-800)

Charging AC - (1300 in performance mode)

Zero crashes, zero problems, and the same crappy battery life that I get with the stock and non-OC kernels. I have the extended battery and still can't go a whole day, but I use the hell out of the phone and charge it constantly so I'm not upset about it. It's time to realize that these batteries aren't adequate for our devices anymore. The technology is improving too quickly and it's about time someone comes up with a more innovative way to power this junk.

Anyway, my phone is running so well right now that I can't imagine it being better. I remember saying that very thing about my Omnia a few years ago. It's crazy how fast things change.
[Verizon Droid Charge] charlie_c:
Thanks for the feedback, I've been going back and forth about trying out the OC kernel and I think based on this post, I will.

As far as the batteries, definitely in agreement. It's amazing that this (relatively) little device can manage to replace my standalone GPS while pulling better download speeds than my home cable internet service and broadcasting a mobile hotspot for others in the car, all while running other services in the background. Capabilities I think have far exceeded the power supply, regardless of battery size or mods. Gives me a reason to keep messing with it though :)
[Verizon Droid Charge] charlie_c:
Just ran SetCPU with your settings with the imoseyon 0.13.3 kernel and got a 1993 quadrant score, so definite improvement (I was around 1550 before iirc) and the phone is definitely snappier. I'll try this for a bit and see how battery life and stability is but...very nice so far.
[Verizon Droid Charge] Justinsimison:
Charlie,

Excuse my ignorance but what is that kernel all about? How does it stack up? I didn't know about other overclocking kernels.

To be honest, while I obviously know how to change them, I don't know what a "kernel" is or even means. I'm really not that technical. I just want a fast phone with advanced capability.
[Verizon Droid Charge] charlie_c:
Justin,

Honestly I don't know much about the kernel. I heard some positive things about it and imoseyon is well respected for the work he does on kernels for other devices (mostly the Thunderbolt I believe) so I thought I'd give it a shot. I've been on imnuts' kernel since I got the phone so I thought I'd check out something else for a bit.

The kernel is basically the OS that communicates between the hardware and the software that it runs. I'm still new to Androids so I'm sure someone else could give better input on that.

I don't want to sidetrack since this thread is for imnuts PBJT OTB kernel, but if you had any other questions feel free to PM me.
[Verizon Droid Charge] kvswim:
Eh. The kernel actually communicates with the BIOS (its probably called something else on phones). So, it goes hardware->BIOS->kernel->ROM->UI's->end user. Its amazing to me what everything does to communicate with each other to give us this experience...too bad most of the world is completely oblivious to it.

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] jdenman03:
anybody know how to boot to CMR from the phone being OFF??
[Verizon Droid Charge] charlie_c:
Hold down the home button and volume up and power button until you see the Samsung logo.
[Verizon Droid Charge] jdenman03:
Thanks for this!
[Verizon Droid Charge] DirgeExtinction:
You mean boot to CWM(ClockWorkMod)? Hold down Volume Up, Home, and Power at the same time until the Samsung logo appears for the second time. After it does, you can let go of all the buttons.
[Verizon Droid Charge] anoninja118:
that is the way you do it though I think he forgot to mention once "SAMSUNG" comes up let go of the power button, keep holding the other two until CWM appears

blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] jdenman03:
you guys are correct. I must of didn't press the home button firmly enough or something. Whatever I did, it sure messed up my phone. Had to ODIN back to ED1 and repartition the internal memory. Got everything back up and running now, and its as smooth as ever!
[Verizon Droid Charge] landshark68:
Another way is to keep holding all three buttons until the Samsung logo flashes for the second time, then immediately let go of all three buttons. It only takes a few more seconds for the logo to disappear and reappear, and for me I find it easier to keep holding all three buttons rather than try to let go of just the power button.
[Verizon Droid Charge] vi3tboiii54:
Im using both setcpu (for profiles) and voltage control (adjusting mv) would i run into problems when running both? Also generally how many steps are recommended for OCing to 1400 I have 100 and 900 disabled as of now. Right now im running BFQ conservative with no undervolting across the board yet.
[Verizon Droid Charge] Justinsimison:
Why are you using both? I'd guess they'd interfere with each other.
[Verizon Droid Charge] landshark68:
If imnuts' OTB kernel is anything like nemesis2all's you can't use set cpu on it, only voltage control.
[Verizon Droid Charge] Justinsimison:
You absolutely can (and in my opinion should) use SetCPU with this kernel.
[Verizon Droid Charge] KaneD20:
I've done a lot of trial and error w/ this kernel and overclocking/underclocking. I've found the best settings (for me) and have posted step by step instructions back in post #128 page #13. I use SetCPU on conservative setting.

I have had NO stability issues with these settings.

Others have found different variations in which they can use profiles (frankly, w/ conservative setting I see no reason to have profiles set as my battery never really gets too hot).
[Verizon Droid Charge] zettawatt:
Hi there. First post to the forums. I just flashed the latest 0808_charge_overclock.zip and I am having an issue with the cifs.ko module.

I ran lsmod and I noticed the module wasn't loaded. I tried loading it manually with insmod. Here is the output:

# insmod /lib/modules/cifs.ko

insmod: can't insert '/lib/modules/cifs.ko': unknown symbol in module, or unknown parameter

Any ideas?

Edit: I have been doing some more searching and I found that this module works in concert with the slow-work.ko module, which needs to be loaded first. Is anyone else seeing this issue?

Solved: I downloaded the kernel source and built the slow-work.ko module. As long as I insmod slow-work.ko before cifs.ko, everything's great.

The zip file has both the cifs.ko and slow-work.ko modules
[Verizon Droid Charge] Highriser:
Bootloop and couldn't get into recovery

I don't know why, but when I flashed the kernel, I went into a bootloop and couldn't get into recovery to restore my backup. I odined a different recovery, but this one wasn't one that worked with backup/restore, lol. Instead of odining to EE4, I decided I would check out the new Gingerbread leak EQ1P. It was nice, but back to EE4 for me. I doubt it was a problem with the kernel, maybe the recovery I was on... I flashed the 8/08/2011 version updating from the 7/09/2011 version. Will try again
[Verizon Droid Charge] KaneD20:
I had some issues w/ that version of the kernel. If the reinstall doesn't work, try the last version (0730)... I KNOW it works and you can backup/restore from the CWM.
[Verizon Droid Charge] Highriser:
Thank you! The reflash didn't work, would't boot, couldn't get into recovery. Hopefully this one will work.
[Verizon Droid Charge] KaneD20:
I can't imagine it won't work. I mean stranger things have happened, but with this file I can backup/restore and have had zero problems. Good luck! :D
[Verizon Droid Charge] imnuts:
Don't use profiles, they are known to cause issues on SGS/SGS-based phones (lockups, force close, instability)
[Verizon Droid Charge] bkott425:
Imnuts do i need to install the voodoo kernal before this one or is it included with the oc kernal?
[Verizon Droid Charge] anoninja118:
this is the voodoo oc/uv kernel

blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] droidnewb2000:
Edit: nevermind
[Verizon Droid Charge] Loustsoul:
Will this work on EP1Q?
[Verizon Droid Charge] bkott425:
I believe you said it worked on all the roms but just making sure will it work on the GB_EP1F_BLOATED rom?
[Verizon Droid Charge] KaneD20:
No this will only work on Froyo roms. If you try to install it on any GB builds it will soft brick your phone and you'll have to start from scratch (Odin).
[Verizon Droid Charge] imnuts:
This is Froyo only, added Froyo tag to the topic title.
[Verizon Droid Charge] Loustsoul:
Thank you. Is there anything for ep1q yet?

ROOTED PBJ OC. Altered!
[Verizon Droid Charge] anoninja118:
nothing for GB yet till source is released except for Imnuts' hacked EP1Q kernel that supports ext4/lagfix
[Verizon Droid Charge] Loustsoul:
So can I flash that over this ep1q gummyrc2?

Wriglys lightning
[Verizon Droid Charge] landshark68:
Flash away
[Verizon Droid Charge] Birthofahero:
Just flashed this and wow. My phone flies! Don't care too much about battery, I always have a place to charge, so it's set to max 1400 - bfq - performance.

Could someone tell me the difference in the i/o settings? Ie. vr, bfq.
[Verizon Droid Charge] maurogg84:
I used to run it @ 1400 performance using set cpu. everything was fine until I started using Netflix. It will make your phone reboot

every time. I can imagine a 3d intensive game will do that too.

I followed the advice of some people in this forum and only activated the 1300, 900, 400, 200. I set the frequency at 1300 in performance. then I set up a profile only when the screen is off, since the phone is not used half of the time, in conservative 200 min-900max 100% priority. In that way that can help me save some battery while the screen is off. Since then I haven't had any issues and my phone runs really smooth

I haven't messed with any other settings in set CPU since i'm not really familiar with set CPU. I tried undervolting like other people did in the forum, but is as unstable as overclocking above 1300. If anybody had better luck in undervolting and overclocking let me know.

Sent from my gummy charged OC 1.3 mhz.
[Verizon Droid Charge] anoninja118:
I use voltage control and don't mess with governors or presets, I set it for a mix of battery life and performance... 7 steps I have on imoseyons' kernel: 100mhz, 200mhz, 400mhz, 800mhz, 1000mhz, 1200mhz, and 1400mhz. So max is 1.4ghz, I like to undervolt more towards the bottom end and less in the overclock range. I know a lot of phones don't so much have a problem with overclocking than undervolting (your phone will most likely not take kindly to undervolting too much especially in the higher ranges). 1200 and 1400 I usually set at -25mhz, 100 and 200 at -75mhz (-100 works sometimes, but usually ends up locking up my phone, makes it laggy, or reboots it) and the middle ones at -50mhz. Pretty stable, its fast when it needs to be and battery life is pretty good plus I get around 2300 in quadrant :cool:

blazing through on my 4G Droid Charge
[Verizon Droid Charge] maurogg84:
Thanks for the tip. This its what I did using set CPU:

1400 -25 mV

1200 -25 mV

800- 50 mV

400 -50 mV

200 -75 mV

I tried to use the governor interactive but it was too unstable, it locked or restarted my phone. So I set it on conservative, I had no problems with it since then. To save on the battery I set up a profile only for the screen off 200 min -800 max conservative 100% priority. I don't really get the quadrants scores you get, mines go from 1700-1900.

Now tell me more about this imoseyons kernel, do you think it's better than imnuts kernel? If so where can I get it?

Sent from my gummy charged OC 1.4 mhz.
[Verizon Droid Charge] anoninja118:
I think imoseyons kernel is a little better when it comes to oc/uv... if you search his twitter a few weeks back it should be 'test kernel 0.13.3' or just '13.3', I'll link when I can get to my pc

blazing through on my 4G Droid Charge
[Verizon Droid Charge] d-loko:
imoseyon's 13.3 oc's up to 1400 and it's a 7 slot kernel. Def worth checking out.

Grab it here http://cl.ly/98dC
[Verizon Droid Charge] Echo5Kilo:
Here is my current setup with this kernel (using SetCPU)

Scaling is set to: Conservative

No Profiles created

1200mhz -25mV

1100mhz -50mV

1000mhz -50mV

800mhz -50mV

400mhz -100mV

200mhz -100mV

100mhz -100mV

Phone runs very stable. I'll get a random reboot maybe once a week. And no force closes.
[Verizon Droid Charge] Birthofahero:
After flashing, i can no longer watch youtube videos in hq. However, I can watch them in standard def. I have uninstalled updates but to no avail. Anyone else experience this?

Also netflix has been a little glitchy.

EDIT:

The issue was with the kak tweak not with this kernel.
[Verizon Droid Charge] ElecTech1:
Will this kernel work with gummy charged 2.0. I'm aware 2.0 has a kernel, but would it work if I flash this kernel after flashing gc 2.0?
[Verizon Droid Charge] kvswim:
Yes.

Sent from my Droid Charge running GummyCharged 2.0
[Verizon Droid Charge] Justinsimison:
My "final" SetCPU Settings

It's fair to say that I have a lot of time on my hands lately. I have posted many "ideal" SetCPU settings along the way, but I have configured this thing in every single possible configuration that I could think of.

Finally, after more trials, errors and crashes than you could imagine, I have arrived at what I consider to be absolute stability. Also, as I have said time and time again, the effect on battery life is absolutely inconsequential. The only thing that matters is the screen. I have simply been killing time by finding the absolute lowest voltages possible. It's not going to noticeably improve your battery, but maybe it will at least make you feel better about it. :) You can literally not go -25 lower at any voltage and not see a relatively rapid crash. This is rock bottom, and it will NOT crash (at least I haven't been able to make it crash).

Here's my final settings, and I won't be messing with them anymore unless the technology somehow changes. My standard setup is 200-1300 in conservative mode using the following clock speeds and voltage settings:

(The final number is the percentage of time spent at each clock speed on a typical day. The vast majority of the time spent in 200 is due to the screen being off. With the screen on, the number skews radically toward 1300.)

1300 (-50 or -75, but it will occasionally crash at -75 if you use Opera) 10.3%

900 (-100) 2.77%

800 (-100) 10.49%

400 (-125) 8.49%

200 (-150) 67.88%

NOTES:

1. 100 at (-150) is stable, but it makes no sense to enable it because at that setting you're using exactly the same voltage as 200 at (150). The same is true with 600 at (-100). It's stable, but pointless because 800 uses exactly the same amount of power.

2. 1400 is not stable using SetCPU. There are no two ways about it.

3. Profiles work, but they're a total waste of time. I was doing the "less voltage with the screen off" thing for a while, but it's pointless. It has no effect on the battery whatsoever.

Good luck. I hope this helps someone.
[Verizon Droid Charge] Outsider2011:
I just wanted to put this up here so that you speed demons that have no faith in this OC kernel can now have faith..it works and its fast! I will be flashing the stock PBJ kernel as i dont need to overclock but i have to say it is snappier, faster and something to think about having. My settings for this are 1.4mhz max and min. Using with lagfix on and the voltage app that imnuts recommended...
[Verizon Droid Charge] breaker911:
I noticed that when you reboot the kernel resets the max frequency to 1000 even if voltage control is set to a different setting and the settings are saved on boot.
[Verizon Droid Charge] c0ns0le:
Any chance you can add smartass govener
[Verizon Droid Charge] Cruiserdude:
Great stuff, thanks imnuts! But are you saying that we would see better stability and battery life with your other kernel (from 6-02) than this one, even if we don't actually overclock it? I've undervolted every laptop I've owned, and kept the stock clock speeds, and if this kernel allows it then great. But I know you undervolted the other kernel already, so I dunno.

I'm having a few stability issues already, not sure if its the kernel or something else causing it though. But I want something as stable as possible and improved battery life, if possible. I would love the ability to overclock on demand, but wouldn't use it regularly. So if the other kernel is more stable and efficient then I'll stick with it.
[Verizon Droid Charge] Phlack:
I am lovin this kernel!! Thanks imnuts! Time to start pushin!

Sent from my overcharged Charge
[Verizon Droid Charge] hogowner:
Anyone notice better battery life with this kernel? also, did anyone try this with Setcpu and use profiles?

Sent from my Verizon Charge!
[Verizon Droid Charge] will2live:
I haven't loaded it myself as I'm with Imnuts on OC'ing cellphones as I see no point either. That said tho SetCPU & profiles is a bad plan with Samsung devices from what I'm told. I did have setCPU setup & profiles with the 6/2/11 PBJ kernel and had nothing but reboot issues. Specially if you try to use a clock speed under 400Mhz, but even at 400Mhz settings it still seemed to act weird. As soon as I disabled ALL profiles all the reboot issues were gone.
[Verizon Droid Charge] charliebronson:
I'm having the same thing happen, even when I saved as boot settings in voltage control. It did save me once when the phone locked and rebooted.

My solution was to save profile in voltage control, then load profile after rebooting and that restores the settings just fine.
[Verizon Droid Charge] breaker911:
That is what I have been doing... Maybe it is just me but it gets annoying that every reboot I have to reload the profile.:confused:
[Verizon Droid Charge] suzook:
Did you guys happen to read the release notes????? Its designed that way.
[Verizon Droid Charge] khanfuze:
I think this is a one time thing. For the people that reset to 1000, if you are running SetCPU, uncheck "Set on Boot"
[Verizon Droid Charge] imnuts:
Yes, if you are not overclocking, I would say you are better off running my other kernel. There are some changes that would affect battery life as far as the voltages go that you cannot change with voltage control. Battery life should be better on the other one at stock clock speeds.

It will reset the 1000 on every boot, but again, I haven't used the kernel at all, and I don't know when Voltage Control App kicks in. If you have SetCPU on your system as well, I would avoid using it and uninstall it because it will conflict with Voltage Control as both change the same data.
[Verizon Droid Charge] breaker911:
Is there anyway when using voltage control to have the max voltage set to what ever voltage control is set to. It worked with the fascinate on an OTB kernel. Im not trying to whine about it, but simply point out something I've seen to better the kerne. I appreciate all the hard work done on this kerne.
[Verizon Droid Charge] elucid:
Any advice on what I/O scheduler and CPU governor to use?
[Verizon Droid Charge] MitchTank:
How am I suppose to download this. Downloaded three times and it never saves....or I don't know where....not in downloads. gives me the option to open in rom manager.... but there is no file to flash....help
[Verizon Droid Charge] Cruiserdude:
Thanks for the reply imnuts, that's just what I wanted to know! I wiped and flashed GummyCharged 1.75 last night after posting that, and reflashed your other kernel, and have had great results so far. Thanks again for your great work! :D

Mitch, are you trying to download this directly on your phone? Dolphin lets you view your downloads, I guess the way to do it would be to use a root-enabled file manager and navigate to your downloads folder, then place it on your sdcard. But its much easier to just download it on your pc and put it on the card. You just boot into cwm and flash the zip like you would a ROM, no need for Odin.

But you really shouldn't even have ROM Manager on your phone, much less try to use it. Its pretty well documented that it doesn't work for our phones yet, and you're likely to just brick it if you use it.
[Verizon Droid Charge] MitchTank:
I got it thanks. Does the new cemetery work for back up restore?
[Verizon Droid Charge] Cruiserdude:
I'm not sure, I use Titanium Backup and it works great. Just make sure that you DO NOT use the backup/restore function in CWM, or you'll get a soft brick.
[Verizon Droid Charge] m6ar2cel6o:
ok so i finally had the balls to root my phone by myself. and everything went great. but my question is i flashed this kernel and gummy and everything works but i cant get voodoo enabled? i went into terminal and it says rfs still not ext4. i went into recovery and enabled it and still isnt enabled.
[Verizon Droid Charge] chiahead52:
access the voodoo folder via sd card and delete the disable-lagfix folder if its there
[Verizon Droid Charge] m6ar2cel6o:
nope not there.