yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] Theraze:
Not add the FReqs needed... remove them. It's the addition of custom frequencies that makes it stop working with Tegrak. If you read more in AntonX's kernel thread, you'll see that he actually released two versions, one without custom frequencies and voltage control for people who use Tegrak, and one with those features in for everyone else in the world. :)

But go for it... compile your versions and see if you can come up with something that works for you. Just be aware that AntonX's Tegrak version didn't have either OC or UV in it. I want you to be well informed and able to come up with a kernel that actually works for you. :)
[Samsung Galaxy S (4G Model)] hampsterblade:
Is there a reason I can't set 100Mhz min? I can't imagine that's good for the battery
[Samsung Galaxy S (4G Model)] raphifix:
From the original post under known issues:

"Minimum CPU speed permitted "randomly" changes between 100 and 200 MHz"
[Samsung Galaxy S (4G Model)] HB66:
Yea it changes, I have even changed via rom performance app. There is only a 25 mv difference. On 25 hours at 200
[Samsung Galaxy S (4G Model)] tichs:
Talking about frequencies, the max I have ever tested somewhat safe is 1.65Ghz OC on the device. Anything higher it crashes. the Hummingbird architecture clearly wasn't made to be pushed above 1.6Ghz Approx. I have tried 1.6Ghz and battery runs out in about 5 hours with a 3500mah battery.
[Samsung Galaxy S (4G Model)] jeffsf:
Hefe Kernel v0.8.1 Available

Thanks to Cedric, the author of System Tuner, responding amazingly quickly to a request for information on how his app handles setting voltages (and a completely selfless offer to compile and send me a version that logged everything so I could debug my problem), as well as Derek Xan, who publishes the sources of his Voltage Tuner, I was able to get both of these apps able to read and control the voltages properly.

This version has the same 25 mV off of "stock" as the previous.

No change in the installation instructions and can be installed over v0.8.0
[Samsung Galaxy S (4G Model)] rbedell:
Edit: this was before under volting. I just got used to setcpu. Changed my scheduler to noop after updating kernel and I am truly undervolted... I'm excited for results! :D Sry guys for posting false stuff, they should be way better lol. :D

Aokp M6.3

Oc'd at 1.2, BadassV2 governor and cfq scheduler... ultra smooth with no rrboots. Didn't use the built in power saver from aokp and still got amazing results. I am getting too tired to really see how much further it would go. Thanks again for your epic development. :)

sent from The Backwoods in South Texas
[Samsung Galaxy S (4G Model)] bhundven:
Have you tried using noop or deadline instead of cfq?

http://xdaforums.com/showpost.php?p=22134559&postcount=4
[Samsung Galaxy S (4G Model)] CSOS:
I just want to give you a "THANKS" and a heads up for working , integrated into CodenamedAndroid.....1.4GHZ OC..FIRST ever...., more test needed but I am working with him right now.
[Samsung Galaxy S (4G Model)] FBis251:
Just wanted to tell you that the install worked. Wifi works for me, but I tried mounting /system by hand before this, though I didn't test to see if the old lib got overwritten before I attempted this. At least I didn't have to push anything by hand.
[Samsung Galaxy S (4G Model)] hechoen:
NOOP there it is. Seriously though Bryans right about using different schedulers. I've always had better performance with noop then deadline then CFQ.

Jeff

Thanks for getting with the System Tuner boys. That's always been my go to for anything CPU related and it's nice to have it back. Also have you heard of Wheatley?

http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__90#entry405813
[Samsung Galaxy S (4G Model)] rbedell:
Wow. Good god, the rom is at least 2x as fast with noop. I'm testing the battery life today, starting now. I might be getting good results partially because half the day I'm on edge because of the country and I work in the city with 4g.

sent from The Backwoods in South Texas
[Samsung Galaxy S (4G Model)] jeffsf:
No, I hadn't! Looks interesting and I'll try to understand what he is trying to accomplish.
[Samsung Galaxy S (4G Model)] doc_v15:
Using your kernel on cMIUI 2.8.10 and it causes bootloop everytime

When i changed the governor to smartassV2..

Any clue?
[Samsung Galaxy S (4G Model)] jeffsf:
Hmmm, I'm guessing something in the cMIUI boot sequence is not handling the smartassv2 governor nicely. How do you have it configured to re-set the governor from the kernel default? Is there a feature in cMIUI, or a thrid-party app?

You can try to catch logs, even in a boot loop, if you have a computer with adb installed. With your phone off and unplugged, you can open a couple of terminal windows ('Nix, Mac, or Cygwin on WIndows) and run

$ adb start-server

then run

$ adb wait-for-device && adb logcat

in one and

$ adb wait-for-device && adb shell cat /proc/kmsg

in the other.

Power down your phone, boot it, then plug it in as soon at it starts to come to life. The windows should start spewing when the kernel loads and starts the other end of adb. This is usually around when the boot animation starts (T-Mo splash, kernel splash, then boot animation).

I apologize that I don't know the equivalent if you're on Windows without Cygwin.

(I want to say that you can do this with your phone plugged in under Linux, but it wouldn't recognize the device just now using Cygwin if I booted it with it already plugged in.)
[Samsung Galaxy S (4G Model)] Theraze:
Equivalent on Windows w/o Cygwin should be single &, not double. Single & means to do another command-line command. Example:

dir C:\ & echo Done!

Displays C:\ drive and prints Done! to screen after it finishes.
[Samsung Galaxy S (4G Model)] turtlepa:
This allows for oc settings in gummys settings without use of an app, nice
[Samsung Galaxy S (4G Model)] htaak:
This Kernel is running very smoothly with cmiui. I am using No Frills CPU app, OC'd at 1.4 with noop and this phone is like butter. No reboots or bootloops since flashing it the day it was posted.
[Samsung Galaxy S (4G Model)] doc_v15:
I am changing the governor using NSTools by Arifhn, he made it exclusively for Nexus S, Galaxy S and Galaxy Nexus..

I have been using it on any SGS4G rom :)

I will try to provide log cat

Thanks for the response man! :D
[Samsung Galaxy S (4G Model)] jeffsf:
If the fix isn't quick (and I suspect it is a ROM / NSTools issue), you might want to try System Tuner. I linked the Pro version as I have always found the author very responsive to questions and issues with his app. I would try the free version first, to make sure it works for you.
[Samsung Galaxy S (4G Model)] doc_v15:
Will try it tonight! Thanks man
[Samsung Galaxy S (4G Model)] cyrixke:
I have this kernel running with codename android 2.0, but can't seem to get bln working anymore. This is what i get in my bln control pro:
[Samsung Galaxy S (4G Model)] jeffsf:
Your image is "broken" -- also a logcat would help. What do you mean by "not working?" What do you see (or not see)? What did you expect instead? Can you replicate the issue?
[Samsung Galaxy S (4G Model)] tichs:
here is a cpu-freq.c modified for the ones who like to compile their own kernel. It has some frequencies added and tweaked. 1.5Ghz, 1.6Ghz. and 1.7Ghz which is only for benchmark and experimental
[Samsung Galaxy S (4G Model)] theoctavist:
works brilliantly with AOKP!

good work man!
[Samsung Galaxy S (4G Model)] bhundven:
A little warning to attach:
[Samsung Galaxy S (4G Model)] jeffsf:
Without malice, please note that this may work with the source of Hefe Kernel v0.8 but your results may vary, including irreversible damage to your phone. (See also the warning on overclocking to any level in the OP.)

Patching like this is not for a casual "flasher" and should not be attempted without knowledge of the architecture and code of the SGS4G.​

Additionally, these patches likely will not work (nor will Tegrak) on later versions of Hefe Kernel or other kernels that do not use the same clocking tree as the current 2.6 line.
[Samsung Galaxy S (4G Model)] jeffsf:
Update on the "100 MHz" issue -- Even though the low-end number fluctuates with time, it looks like my phone does use 100 MHz a reasonable amount of the time. I unplugged my phone around 11 PM last night, used it "like normal" during the day, and took this screenshot around 9 PM tonight. The phone hasn't been on charge all day. (I'm not bragging about battery life, just setting the stage about how I used my phone.)

You can see the phone using deep sleep most of the time. During the "awake" times (which may or may not be screen-on time) you can see that 100 MHz was used more than any other frequency.
[Samsung Galaxy S (4G Model)] doc_v15:
Sorry for the late report, i uninstalled NSTools and installed System Tuner, and the smartassV2 governor works like charm! :D

Thanks man!

And oh yeah, I agreed with you about the phone uses lots of lower frequency (100mhz, 200mhz) I must confirm the battery life on the newest version is way better, added 10hrs more life time of my general 10hrs usage :D
[Samsung Galaxy S (4G Model)] jeffsf:
Glad it is working out for you. When I drag myself off Aries for a while, I'll take a look at NSTools to see what I can do to improve the compatibility.
[Samsung Galaxy S (4G Model)] SilverL:
NSTools reads the ARM and Int voltages from the table created in cpu-freqs(ithink).
[Samsung Galaxy S (4G Model)] doc_v15:
Hey jeffsf, while you are developing this awesome kernel, do you mind looking this post as your reference in making your kernel even better?

I am using this this kernel on my Nexus S with MIUI rom, and it could last for 24hrs++ with medium usage and with smartassV2/deadline

When I'm asleep, the battery only cost 1% for 8hrs of sleep!

So this guy name Bedalus, before he made a kernel called Marmite, he did a hell of research of kernel and stuff

Well, I could go really long, but give yourself a minute to read his script

Hope that it could make our SGS4G "alive" once again :)
[Samsung Galaxy S (4G Model)] jeffsf:
"Hefe Kernel Of Darkness" now available -- see Post #2 in this thread.
[Samsung Galaxy S (4G Model)] getochkn:
wifi doesn't work or even let me turn it on in options after installing KOD. Reinstalled my backup I did right before KOD and wifi is right back connected, so it's not my phone.
[Samsung Galaxy S (4G Model)] eollie:
I would go out on a limb and say its probably the wifi module.
[Samsung Galaxy S (4G Model)] gizmoscoop:
Did you take down the download link, can't see it?
[Samsung Galaxy S (4G Model)] jeffsf:
Yes, sorry -- There was/is an issue where the touchkeys themselves get disabled, which was not the intended behavior. Apparently there have also been issues with the WiFi kernel module not installing properly. Rather than put people through hoops to get back to a working phone, or, worse, leave them without one, I took down the link until I have a bit more confidence. I apologize for posting the kernel prematurely.
[Samsung Galaxy S (4G Model)] getochkn:
I liked the touchkeys not working. lol. I want them disabled and it use the softkeys in AOKP instead.
[Samsung Galaxy S (4G Model)] jeffsf:
See how you like Hefe KOD b2. I left the touchkeys working for those that want to continue using them, but without the annoyance and/or battery drain of the backlight.

This time I bundled the WiFi module ;)
[Samsung Galaxy S (4G Model)] pisherthefisher:
Awesome job, it works great on eriks miui. The key lights flicker only for a split second when pressed and are no longer turned on when pressing the power button when the phone is locked. It's like they're not even there. :good:

EDIT: It looks like this kernel makes it no longer possible to long-press a button. It isn't really a big issue, I simply re-mapped my search key to become the multitasking button. Perhaps making the soft key presses register for a few seconds longer will fix it?
[Samsung Galaxy S (4G Model)] farmerbb:
Getting the same behavior here. This means it's not possible to access things such as the recent apps menu.
[Samsung Galaxy S (4G Model)] gizmoscoop:
Is there a fix to this? I still want to use my recent app opener.
[Samsung Galaxy S (4G Model)] jeffsf:
Hefe-KOD-b3 only turns off the backlight on touchkey-release. It should resolve many of the issues.
[Samsung Galaxy S (4G Model)] farmerbb:
I can confirm that long-pressing the softkeys works perfectly now. Thanks!
[Samsung Galaxy S (4G Model)] gizmoscoop:
I installed into remisc, and can't turn on wifi. It stuck at the loading screen.
[Samsung Galaxy S (4G Model)] jeffsf:
Try re-flashing. Have you used a version of Hefe on Remics before without the Wifi issue?

Also, check the Q&A thread for both Hefe Kernel and Remics in the Q&A section.

Posted from my SGS4G, thanks to Team Acid development
[Samsung Galaxy S (4G Model)] gizmoscoop:
There is no wifi issue with original remics. I am using it right now with hefe kernel. I'll give it another try with this kod version.

---------- Post added at 06:29 AM ---------- Previous post was at 06:16 AM ----------

Great. Reflashed kernel got wifi working again. This kernel makes remics runs smoother. No stuttering.
[Samsung Galaxy S (4G Model)] bot42:
I have only had Wi-Fi problems with heffe only when I installed it and the ROM at the same time. I found that if you flash the Rom and gapps the boot to the system let it soak, sign into your Wi-Fi then flash heffe that problem doesn't occur. This worked for KOD as well.
[Samsung Galaxy S (4G Model)] jeffsf:
I've just seen the same thing myself where if flashed in one step (ROM, gapps, Hefe) the Wifi driver doesn't update So much for the robustness of Edify. Seems like it's time to write the installer as a shell script.

Posted from my SGS4G, thanks to Team Acid development
[Samsung Galaxy S (4G Model)] getochkn:
I've found the stacking zips doesn't always work properly, so I just install 1 by 1 or reboot in between, which is better anyways. If you stack 8 zips and flash them all, and something doesn't work, it's hard to know which one did it.
[Samsung Galaxy S (4G Model)] FBis251:
It might be the old overwrite bug from the GB kernels. I guess that's why we moved toward shell scripts with CM7/9 and I started adopting that in aroma. :D
[Samsung Galaxy S (4G Model)] bot42:
Well the easiest temp fix might be just to add a warning to the OP, to flash on a soaked in ROM.
[Samsung Galaxy S (4G Model)] Theraze:
Or just noting there that if you're missing wifi, reflash. Since that fixed mine this morning. Whether it's soaked in as broken-Hefe or soaked in as stock-whatever, both are fine to flash into.
[Samsung Galaxy S (4G Model)] Shortbus-Driver:
+1 I've found this to be true
[Samsung Galaxy S (4G Model)] eollie:
I think the main purpose of stacking zips is so you can install the rom and gapps together.
[Samsung Galaxy S (4G Model)] jeffsf:
Looking at my Edify updater script, it looks like I don't explicitly mount /system/ -- if a previous script unmounts it, unless package_extract_dir("system", "/system"); mounts it, then the kernel modules wouldn't be installed to the right location.

I did look at the lead posts and they already did identify it as known issue, but I did add a bit about re-flashing if there were WiFi problems.

Thanks for the feedback. I'll work out something with my installer to make it more robust.
[Samsung Galaxy S (4G Model)] bot42:
Well I don't think there's a problem with stacking ROMs, but on the same note just because twrp allows you to stack 10 doesn't mean you should.
[Samsung Galaxy S (4G Model)] FBis251:
I always blame the updater scripts. We had that problem with rom authors back in the day who insisted users set mounts (ummu) instead of trying to fix the problem themselves. I had originally planned on making a universal updater script for all roms but that wound up becoming the aroma installer. I'm glad it turned out that way because everyone adopted it.

Anyway look through the updater script in github. There are a lot of goodies in there. ;).

I would hop on irc but I'm not gonna be home for a while
[Samsung Galaxy S (4G Model)] jeffsf:
Now you tell me! I've got I don't know how many lines of sh-script already written this morning!!!
[Samsung Galaxy S (4G Model)] FBis251:
Haha. It should be under sgs4g-installer
[Samsung Galaxy S (4G Model)] jeffsf:
Hefe-KOD-b3a.zip now up. It is the same kernel and module, but has a new installer that should resolve the issues with some flashes not properly writing the WiFi module.
[Samsung Galaxy S (4G Model)] getochkn:
Noticed a weird problem with the KOD. I used Dell voice for wifi calling and when I'm on a call and the phone is close to my, it should dim the screen but it fully blacks it out and it won't come back on until I pull my battery. Reflashed a different kernel and the problem went away.
[Samsung Galaxy S (4G Model)] jeffsf:
If you can easily replicate it, you could start logging /proc/kmsg and logcat to files on your microSD. They might provide some clues and will be there after the hang.

# cat /proc/kmsg > /mnt/sdcard/kmsg log &

# logcat -v time > /mnt/sdcard/logcat log &

Is it that it completely freezes, or just the display in non-responsive? You could check with adb after it freezes.

Posted from my SGS4G, thanks to Team Acid development
[Samsung Galaxy S (4G Model)] turtlepa:
I flashed the hefe mod kernel and tried installing blastoff and it says it flashed correctly but when I reboot it still shows hefe.
[Samsung Galaxy S (4G Model)] lumin30:
Blastoff is BML.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
Hello all, typical noob here.

I tried to install cyanogen 9.0 on the phone(st15i)

i followed this tutorial(at cyanogen wiki) and everything went fine up to :

then when I try o power on the phone, It won' get turned on no boot screen(battery level was full ), I tried pressing the volume buttons, while pressing the power button, no use. I can feel the vibration while holding the power key. Can any one please help me out? I tried reading some threads and tried few stuff, still no use.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
Is your Bootloader unlocked? Because if your Bootloader isn't unlocked ( official method by Sony or tespoint method) you can't Flash the custom Kernel and it won't work.

Have you flashed the Kernel or Not?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
yes, bootloader is unlocked(Sony method) , and I flashed the kernel(should i post any screen shots? I used fastboot)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
Maybe Flash Sony offical Rom again (Flash Sony Kernel and then Sony official gingerbread Rom). Then try it again.

And you are sure you performed all steps of the tutorial? And everything went really fine?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
I'm downloading official rom now. will let you know the result.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
But remember to download the official kernel from sony, too! And flash the kernel and then flash the ftf file from the rom!

And then reinstall cyanogenmod. But I'm not sure if this helps anything...

Could you post the link from the tutorial?

Did it work?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
the phone's now back to gingerbread, official rom worked
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
Then you could try it again. I don't know now if gingerbread is right, cause the cm9 rom is ics, right? Sorry but I don't know if you should root and update to ics and try it then!

Which rom was installed as you tried to install cm9 first, as it didn't work?

Could you pls post the tutorial from cm wiki?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
They won't let me post the link

I was running ICS earlier . Guess I need to update now
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
Don't update over the air, or your phone will brick!!

Why won't they let you post the link? I don't know if it is against the forum rules, but hmm...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
FIRST READ AND THEN CHOOSE IF YOU WANT TO TRY IT ON YOUR OWN RISK!

Do it like in this tutorial. But download the files from here. Then extract it, so you have got 1 packed and one extracted foler.

Then install sony flashtool and go to the flashtool installation folder on your pc and make a new folder "kernels". Then copy from the extracted cm9 folder the boot.img to the kernel folder of flashtool.

The packed package of cm9, you put on your sdcard. Then you open sony flashtool, click on the flash, choose fastboot mode and go to your created kernels folder and choose the boot.img. Make sure it is named boot!

Then connect phone in fastboot mode (volume rockers up and connect usb to pc. It will automaticly flash the kernel you have chosen.

SEE THE LOG BEFORE YOU PLUG OFF THE DEVICE!! If everything in the log is right, you can turn your phone on. When the "Free xperia project" screen comes up, you press volume down again and again, until clockworkmod comes up.

When your are in cwm just do it like in the tutorial. (Wipe data/factory reset, wipe cache partition)

Then choose "install zip from sd card" and choose zip from cm9. Click yes and it will automaticly flash it. DON'T TURN OFF DEVICE WHILE THE PROCEDURE! Then, when it is ready you can startup your device.

I DONT TAKE ANY RESPOSIBILITY AND I'M NOT SURE IF IT CAN WORK (just installed it like this on my xperia mini pro)

Greets and keep up! In the end you will experience cyanogenmod 9!!

Michael
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
It's something related to minimum post . Well ... I guess CM9 kernel hat I downloaded might be corrupted.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
But does it work now? Cause with the method I posted before and with the files I posted it should really work. Cause I tried it on my mini pro, the files and kernel I posted is for your xperia mini :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ss192:
I installed CM9, works fine now.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] umair928:
thanks for sharing!:good:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] light19940120:
i have 3.8.16
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Sparksys:
Why the play store doesnt get auto updated ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] iPusak Gaoq™:
Your Welcome My Friends :highfive:

That's Gud For You :D

I don't know...last auto update for play store is v3.7.15...that why i uploads the latest play store here so everyone can update it them self :p
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] iPusak Gaoq™:
Latest Google Play Store Update v3.8.16 on OP ;)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] E43JAP:
View attachment 1269546

Mine still looks the same.

Maybe this is just for Sony phones?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] shyam4ever:
My google play auto update is 3.7.15 then auto update stopped. I download the 3.8.15 version from here and now I again get the auto update 3.8.16
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] john9:
Thanks for your contribution .will give it a try.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Sparksys:
How you can get them ?? :P the latest versions of play store ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jose385:
thanks for sharing and providing :good::victory:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] agoescivil97:
Can't be installed in my phone..it says that the same program name has already installed in myphone...please help me to solve this problem...thanks in advance...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] iPusak Gaoq™:
Please check your Google Play Store with version is it currently on....there shouldn't be any problem install this Store since it is compatible with all phone....
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] agoescivil97:
My Google Play version is 3.7.13...still can't instal with the new one...please help me again to solve this problem...many thanks before...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] iPusak Gaoq™:
New Version (v3.8.17) Have Been Uploaded In OP :highfive: