yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] Beastmode:
I believe cm7 is mtd and this is a bml kernel, so i think no.
[Samsung Galaxy S (4G Model)] Juls317:
Please, please, please, read..
[Samsung Galaxy S (4G Model)] adobrakic:
Sorry lol, been studying all day and my brain's fried. Figured I'd take the lazy way out. Just so happened to be answered on the 4th line of the very first post lol -_- facepalm. Just ignore me.
[Samsung Galaxy S (4G Model)] mzangui:
Valhalla Black FB Edition with this Kernel, light usage
[Samsung Galaxy S (4G Model)] AntonX:
OK, I need another vote :)

I have implemented OC/UV. Running it on my phone, seems to work fine. Now I use SetCPU (free xda edition ), Tergak is uninstalled although it can still be used if desired with its own module. But SetCPU feels nicer.

At the moment I use two overclocking frequencies, 1.2GHz and 1.3GHz. Not sure if I want to go to 1.4GHz, but I can... if pushed hard enough ;)

The vote is about default voltages. I need to set them not too low and not too high, someplace reasonably safe so nobody's phone starts crashing. SetCPU will allow undervolting with sliders going down to -mV, but not up, so it's better to have staring voltages higher than too low right away.

I picked some more or less common numbers from the web, but some people set them quite differently (some lower, some higher), so I'm not sure. Hence the vote.

The voltage table is like this:

Freq (MHz) - Voltage (mV)

1300 - 1375

1200 - 1325

1000 - 1250

800 - 1200

400 - 1050

200 - 950

100 - 950

Give me better numbers if you can. I also remember there was a thread with safe voltages, if somebody finds it post a link.
[Samsung Galaxy S (4G Model)] hechoen:
anton

Here's an old thread about OC.

http://xdaforums.com/showthread.php?t=1109170&highlight=1+6&page=11

Those values look pretty good but if you can only go down I would bump them up a little. Better to be safe than sorry. I think the bali kernel was undervolted as well so you might be able to use that for some reference if you haven't looked at it already.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
I've been using your kernel since the first beta without issue, very nice...

Back to the topic at hand, is this vote for the value of OC/UV or if it should be incorporated? If the latter, I'd discourage it. I'm not a developer, nor do I pretend to be, but I've been following this forum since dsexton was helping us to get oc values that were stable and, as with most things, there was no one size fits all.
[Samsung Galaxy S (4G Model)] AntonX:
I need voltages. OC doesn't have to be used, you actually have to enable it, and you can enable only up to frequency you want. You also don't have to use UV. Basically I'm looking for a very safe starting point.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Edit:

frequency-core voltage-internal voltage

1256-1228-1095

800-1040-1035

400-955-960

200-835-950

100-825-930

Using Tegrak
[Samsung Galaxy S (4G Model)] 95Z28:
I would vote for leaving stock voltages as is. I'm running the same OC/UV profile (1.2) I've been using for months now via tegrak, but I prefer to apply my own settings from stock.
[Samsung Galaxy S (4G Model)] htaak:
I am not a fan of overclocking, except where it is absolutely necessary - example - I got a deadline in 3 hours & my workstation tells me it's going to take 4 hours to complete a render....in that case I have no issue jacking up the CPU frequency to reduce that time and make the deadline.

I would use a kernel that came mildly undervolted (Bali3.3UV was great) but would definitely shy away from anything that had preset OC values. I've had 3 SGS4G's and they have all been significantly different and particular when it comes to screwing with stock voltages. I am currently running stock voltages while testing these new kernels, but when things settle down I'll likely return to Tegrak & Dsex's UV settings which have been great for me in the past. Adding OC at this point could potentially end up being another source of freezes and reboots for a kernel that's still in development - maybe release it to only those people that have had previous success with OC on their phone until they can confirm that gives expected results?

If the Kernel OC deal is something that has to be "turned on" for it to work and still defaults to stock values otherwise then I guess I wouldn't have an issue trying it. :)
[Samsung Galaxy S (4G Model)] ipaq_101:
I think your voltage settings look fine, they are in line with others I have seen in this forum.
[Samsung Galaxy S (4G Model)] AntonX:
Here is the deal. The standard Samsung voltages are different for regular Galaxy S and our phone, Samsung want to run Galaxy S cooler, no idea why. Common internet knowledge has OC/UV settings only for I9000 but nothing for ours. This means that we have to improvise. Below are the comparison tables between the two phones from standard Samsung kernel, as you can see they are quite different.

I have decided to set the voltages slightly undervolted to (VibrantPlus - 0.25mV), unless somebody convinces me to set them even lower to I9000 defaults. I'll set the overclocking voltages safe too, which means higher than our phone can potentially be comfortable with. You'll need to UV yourself if desired.

Samsung default voltages for T959V (VibrantPlus SGS4G)

Freq / arm_volt / int_vold

1000	1325000	1100000

800	1250000	1100000

400	1100000	1100000

200	1000000	1100000

100	1000000	1000000

Samsung default voltages for I9000 (Galaxy S)

Freq (MHz) / arm_volt / int_vold

1000	1275000	1100000

800	1200000	1100000

400	1050000	1100000

200	950000	1100000

100	950000	1000000
​

Btw I enabled 1.4 GHz frequency, what the heck...
[Samsung Galaxy S (4G Model)] AntonX:
Posted 1.0b4 with native OC/UV.

You don't have to use it, or you can still use Tergak. If not enabled there should be no changes to the phone (if you find any let me know!) If you want to use it, get SetCPU (http://xdaforums.com/showthread.php?t=505419)

You cannot use both Tegrak and SetCPU, they will fight with each other. Uninstall Tegrak if you want to use native kernel overclocking.

I'm running 1.4 Ghz right now and it seems fine, but probably wouldn't recommend it to everybody, it just sounds too high for our CPU.

I implemented smooth ramping up for frequencies higher than 1.0 Ghz. The frequency will not jump immediately to the highest available. This should help to save some battery.

The kernel is slightly undervolted to -0.25mV. The table is like this:

1.4 Ghz -- 1400 mV

1.3 Ghz -- 1375 mV

1.2 Ghz -- 1325 mV

1.0 Ghz -- 1300 mV

800 Mhz -- 1225 mV

400 Mhz -- 1075 mV

200 Mhz -- 1000 mV

100 Mhz -- 975 mV​

This is quite higher that numbers posted on this forum, but tha'ts what default Samsung voltages are. You can UV it yourself with SetCPU easily.

Let me know ASAP if you find any problems!

EDIT: Forgot to update kernel version number so it reads 1.0b3 in the settings. Don't have time to tinker with it today anymore, so just ignore it.

EDIT2: Updated version info and re-uploaded. Noting else changed.
[Samsung Galaxy S (4G Model)] Juls317:
Flashed beta4, i'll update with thoughts later
[Samsung Galaxy S (4G Model)] nazcalito:
is there any advantage to using your built-in OC instead of tegrak's?

BTW the phone works fine at 1.4 with your kernels and doesn't even seem to get warm.

Oh -- here's some feedback on your kernel and tegrak. Although your kernel lets me set values for 1400, 1300, 1200, and 1100 mhz in addition to the standard frequencies and whatever faster frequency tegrak has set up, it seems that the phone doesn't go over 1000mhz whatever you've told tegrak to do. At least on my phone
[Samsung Galaxy S (4G Model)] m0bstr:
Thank you for making a oc kernel
[Samsung Galaxy S (4G Model)] Kyndig66:
SGS Kernel Flasher didn't work for me updating from b3 to b4. Ended up flashing in recovery.
[Samsung Galaxy S (4G Model)] Juls317:
I flashed through recovery and the phone info still says beta3, same for you? I'm just trying to see if it's a bad flash it just a missed change before release
[Samsung Galaxy S (4G Model)] FBis251:
Look at his edit:

http://xdaforums.com/showpost.php?p=25396817&postcount=145
[Samsung Galaxy S (4G Model)] Kyndig66:
Thanks for pointing that out. Mine says beta3 also... zip says b4 though.

---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------

Thanks FB. Totally missed that.
[Samsung Galaxy S (4G Model)] lumin30:
Read the edit in the bottom of AntonX's post.

EDIT: Sorry - didn't see there was another page before posting.
[Samsung Galaxy S (4G Model)] crackpot:
Kernel flasher worked fine for me going from beta 3 to 4.
[Samsung Galaxy S (4G Model)] m4xm4n:
AntonX has got SVNET_WHITELIST enabled in this kernel (presumably to prevent unexpected reboots).

To people using this, is there any noticeable battery drain?
[Samsung Galaxy S (4G Model)] g4ry12:
Same here. Flashed fine with SGS Kernel Flasher.
[Samsung Galaxy S (4G Model)] AntonX:
I don't think I have. Just checked both my config and final .config, it's not there. It says '# CONFIG_SVNET_WHITELIST is not set' in both files.

Am I missing something?
[Samsung Galaxy S (4G Model)] Juls317:
Sorry, didn't see the edit
[Samsung Galaxy S (4G Model)] AntonX:
Just checked - Tegrak seems to work fine at least for scaling. CPU seem to follow it properly. For advanced stuff like voltages it needs its own module, I haven't really checked that. I use OS Monitor (free from market) to see what frequencies the phone is running. Anyway, we need a little more info on that, let's wait. That what Betas are for.
[Samsung Galaxy S (4G Model)] m4xm4n:
Oh, maybe you don't. I was looking at aries_galaxys4g_defconfig
[Samsung Galaxy S (4G Model)] AntonX:
Yeah, I don't use aries config, I used vibrant and renamed it to vibrantplus_antsvx_defconfig.
[Samsung Galaxy S (4G Model)] AntonX:
To avoid confusion - updated the config version to 1.0b4, rebuilt, and reuploaded. Nothing else changed.
[Samsung Galaxy S (4G Model)] ipaq_101:
Will give it a try
[Samsung Galaxy S (4G Model)] AntonX:
Update OP with v1.0b5.

Changed some code in OC/VU. The smooth ramping up for high frequencies is a little more correct now.

Made changes to cypress touchpad to fix race condition with BLN, used a mutex.

Two new governors. We should test them, they seem to work better.

Couple of other minor changes.

Report any issues!
[Samsung Galaxy S (4G Model)] Beastmode:
Nice work bro

Sorry to hijack ur thread but dies the phone reboot for everyone flashing the kernel?
[Samsung Galaxy S (4G Model)] 95Z28:
No reboots. Of course I didn't have any before flashing this kernel either.
[Samsung Galaxy S (4G Model)] Beastmode:
Sorry I meant does the kernel flash and reboot or does it flash and stay in cwm ?
[Samsung Galaxy S (4G Model)] iamperson347:
Reboots after flashing, I think FB knows how to fix.
[Samsung Galaxy S (4G Model)] Beastmode:
Thanks I was testing out his kernel on a rom and it doesn't flash it only 2.0bml by bhund flashes thru aroma.

Well sorry for the posts antonx
[Samsung Galaxy S (4G Model)] g4ry12:
I used SGS Kernel Flasher app, and if I unchecked the reboot checkbox the phone did not reboot after flashing.
[Samsung Galaxy S (4G Model)] FBis251:
I do know how to fix this.

AntonX, replace the redbend_ua binary you've been using in your zips with this one:

https://github.com/teamacid/valhalla-black/blob/master/updates/redbend_ua?raw=true
[Samsung Galaxy S (4G Model)] iamperson347:
Thanks FB.

As for kernel feedback, this smartassv2 governor seems snappier than the stock on demand, we shall see what it does in the long run with battery life. Hopefully it will do well since it's supposed to be a balance between battery life and performance. Thumbs up so far anton.
[Samsung Galaxy S (4G Model)] AntonX:
OK, will do for the next update. I don't really care about it, I want to reboot the phone after flashing anyway. This bug actually saves me some time ;) But I'll update.
[Samsung Galaxy S (4G Model)] AntonX:
Using Tegrak Overclock with OC/UV kernel

There is no reason to use Tegrak on natively OC/UV kernel if you don't intend to undervolt internal CPU voltages. It has its own proprietary module sitting on top of the kernel, who the heck knows what it's doing.

There is no good reason to undervolt internal CPU voltages. You will not gain much, there is not enough current draw there to make a difference. It's the CPU core that draws most current.

If you still insist.

Use the latest version of Tegrak.

Do not use SetCPU or Voltage Control and Tegrak Overclock together, they will fight with each other!

If you used Tegrak before with an older (not OC/UV) kernel, completely reset its data or uninstall/reinstall.

Setting up Tegrak with natively OC kernel is a little different. Before, if you wanted to OC, you would go and enable CPU Max Frequency, which would replace 1.0 GHz. Do not go there! The kernel already has all overclocking frequencies available. Instead set the Scaling to the highest frequency you want to use (let's say 1.2 Ghz, which is CPU Level 2.) Then go to Optimization and set desired voltages for the frequencies you chose.

Tegrak seems to have a problem with smartassV2 governor. If the scaling in Tegrak is set to use anything but all frequencies, including 1.4 Ghz, the governor will never lower the frequency from the highest selected. The kernel itself (with SetCPU or without) doesn't have this problem, it's happening only when Tegrak module is loaded. So either use any other governor or enable all frequencies.

Tegrak Overclock officially does not support custom OC/UV kernel. If you still want to use Tegrak, use it with no-OC/UV kernel.
[Samsung Galaxy S (4G Model)] Kyndig66:
Turns out that I am already doing exactly that with Tegrak. Plus I've had no problems with the smartassv2 so far... I'm on SCOMv4.4

Sent from my SGH-T959V
[Samsung Galaxy S (4G Model)] AntonX:
Can you try monitoring real time CPU with some program? I usually use free OS Monitor from market, it's on Misc tab there. Then try to set Scaling to 1.2 or 1.3 Ghz and see if the smartassV2 will let the CPU go to anything lower than that. On my pone it was stuck on the highest frequency. All other governors worked fine.
[Samsung Galaxy S (4G Model)] Kyndig66:
Today is a family day so I may not have a chance to. I'll let you know asap.

Sent from my SGH-T959V
[Samsung Galaxy S (4G Model)] FBis251:
For me it stayed on 1000/1200 for about 15 seconds before scaling down to 100 after I let the phone sit idle. I think that's the normal behavior of smartassv2 though, just ramping up quicker than ondemand. Mine isn't stuck on the highest frequency though.
[Samsung Galaxy S (4G Model)] AntonX:
Maybe it was something with my phone then. I tried several times, it was always stuck on maximum scaling if it was not set to 1.4. But once I moved scaling up to 1.4 the governor would start behaving normally again. I was not using paid app, maybe that's the reason. Do you have Tegrak module loaded? It's not required to only control scaling, so maybe you didn't load it?

I actually like smartassV2, it seems to work more intelligently than ondemand.
[Samsung Galaxy S (4G Model)] FBis251:
Hmm, actually I'm only using setcpu and I have the cap set to 1.2. I've never really liked that tegrak free automatically ups the voltage even though you're not using the higher fequencies.

My setcpu profile:

1200 max, 100 min, smartassv2.
[Samsung Galaxy S (4G Model)] AntonX:
I never liked tegrak myself. It's proprietary and actually every now and then I had problems with it loading.

Neither the kernel nor SetCPU (which just sends the values to the kernel) don't have problems with smartassV2. Only Tegrak's module seemingly does.

I'm running all the way to 1.4 Ghz but only for the sake of testing. I'll throttle it down a little eventually.
[Samsung Galaxy S (4G Model)] FBis251:
Yeah I'm planning on relasing a new build of vb today that will use your kernel and smartassv2. It's really handy. You can do it without even using setCPU/Tegrak

http://xdaforums.com/showpost.php?p=22903520&postcount=1
[Samsung Galaxy S (4G Model)] AntonX:
Yeah, I know. But for regular users it's easier to use SetCPU or similar, plus sometimes having it may help to temporarily bump the maximum if you're playing a CPU hungry game or something.

I've seen some ROMs that include SetCPU, although the developers are asking not do to that. ICS ROM for my Touchpad comes with it preinstalled.
[Samsung Galaxy S (4G Model)] hampsterblade:
Pushed you some changes that fix vibrate in MIUI ;P.
[Samsung Galaxy S (4G Model)] nazcalito:
I have Tegrak set at 1424 MHz. Os monitor says it is getting up to 1424. Odd thing though is that quadrant scores are down by 500 with betas 4 and 5.
[Samsung Galaxy S (4G Model)] hampsterblade:
Quadrant scores don't mean much, but if I had to guess, I'd say you're being slowed down by heat. OC can increase performance, but more speed means more heat, and more heat, means slower speeds. It's a curve. The optimum is about 1200, probably shouldn't go past it for any reason other than to say you did :p
[Samsung Galaxy S (4G Model)] m0bstr:
i just did a quadrant test and i got 2804
[Samsung Galaxy S (4G Model)] nazcalito:
Quadrant score is higher with beta 3 I should have said.
[Samsung Galaxy S (4G Model)] iHelper:
The scaling was also stuck at the Max for me without Tegrak only setcpu. To fix it, I basically set the Max and min to 1400 and then set it back to my previous settings and then it started working again.

-Sent From My Amazing SGS4G-
[HTC EVO 3D] robforself:
There are some people out there using windows 8 as a base computer even tho its just a preview/evaluation copy..

but HTC sync wasnt connecting when I tried it to just try it..

so basically this is just a thread with a link to the htc site.(if anyone needs or wants it)

I just glimpsed the threads and didnt see anything on it so I was bored and tossed it up.

if its already discussed feel free to delete this. just trying to help.

HTCl Link http://www.htc.com/us/support/htc-evo-3d-sprint/software-updates
[HTC EVO 3D] androidcues:
This actually installed on my Win8 64....

HTC Sync v3.2.10 for Windows – All Models

I was about to wipe this machine and go back to Linux Mint because I had a nice adb/fb setup there! Guess I get to stay with the WINdoze
[LG Optimus 2x] Najmuddin NP:
Re: [CM7/MIUI Kernel][KANG][APR18][NEW] ETaNa v3.0.y with Spica (c) OTF ToolKit

Am new to android so plz correct me if am wrong.

1.Does this kernel have any bugs?

2.And if yes which would be a stable kernel for cm 7

Am experiencing network drops and battery is acting kinda weird like one moment it will be on 90 and the other it will be 80 ( and yeah I have calliberated after charging it to 100% ). Is there anyone else with this problem.. sorry I didn't have the patience for reading this entire thread. ( sorry for my bad English. ) So please help..:)
[LG Optimus 2x] Pascalone19:
Hello I installed this kernel looks on cm7 and have not had any problems, bugs or viruses, is very stable and has frequent updates!
[LG Optimus 2x] DrummerMuppet:
From what I have read in that thread, that kernel has a bug that makes /system read-only. There's also a workaround to fix it, though.

Sent using some sticks and gum, just as McGyver would
[LG Optimus 2x] k101d:
Not for me I always can set R/W for /system this kernel work like a charm.
[LG Optimus 2x] Najmuddin NP:
But what does R/W has to do with battery level fluctuations.. network is kind of stable now. But the battery level fluctuations are occurring as usual. Am I the only one with this kind of weird problem ...:confused:
[LG Optimus 2x] Najmuddin NP:
Really good kernel.. that's what holding me back from flashing another kernel.. please some one help..
[LG Optimus 2x] Cydras:
Yes this Kernel is good, but he have the r/w issue...

Because that, i use the ETaNa 2.6 Kernel. He runs also very nice and have a good battery life :)
[LG Optimus 2x] Najmuddin NP:
Perhaps the DS battery driver was causing the problem with the weird battery readings... just flashed a kernel without it everythings back to normal.
[LG Optimus 2x] k101d:
Try to install new superuser from play store it solved my problem about system R/W.
[LG Optimus 2x] KittyCatCat:
I'm using Optimus X2 on CM9 now and I want to revert back to stock.

Problems I faced are unable to use front camera, camcorder and the camera freezing after a few uses and I have to restart the phone. :mad:

The build is great, but I just NEED the camcorder and front camera function. Call me stupid for not reading before upgrading (got my bro to upgrade for me on impulse) and now we can't revert to stock because the phone is not connecting to computer at all. :(

The phone can be connected by USB as a Portable Media drive but cannot be detected when drivers are used. :confused::confused::confused::confused:

This is driving me to wits end ): Even my brother couldn't get it to go back to stock after trying for an hour.. I just want to go back to Gingerbread 2.3.4 (came with the phone)

I need help guys. Desperate.

Thank you all so much in advanced. :)
[LG Optimus 2x] KittyCatCat:
Oh to add on, any solution that requires me to connect to the computer now doesn't work at all. Because the phone cannot be detected by drivers. Gah.

It's not that CM9 isn't good. I just really need the camcorder function.

):
[LG Optimus 2x] Mungulz:
You have clockwork mod installed I assume? (Not sure if you can even install cm9 without it but thought I'd check :))

Just go to the development section and find a stock ROM, and flash it using CM7. If your phone isn't detected in storage mode then transfer it over Wifi, software data cable is good for FTP, Airdroid has a pretty GUI and super easy to use.
[LG Optimus 2x] KittyCatCat:
Is there any way I can return the phone to baseband instead?
[LG Optimus 2x] KittyCatCat:
Hi there thanks for your reply.

I have CWM installed. How do I flash it using CM7? Omg I'm a total noob here. :/
[LG Optimus 2x] 75markus:
if you want to go completely to stock, you can use NV flash.

it contains stock FROYO Rom and recovery, you can flash a gingerbread ROM afterwards.

find it in my dropbox :

NVFlash : https://www.dropbox.com/s/phs3nab3seanzu3/2x-v10b-1300166062-nvflash.zip

drivers : https://www.dropbox.com/s/1j1j8fc1ljz85dl/2x-nvflashdrivers.zip

guide : https://www.dropbox.com/s/csz222gw3fut2wm/General NVflashGuide.pdf
[LG Optimus 2x] Marsou77:
You can download CM7 from your phone and flash it directly! With wipes of course

Sent 2X faster with my LG
[LG Optimus 2x] KittyCatCat:
Thanks for your reply. I see that you are hosting V10b. Mine is V20C. Would there be a problem??

Singapore:Starhub

Thanks will look into it.
[LG Optimus 2x] markop90:
ehm...just download the rom directly on your phone and then flash it via recovery!

Inviato dal mio LG-P990 con Tapatalk 2
[LG Optimus 2x] antec123:
nope it's okay, if you don't mind use smartflash but you will wipe all data back to normal again
[HTC Amaze 4G] ITALIANNYC:
I go to the quick settings and the total memory is 829MB.. 624MB used and 204MB free. There are NO applications running on the task manager. Is 204 normal or should I have more? If so, what should I do to get more?

Thank you
[HTC Amaze 4G] EclipzeRemix:
The task manager only kills some apps, the most ive had free is 689 and that was with CapRom, sense is a ram hog
[HTC Amaze 4G] ITALIANNYC:
Wow 689 free when on the task manager screen? I cant even get over 200mbs and dont have any real apps open accept facebook.
[HTC Amaze 4G] Ray196:
well in my experience with Energy Rom, Xboarder's roms and even ICS you always have around 350-440mb free when no running aything.
[HTC Amaze 4G] ITALIANNYC:
Well that makes sense. My phone is out of the box normal. I guess I need to start rooting it. I dont wanna run out of memory in the end while using apps.
[HTC Amaze 4G] Karmavore:
It says 830MB total. And with all my widgets i have 198MB free
[HTC Amaze 4G] realitysconcierge:
I've got 219 free. Having more ram doesn't affect anything unless you are running out. That's when stuff starts slowing down.
[HTC Amaze 4G] jimczyz:
428 here