yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] sixstringsg:
To everyone with issues flashing B2: it is always good practice to match the build date of your kernel with your ROM as best as possible. This is especially true on beta ROMs, where things are changing so constantly. The only people with issues are on build 14.
[Galaxy S I9000 Android Development] Doctor Phate:
Looks like the kernel's dev doesn't agree :rolleyes:

I've just reported (badly, sorry for that) what I've read.

Sorry for the OT, but since I'm going to test this kernel too, I shall ask if it needs the modded framework too ;)
[Galaxy S I9000 Android Development] lippol94:
I'm sorry but I'm on build15 and I got bootloops after flashing Beta2.

had to go back to Preview5 with Heimdall, deleting NStools settings and flashing via CWM Beta2.

It worked :)
[Galaxy S I9000 Android Development] zadock:
Flash on build15 whitout problems here.
[Galaxy S I9000 Android Development] rugal28:
awesome & fast great kernel,

but i had one problem for B2

when go to CWM mode

in install ZIP monitor

i have lots of folders and file,

it cause cut off picture, lose bottom information:confused:

every thing is perfect, except CWM problem :D

sorry my bad english ~"~
[Galaxy S I9000 Android Development] Wendigogo:
Great kernel here (Beta 2) !

About Dock Audio, is it supported (audio usb) ?

Does it needs an app (like "Galaxy Dock Sound Redirector" with GB patched kernel) ?
[Galaxy S I9000 Android Development] zadock:
What's the finaly of call volume hack?

It's too high :confused:

Regards.
[Galaxy S I9000 Android Development] st4rk:
Yup I agree something seems off with call sound, people on the other end of speaker phone say it sounds really bad. And earpiece level is so high its almost like speaker phone.. lol

That's my only issue so far though.

Sent from my brain to my hand to my SGS to the internetz!
[Galaxy S I9000 Android Development] sixstringsg:
The voltage table changed, which can cause all kinds of odd things to happen.
[Galaxy S I9000 Android Development] sixstringsg:
From what I've seen we didn't touch anything that would break it. What ROM are you on?
[Galaxy S I9000 Android Development] .:Crack:.:
CM9 b15

the scripts worked on b1..

+ zipalign script won't work
[Galaxy S I9000 Android Development] Tk-Glitch:
I'll look at this, thanks for the report.
[Galaxy S I9000 Android Development] Doctor Phate:
Wall of code! Greetings from xda app lol

Sent from my GT-I9000
[Galaxy S I9000 Android Development] yuri76:
with the B2 I freeze problems and spontaneous reboots
[Galaxy S I9000 Android Development] DaXmax:
Hey, anyone has buggy recovery? From below u cant see any listing?

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] sixstringsg:
We know its happening, but not why. Its being worked on.
[Galaxy S I9000 Android Development] DaXmax:
Will wait for the fix... :/

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] Sharken:
Team Hacksung B15 + Glitch Beta2 = Works

Had problems with bootloop when flashing B2 over TH Build 14.

When i flash TH Build 15 and then Glitch B2, the bootloops is not present.
[Galaxy S I9000 Android Development] He4dShOt:
Sometimes a got a popup telling that the sim card was removed...i don't know if is kernel related...but it never happend before flashing B2...
[Galaxy S I9000 Android Development] m4ssnet:
yep really bad bug, recovery doesn't show the entire .zip lists in your sd card, my galaxy scream for install that scripts/mods :rolleyes:

EDIT: Last bad news -_-'

I think I soft-brick my SGS1, bootloops and not enter in recovery... I think I can only download mode wipe super reset only !!!! This is really bad for me !!!

For know to you all, as I can't flash the zips files directly to recovery, I've used the rom manager with multiple .zips, and ZAK, after flashed them, bricked :(
[Galaxy S I9000 Android Development] Bavaria85:
It's fixeable. You need to flash recoveryfix.tar or something like that. I dont have this file myself but i have used it before. I had the same problem as you, i couldnt get into recovery but download mode still worked. After i flashed the fix recovery through odin and flashed a full rom everything worked again.

Good luck anyways. Maybe someone else can give you the file i mentioned.
[Galaxy S I9000 Android Development] spoonymoon:
I really like Glitch Kernel's and tried all versions several times on different roms different setups ... but always ends the same way NO CWM available reboots freeze :eek:

And i don't even bother try this, wats the purpose??? posts talk for themselves..

At the moment there is only one proper ICS kernel and that's the Devil :D

That's a h... of a good job the Devil makes - THX buddy
[Galaxy S I9000 Android Development] Tk-Glitch:
Make sure you have GB bootloader, as DIDLE can't be disabled and requires it to work.

You can try to lower Int voltage for 1GHz to 1.10V as well.

Ho and if you are overclocking then go find stable settings or don't oc.

Also, random reboots are a known ROM issue btw.

Devil's kernel is based on Glitch. Now let me laugh a minute or two.

Oh but wait.. Isn't it Glitch kernel thread here and not Devil's ?
[Galaxy S I9000 Android Development] fishcake13:
from my experience i've only had bootloop when i flashed glitch with face unlock installed... without face unlock everything is fine....

could you have look into this TK? might be something in the face unlock files?
[Galaxy S I9000 Android Development] Tk-Glitch:
I'm using a fix for the camera that *could* *possibly* interfere with faceunlock. Anyway why anyone would use that thing ? It's slow, buggy, not intended for the poor ffc of the SGS, and doesn't work at all in low light.. Let alone that you look stupid trying to get the "unlock pose".

Anyway it does look strange to me and I'll verify that. Thanks to have pointed something to look for, unlike 90% of the posters.
[Galaxy S I9000 Android Development] JJustin:
for the random reboots problem some people are having, have you tried taking a look into the nstools app and check max frequency? when i first flashed beta2, i was having random reboots but then noticed it had overclocked itself to like 1500 mhz, something my phone can't handle.
[Galaxy S I9000 Android Development] sixstringsg:
Between new kernels always uncheck set on boot in NsTools. This version is a perfect example. The voltage table changed, so nstools got all screwy. Also, never assume that your old voltages will still work on a new kernel.
[Galaxy S I9000 Android Development] JJustin:
Just wondering if the lmk settings have changed in this kernel? On ths 14 and glitch beta 1, I used to always have over 60mb free ( smooth even after days of use without reboot). On ths 15 and beta2, I sometimes have less than 50mb free, causing some lags once in a while. Are lmk scripts like thunderbolt recommended? Thanks
[Galaxy S I9000 Android Development] Gage_Hero:
Op Page

Just gotta say.... love the big red letters on the OP lol.... perhaps people will get the point :P
[Galaxy S I9000 Android Development] wogfella:
You mean people post bug reports and don't actually give you information other than "it doesn't work" ?????:confused::confused::eek::eek:

Just to say: Never used face unlock (too ugly and don't want to break the camera) and the only times I have experienced wierd sh*t with ICY Glitch kernel was in the "early days" of THS ICS....ie, when the thing rebooted by itself because it didn't like Monday's, not because the kernel was iffy.

As a result I bought your donation app - just to show the love. I deleted it after downloading, of course, because it doesn't work properly with ICS :p

TK can you increase the font size? I don't think it's big enough :D
[Galaxy S I9000 Android Development] spoonymoon:
Laugh all you want, but my phone dosent reboot :rolleyes:

I have GB bootloader Overclocking only to 1200mhz no voltage change at all, default used - but always same result - i never have reboots with other kernels even if its a ROM issue.

Always ends with no way to get into CWM

And yes its maybe the 'wrong´ thread but aren't we allowed to express our comparison's ...or what?

Not my fault your kernel is so unstable...

Some people just don't like the truth :p
[Galaxy S I9000 Android Development] DaXmax:
Umm bro, can i tell u something... Glitch kernel is so stable like a fresh strawberry which has been picked from the tree.... The reason u having this problem is: U need a full wipe of the kernel... It happens to me once get it? The only problem is your spamming this thread too much...

Short word: The kernel is stable, look few pages back, how they made the kernel work...
[Galaxy S I9000 Android Development] acras:
Which multiplier is used for this step? 1160/200=5.8?
[Galaxy S I9000 Android Development] Tk-Glitch:
Truth is that you don't know anything about how your phone actually works, let alone overclocking it. I'm running 1.5GHz for a year on all my kernels with no stability issue, and many of my testers and users can say the same. If you can't even get 1.2 stable (a useless bump btw), you're clearly just a big noob and you shouldn't even try to overclock your phone.

About Devil's kernel, express your preferencies if you want, I don't care at all. But thanking him here is like spiting on my shoes, as he will probably never see it anyway. Learn to respect other's work and time passed for free on this. When you know it's using my kernel as base, that's just more of a stupid move from you. You wouldn't have devil's kernel to play with if glitch wasn't there. Time will come when you won't get anything free from the community anymore, and you'll regret to have been such a douchebag with devs.

You have nothing to do on XDA man (or young boy, most likely).
[Galaxy S I9000 Android Development] DaXmax:
Steady bro, your blood pressure might rise up... ;)
[Galaxy S I9000 Android Development] hs911:
how can i make sure for this?

anyway: thank you very much for dock audio support!! going to flash as soon as onecosmics rc4 is ready for download again.
[Galaxy S I9000 Android Development] DaXmax:
Im not so sure with the support for onecosmics... I guess this kernel supports only for cm9 but partially supported on onecosmics...
[Galaxy S I9000 Android Development] spoonymoon:
:o Dear Glitch

I have loved your kernel for a long time now!

It surely was not meant as disrespect to you and your team..

I apologize sincerely.

Respect from here!!!
[Galaxy S I9000 Android Development] hs911:
afaik dock audio is only kernel-dependant. i will give it a try and report here. generally, the glitch kernel works fine with onecosmics what i saw in the past.
[Galaxy S I9000 Android Development] Tk-Glitch:
- Accepted -
[Galaxy S I9000 Android Development] pl4cid:
Hey, sorry for asking this here. I already asked in the appropriate custom voltage thread but no answers yet from devs, so again:

Would you be so kind and tell us more about your settings for 1.5ghz?? The best stable clock I can get is 1.32 at 110%. Can you give us more information especially voltages and bus speed? This would be very helpful for the community, I think many of us are anxious to get this awesome kernel to the edge and some 'personal' settings directly from source might be very helpful.

I know each phone is different but it could be a reference for everybody.

You really do a formidable job on this! Hats off!
[Galaxy S I9000 Android Development] Doctor Phate:
Someone already asked this, but a clear answer hasn't been given yet:

About the in call volume hack: my experience is kinda bad, I hear a really distorted sound both if I have high or low volume (on low the audio is still distorted, just more quiet).. and I don't have to use a bluetooth handsfree device, with that it's even worst.

I tried to remove the 90call_vol script from the init.d but the problem does persist.

I also tried to tweak dsp manager values (even freezing it) but things don't seem to change at all.

So here's my question: do I do something wrong or it's just a bug and you're aware of the problem? Yet, can I do anything to keep the B2 kernel (way more stable, gratz!) but with the B1 audio?

Thanks in advance ;)
[Galaxy S I9000 Android Development] .:Crack:.:
Hey Glitch,

I have to report a pretty severe bug I found...

When trying to OC you sometimes get freezes which lead to reboots!!

hah. (funny.) thats obviously not the bug :D

So if it's started up again it obviously reboots again as soon as NSTools gets loaded.

But: If you take out the battery in order to start into recovery mode, you can't get into it, further you get a "soft-brick", i.e. the bootsplash (white Galaxy S) is shown, then the kernel splash, then it stays there a bit until it "reboots" to bootsplash and all starts over again.

I have to flash another kernel via heimdall then and reflash B2 in CWM. Pretty stupid if you don't have a PC around -.-

Or am I doing any mistakes?
[Galaxy S I9000 Android Development] purpleraintoxicity:
So I've decided to come on board too.

great work.

2 questions:

1. I get 1000 lock on every governor I try, from time to time.

2. As much as I understood we hand the deep idle which enabled by default and we can't see the states as before.

Is this ? Cause if not, I got problem haha
[Galaxy S I9000 Android Development] st4rk:
Seriously glitch, build 15 stock was good battery wise, but your mods take it up a notch!

Sent from my brain to my hand to my SGS to the internetz!
[Galaxy S I9000 Android Development] cba1986:
How are the bus frequencies on b2?
[Galaxy S I9000 Android Development] Tk-Glitch:
@ :Crack:

It does really depend of how / when it did crash. You have a 'wipe NSTools settings' in recovery if you can't boot with your OC settings, but yeah, if your system was somewhat corrupted you may be unable to get into recovery at all. It does happen on stock kernel as well so our great CM9 devs will probably fix the issue at some point. For now, the best is to uncheck the 'set on boot' option in NSTools and experiment with OC only after the system is completely booted (let it settle down for 5 minutes). Once you find good and stable settings, check set on boot again.

I'm not satisfied by the frequency table in beta 2 btw and it'll change again in beta 3. It's not as stable as before, and it's harder to find the sweet spot.

My settings are as follow for 1512 MHz OC :

- - - -ARM- - -Int

1300 1.450 1.200

1160 1.350 1.175

1000 1.250 1.150

800 1.150 1.125

400 1.000 1.100

200 0.900 1.100

100 0.775 1.000

Frequency table and dividers for OC steps on B2 are as follow :

1500 - 7.0 - 214MHz bus

1400 - 6.8 - 206MHz bus

1300 - 6.0 - 217MHz bus

1160 - 5.8 - 200MHz bus

About call volume hack, yes it's a bit hard to tweak so expect a better experience in the next updates, I'll do my best as always. You aren't doing anything wrong, it's just not that good as it is for now (especially on gsm phones).

Yes DIDLE is enabled and it's not possible to disable it, and you can't see stats for it as it's not Ezekeel's implementation anymore. NSTools will only react to his implementation of DIDLE, so it's absolutely normal it has vanished from it. You will need GB bootloaders to prevent instabilities with it. I may end with a custom implementation NSTools will recognize just to be able to disable it, because some phones are unstable with DIDLE enabled.

If you get some occasional freezes @ 1GHz with no uV, then lower the Int voltage for it to 1.10v instead of 1.125.

Some VERY sensitive phones are stabler this way.

All the best guys.

EDIT : Added Int voltages to my settings & quick note on 1GHz freezes
[Galaxy S I9000 Android Development] cba1986:
Thanks for the info.

By the way. Oc is more stable for me now. i can use 1400 without any trouble. But i try to keep away from live oc. It freezes at any value.

The most stable for me is 1300. Rock solid.

1400 also but the diff in benchmark doesn't justify the extra battery juice.

Best ICS's kernel out there.

Great work!!

EDIT: n00b question.

Those voltages are ARM or internal?
[Galaxy S I9000 Android Development] trailblazerz11:
After a couple days playing around, have to so this kernel is crazy smooth. best governor for me is smartassv2.

I leave stock voltages and have been increasing liveOC 1% everyday til it starts getting unstable. On 113% as of now, shall see when it gets to be too much.

Battery is best I've had on ics too
[Galaxy S I9000 Android Development] senotrius:
I don't use live oc but the oc values of beta 2 are not stable.beta 1was stable1440,1304. .

also nstools seems to stop responding every now and then.I get that message to close or wait.I use setcpu app only btw.
[Galaxy S I9000 Android Development] DaXmax:
This is my settings and i dont use LiveOC to get 1.5ghz stable...

1500/200 lazy/fiops

Max Volt/1.475V

1500/1.450V

-------------------

Int Volt

Max/ 1.225V

1500/1.200V

1400/1.175V

1300/1.150V

1200/1.125V

1100/1.100V

800/1.075V

600/1.050V

400/1.025V

So all steps down to -25mV

IMDriving...
[Galaxy S I9000 Android Development] purpleraintoxicity:
After one day of usage this kernel, for the first time, its amazing and solid.

17 hours and down by 50%, while wifi on and I'm using it.

Great work!

Although I got to say t that the second kind of didle was better to me
[Galaxy S I9000 Android Development] cink40:
BLN pretty, pretty please...CM LED is not working for missed calls (i know that for some is working, but for majority not).
[Galaxy S I9000 Android Development] cba1986:
On what freq are you applying live OC?
[Galaxy S I9000 Android Development] Tk-Glitch:
Looks near useless to me to use 1.5Ghz step as is. Bus is so slow man.. Plus your voltages are very high for this low bus. I'd be unsatisfied if I was you :P

LiveOC will affect all frequencies at the same time.
[Galaxy S I9000 Android Development] .:Crack:.:
Oh, I forgot to add a second way it happens sometimes:

it actually boots normally (and reboots as soon as NSTools loads) and does go into recovery. after selecting wipe nstools and trying to reboot I get the same "soft reboot".

oh well, if its a stock kernel issue, I hope it'll be fixed soon ;)

btw how long does your battery last with that setup?
[Galaxy S I9000 Android Development] Bavaria85:
It's probably been asked before, but i can't find it anywhere so:

If i'm on cm9 build 15 do I already have GB bootloader or do I have to flash it first before i use this kernel?

And if so where can i find it?

Thanks
[Galaxy S I9000 Android Development] purpleraintoxicity:
depends on what rom was you on before.
[Galaxy S I9000 Android Development] DaXmax:
Well, im no pro in this lol... :p But i will try your settings if a next version released, got problems with Beta 2 yesterday... :/

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] cba1986:
What i tried to ask is what is the max freq that he uses.
[Galaxy S I9000 Android Development] davidisflash:
comparing smartass govenor to conservative: battery and smoothness

Has anyone done extensive testing to compare the conservative and smartass govenors? Noticeable difference in battery / smoothness when choosing one versus the other? I'm on ICS v12 Beta, Samsung vibrant.
[Galaxy S I9000 Android Development] sixstringsg:
Smartass will certainly be faster and smoother. Conservative will theoretically have better battery life.
[Galaxy S I9000 Android Development] davidisflash:
Yeah I expect that, but I guess what I should have probably asked is: do the battery savings on conservative warrant the performance hit? More specifically, are the performance gains greater than the battery loss when using smartass? I've used smartass before and really enjoyed the performance, but that was glitch v13 on 2.3.7 Android.

The fact you said "theoretically" may suggest that the question is answered :) Thanks
[Galaxy S I9000 Android Development] sixstringsg:
In short: I do not think conservative is good enough with power saving that it warrants the performance hit. That is my opinion, as always test on your particular phone.
[Galaxy S I9000 Android Development] purpleraintoxicity:
I don't feel any change with wifi.

In fact its the opposite if what I understood.

Signal is weaker then other kernels, and battery consumption is lower then others.

Have I missed something?
[Galaxy S I9000 Android Development] hs911:
does not work with onecosmics (or icssgs) :( thinking of switching to teamhacksung now...
[Galaxy S I9000 Android Development] jbarbosa93:
With the onecosmic rc3.1 the application firefox crash, and all tye rest works
[Galaxy S I9000 Android Development] sixstringsg:
We dont much care about onecosmics ROM.
[Galaxy S I9000 Android Development] revthanki:
bootloops (no CWM)

I'm running into a peculiar problem.

Using NSTools to explore undervolting my CPU (running TH 15 and V.14 B2). I'm being sensible and keeping a log and making sure that "set on boot" is not checked. However, twice (once last night and just now) I've run into a sudden bootloop. I can't get into CWM and the battery charging animation also bootloops.

How could this happen? I mean the undervolting I was doing shouldn't be altering anything on the storage...

Last night I had to flash to stock, root and then restore a Nandroid. Is there a better way out of this mess?
[Galaxy S I9000 Android Development] jbarbosa93:
But why is a good rom, to run with yours kernel.
[Galaxy S I9000 Android Development] purpleraintoxicity:
Cause glitch is all about cm9
[Galaxy S I9000 Android Development] DaXmax:
In fact, all other custom kernels is about cm9...

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] arifroni:
is anyone having wifi problem?
[Galaxy S I9000 Android Development] DaXmax:
Like on and off?

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] arifroni:
no, internet is not working after sometime....like, i opened FB, worked...then i tried to go to another group....not working.....reconnected wifi....then worked...:(
[Galaxy S I9000 Android Development] roland23:
Faced something like that when I was on smartass. Try to change to other governor; for me problem solved like that.
[Galaxy S I9000 Android Development] wogfella:
Check the lease tim set on your router. That issue went away for me when I set it to anything that wasn't "never expires"
[Galaxy S I9000 Android Development] revthanki:
This nasty bootloop happened again, with no UV this time. I think this is what's happening: I'm getting a reboot to recovery and this is actually making recovery reboot itself. Has this happened to anyone else?
[Galaxy S I9000 Android Development] Gage_Hero:
What ever undervolt your trying to apply is too agressive. I found this out also... it is probably the lower end meaning in the 400 Mhz and down where you have undervolted too much... its best to work your way down gradually and when you hit the reboot you have gone too far.
[Galaxy S I9000 Android Development] revthanki:
an idea...

i was doing exactly as you suggested last time :) but this time i got into the bootloop without any kind of oc/uv. i'd kept stock voltages and had just changed governer to lazy. i then went into cwm to do a nandroid. after i finished the nandroid i pressed 'reboot system now' and then voila, unrecoverable bootloop.

this isn't happening on devil's kernel or stock. with these i sometimes get random reboots into recovery, which are no problem. with glitch i never get crashes that reboot me into recovery, and i suspect that this is the problem: the system is trying to drop me into recovery and the custom recovery that glitch uses isn't letting it in --> therefore you get an unrecoverable bootloop...

my 0.02€ suggestion!

btw TK/SS, thank you for your kernel, it's by FAR the smoothest and most fun to use out there, if only it weren't for this annoyance...
[Galaxy S I9000 Android Development] Gage_Hero:
Just a stupid question but did you wipe the cache at all? The other thing that you might try is reflashing the kernel.