yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] spoonymoon:
Same happened to me :eek:

I guess that disabling fsync did made the error....

So if on 0.67 dont fiddle in misc options, leave it alone to Devil releases a new version ;)

Im sure its not rom related, but kernels fault

Cheers
[Galaxy S I9000 Android Development] yahyoh:
why u disabled fsync all developers says its dangerous for data loose :eek:

try to take of the battery then try the three buttons for download mode if still nothing i think u need usb jig
[Galaxy S I9000 Android Development] saphirrot:
thanks mate but i already told you that download mode is working, but i dont want to reflash everything. it sucks.. maybe DerTeufel can make a tar kernel for Odin !
[Galaxy S I9000 Android Development] yahyoh:
lol sorry i thought u say i cant go to download mode :D

ur problem is easy to fix just flash recovery fix from this page just scroll down to Phone is in boot loop can't get to Recovery (I9000) and follow the instruction

then reflash the kernel
[Galaxy S I9000 Android Development] abalam:
Maby with recovery fix

Print from my GT-I9250® using

CyanogenMod9.0.0-RC0
[Galaxy S I9000 Android Development] marcedli:
flash cm7 initial kernel with Odin, then flash your ROM again.

if it booted up properly, flash the devil kernel again and don't mess it up again :D

Tapatalk 2-vel küldve az én GT-I9000-ről
[Galaxy S I9000 Android Development] doc_2nas:
Or make a backup first before messing around... curiousity is something irresistible.... :D
[Galaxy S I9000 Android Development] saphirrot:
thanks to all, i really dont know why i asked this stupid question, i think my brain was in deep idle mode....

flashing a gingerbread / cm7 kernel will of course help me...

by the way : you dont need to flash your rom again. Boot up with cm7 kernel into recovery and after that reflash the Devil Kernel .
[Galaxy S I9000 Android Development] saszseb:
Not needed the ROM flash.

- In CM7 recovery flash the Devil kernel again.

- Battery out/in

- go recovery via 3 button combo and your phone will boot up.
[Galaxy S I9000 Android Development] marcedli:
good...

I've suggested ROM flash only because it takes only 30 seconds more and it's kind of safety precaution to avoid some corrupted scripts, whatever remained in system....

if kernel flash was enough, it's good
[Galaxy S I9000 Android Development] .:Crack:.:
- PMFAST mode for best wifi performance (different low power mode than default, using a bit more power). (glitch)

Confuuuuused :D
[Galaxy S I9000 Android Development] saszseb:
- pmFast: battery saver.

- pmMax: better signal.

Sent from AOKP.
[Galaxy S I9000 Android Development] cspiby:
I was referring to this post http://xdaforums.com/showpost.php?p=21480437&postcount=245

You're probably right, the problem lies in the ROM not the framework :(
[Galaxy S I9000 Android Development] fulii:
Hey!

I really don't understand something. In EVERY F***ING thread about ICS or ICS kernel

or something about ICS there is not an actual conversation about the stuff itself but "is it working on onecosmic's?" and "is it working on teamhakcsungs??" Stop to do it please it makes the thread dirty and I guess that's why people don't read through the whole thread because there are loads of posts about this sh*ts. Just stop it!

READ THE OP, and btw every kernel dev stated that who do they support.

TH : GLITCH , PLATY,DEVIL

OC: STOCK+, and his selfmade recomplied kernel thats all

please stop moaning !!!!!

thank you
[Galaxy S I9000 Android Development] thaidroid:
Posted earlier in this thread DIDL gets disabled when USB is connected reboot phone after USB disconnect
[Galaxy S I9000 Android Development] DerTeufel1980:
I am not against supporting onecosmic rom, but I just don't know, what changes he makes to his kernel when he is updating the rom. This is why I can't guarantee that the kernel will work on next version. If I would know it, I would make an extra version for his rom.

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] darckengel:
@DerTeufel:

With music while screen off, i have a little time in deep iddle, but very few

I remember that GB (stock based) kernels have also Deep Iddle code, but they use DVFS to set fixed cpu freq for some tasks (ex music player) to be able to work.

So i set manually min freq=max freq and i lauched music player and now i have 80% maybe more of deep iddle state while screen off and listening music

To be able to get into deep iddle, there can't have freq changes.

Maybe we will have to set DVFS to make deep idle working properly.
[Galaxy S I9000 Android Development] erto90:
Can you also make a -non voodoo color- version? Cause the green flicker with voodoo that appear every time screen go black also for half second ( ie when arrive an email an switch to emailmapp)

Thanks
[Galaxy S I9000 Android Development] DaXmax:
Thanks DerTeuFel, but do i need the modded framework when i dont need DIDLE? Does it breaks anything?

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] DrAnGeR:
i cant save the current settings to be activated after reboot. the Set on boot is ticked but still after reboot everything turns on default. same on voodoo app. any suggestion?
[Galaxy S I9000 Android Development] DerTeufel1980:
I will try it. My older tests showed that dvfs limit was making deep idle worse.

Yes. It's on its way. This is, why last kernels are named vc (Voodoo Color).

No, you don't need it.

You need voodoo pro, because of the free version is not updated for ics yet.

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] ocelofil:
Hi DerTeufel1980,

with the newest kernel I had spontaneous restar. I am on Onecosmic rom, and your previous kernel works great on it...it will be great if you release an extra version for Onecosmic, coz your kernel is the best from all kernels for me! Great job man;)
[Galaxy S I9000 Android Development] Broeser:
If i update the kernel to new versione i must re-flash the modded framework?
[Galaxy S I9000 Android Development] Bonvaz:
tell me why people doesn't read the ****ing last 3 pages....tell me why.....

anyway flashed last kernel on build 13,perfect ;)..I don't have wifi in my home,but trying to turn on it and search wifi's neighbour and find it..very weel:D
[Galaxy S I9000 Android Development] titovic:
AFAIK, the framework is handled by the ROM so a kernel update shouldn't require you to re-flash the mod.
[Galaxy S I9000 Android Development] purpleraintoxicity:
Correct.

I think I'm going back to th13.. 14 giving random reboots haha

And giving the fact its works great on 13, I want enjoy this kernel more

Send through space, using my alien phone running TH CM9
[Galaxy S I9000 Android Development] cspiby:
Could deepidle be enabled by default on your next release? (I presume defaults are handled by kernel).
[Galaxy S I9000 Android Development] giokspy:
Some times deep idlie working on me and other times no . For this time working or not??
[Galaxy S I9000 Android Development] superwahwah:
When you got values in TOP=off, that's mean deep iddle works

you should read the OP ^^
[Galaxy S I9000 Android Development] Broeser:
It does not work very well on build 14?
[Galaxy S I9000 Android Development] darckengel:
Deep Iddle is very unstable, after a moment, seems that you could not be in this state without reboot.

I wanted to do some more tests (same tests than before: music player + screen off) and can't be able to set deep iddle state anymore ...

I didn't do anything else with it, just changed governors and freqs, but with exactly the same settings than before (where i got deep iddle state), i only had sleep (and i didn't use usb connexion or camera or anything else).
[Galaxy S I9000 Android Development] stfudude:
i'm waiting for OP to update his kernel to:

1- have stock teamhacksung colour. voodoo colour is great but i just can't find the settings to get better colour for my phone.

2- fix wifi and random reboot issues some people are having with this kernel.

3- fix lazy governor-DIDLE compatibility someone reported.

when all this conditions are met, I'll flash the kernel in a heartbeat.
[Galaxy S I9000 Android Development] .:Crack:.:
I don't know if you've read my post....
[Galaxy S I9000 Android Development] mk_ln:
maybe it's just me, but it seems that 65 is faster/smoother than 67...in terms of gaming performance.
[Galaxy S I9000 Android Development] beat.kitano:
I'm sorry for the question.

Is the battery life extender active by default?

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] DerTeufel1980:
you are right....damn, it was too late when i was releasing it...

thx
[Galaxy S I9000 Android Development] pbecks1963:
Just flashed latest (bm) Devil kernel 2 XL 0.67. (already had the former devil - version (bm) running without any problems (set performance = smooth, NO other settings done)

I ended up with a bootloop (couldn't get into cwm) Had to use Odin to fix cwm and used lippol's cleaning script this time BEFORE flashing the latest bm-version (12/4). This time everything is OK..

Just wonder why it went wrong in the first place????

ps: love this kernel and the "smooth" performance setting in the (devil) cwm
[Galaxy S I9000 Android Development] dark_knight35:
Bug report:

1. If phone is off and connected to charger, I have to disconnect it first to turn it on, otherwise it'll just reboot into charging mode. This happens with fsync on and off, I'm using 0.67 xl bm on Slim 3.2.

2. Little typo: you wrote 'defaul' instead of 'default' in fsync menu in CWM ;).
[Galaxy S I9000 Android Development] eloptimistico:
I also had the same thing. Came from 0.65 xl, ended up in a bootloop and lost recovery. Needed odin to fix everything. Maybe some conflicting init.d scripts or something? Did the usual wipes (cache, dalvik, init.d, nstools settings). Just wondering why it went wrong.
[Galaxy S I9000 Android Development] FadeFx:
Did you guys flash the kernel with charger connected? I have a suspect that offline charging is the culprit for those bootloops...

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

tapatalked from vizio vTab1008
[Galaxy S I9000 Android Development] saszseb:
I think, no. If you simply flash a Devil over Devil you'll get bootloops. You should clear "nstools settings" and "init.d" in recovery before flashing one.

Sent from AOKP.
[Galaxy S I9000 Android Development] sthomas38:
I flashed 64 over 62 and 67 over 64 and all went fine.
[Galaxy S I9000 Android Development] FadeFx:
I always flash devil over devil without any problem, all init-d scripts are moved to backup folder anyways, so this can't be the case. However, those exact bootloops are reported on cm9 thread as well and i had one with stock kernel myselfs.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] DerTeufel1980:
it's not against you, but these theories are almost ....

what do you think how i am testing my kernels? i always flash every kernel over my previous, ten times a day.... i never got a bootloop.

i also was reading about bootloops in stratosk thread, even at cm9 thread, by flashing a new nightly....

edit: i NEVER clear cache or dalvik cache, and i also NEVER ever was using lippols kernel cleaning script...maybe these things are not working for cm9
[Galaxy S I9000 Android Development] saszseb:
That was my experience. I got bootloops and lost recovery, too. But this was a small issue and solved the prob.

Sent from AOKP.
[Galaxy S I9000 Android Development] habylab:
I get the same. You also misspelt battery, as batterie in the wifi section of recovery.

Sent from my Galaxy S running Slim ICS 3.2 with Devils 2.0.67xl Kernel using the XDA Premium app
[Galaxy S I9000 Android Development] LoqOs195:
I think the same thing, I'm surprised how many people get bootlops just flashing a new kernel, I never get any bootloop for it, maybe it could be a hardware issue?

BTW, I'm on AOKP with Devil2 0.6.7XL, and my battery life is simply amazing! I want to think that is for the rom but also it is for the kernel, and your kernel is the best for the battery life, no Semaphore, no Midnight, ONLY DEVIL!! :D

PS: sorry for all my gramatical mistakes in the post but my english is not verry well now :P

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] yahyoh:
@DerTeufel1980 so now the version with b no need to patch the rom and it will play all type of videos ?

but not a big deal cuz the huge ram kernel can play 95% of videos type on h/w decoder
[Galaxy S I9000 Android Development] cba1986:
+1^^

I'm using the 389Mb version without any problems....

On another subjects. Supercharge memory's setting doesn't stick after reboots. It's init.d working properly?
[Galaxy S I9000 Android Development] DerTeufel1980:
check the user.log at /data, or upload the file for me, then we will see :)
[Galaxy S I9000 Android Development] cba1986:
Here you are.

http://www.mediafire.com/?ahqwpez6yhyq849

Also. I had the script for the low space left bug on init.d and it seems it doesn't get applied either.
[Galaxy S I9000 Android Development] takerhbk:
im sorry but im confused which kernel version to use for RC4.2 ?? :confused::confused:

Can anyone provide me link??

OP link says "only for rc4.1"
[Galaxy S I9000 Android Development] gokussjx:
May be setting the permissions to executable would solve it.

Change permission of init.d scripts (the ones you want executed at boot), to rwxr-xr-x

Check with log/terminal if that works :)
[Galaxy S I9000 Android Development] CheekyLord:
---

try not the script as LowDataBug solution...

i use the LowDataFixer from AOKP-build-22 and never got this 'Low data message' again.

(i use that fix on AOKP/RC4.2/Hacksung/ without any probs)

---

@ takerhbk

Devil Kernels runs smooth like butter on my RC4.2...!! :)

SentFrom XDA ForumApp by ICS SGS-I9K
[Galaxy S I9000 Android Development] doc_2nas:
Nope, change permissions or change owner won't work. I don't know what's the culprit, but some scripts works (eg. 99nstools) and others don't (eg. SS99Supercharger, S80Enable_bt_off). I have tried to change busybox to other versions (1.9.4-cm9, 1.9.4-stericsson, 1.9.3, 1.9.2, 1.9, 1.8.4) but no luck... :(

As I remember this also happens on semaphore and midnight with SS99Supercharger script...

Maybe it's ROM issue, I'm on slim 3.3, and haven't tried other ROMs beside Slim (never used stock kernel anyway...)

Will try to test other scripts....
[Galaxy S I9000 Android Development] dark_knight35:
On supercharger thread, there's a special busybox with more tools. I took this and everything worked.

EDIT: And set permissions to rwx - r-x - ---
[Galaxy S I9000 Android Development] DerTeufel1980:
it is executed:

you could check the mentioned log file now
[Galaxy S I9000 Android Development] DerTeufel1980:
please also upload /data/user.log, or check for yourslef, if the scripts are told to be started. if yes, try running them in terminal emulator and look at errors.
[Galaxy S I9000 Android Development] doc_2nas:
Yes, I've tried that busybox also (1.9.4-wraithdu) but still the same. Working well through script manager/terminal but not through init.d, minfree and adj tweaks failed.

Thanks for your concern mate...
[Galaxy S I9000 Android Development] doc_2nas:
Hi DerTeufel1980,

Here's my user.log http://db.tt/rdGMTwqc

It said it was executed. But when checked the minfree and adj, it didn't change. But when executed through terminal or set to executed at boot using script manager it worked with no errors. So I guess maybe something is executed during boot sequence that override the settings from init.d so some scripts looked to be working and others not....

Thank you so much for your concern, time, n effort Sir....
[Galaxy S I9000 Android Development] dark_knight35:
Did you mod services.jar with the online app found on supercharger thread? I think you need this to change minfree values on ICS.
[Galaxy S I9000 Android Development] doc_2nas:
Yes, I did it through online service (http://android.mimic.ca)

Supercharger installation will give us error message if we don't modify the services.jar (I have tried to install it without modified services.jar :eek:)

I think the problem here is the boot sequences, not the supercharger script. Since others script like rfkill(power down bluetooth) also doesn't work if we run it through init.d. but they work well through terminal/script manager.

Really appreciate your help mate....
[Galaxy S I9000 Android Development] dark_knight35:
I don't use the scripts anymore, but on 0.65(or maybe 0.64) and Slim 3.2, they worked fine for me, so I think it's just bad luck or something changed in new version of kernel/ROM, but I don't think so. Strange issue :confused:.
[Galaxy S I9000 Android Development] Segnale007:
Minifrees setting doesn't stick at boot because the rom you're using doesn't have the the services.jar patched for V6_Supercharger script in order to read ADJ values at boot time. Its not a kernel related issue, but its rather the rom you're using.

You have two options at this point. 1) deodex the rom you're using and patching the services.jar file according to the guide on V6Supercharger thread on the second post.

2) Get the services.jar and services.odex files from infinity rom and copy them into /system/framework

Bye
[Galaxy S I9000 Android Development] doc_2nas:
Thanks for the info mate. But I think you got a wrong impression of what we are talking about. We've already had patched service.jar but the problem is in init.d (maybe?), SuperCharger is only a sample script for this situation..... (but I also suspect it's ROM related, not kernel) Hopefully DerTeufel1980 will give us some enlightenment.....

Since in slim ics thread they said don't post there if you are not using stock kernel....too bad.... and I don't want to use stock one.

Maybe anyone whose still in stock Slim 3.3 could report here for comparison?

BTW it's not important issue for me, I can still run the script using ScriptManager...

So sorry mate, just want to make it clear...
[Galaxy S I9000 Android Development] magik-thc:
Still there is an error:
[Galaxy S I9000 Android Development] dark_knight35:
We know. Who cares? Message will be away when virtual keys are added.
[Galaxy S I9000 Android Development] cba1986:
I don't think that is a ROM issue i never had this problem on CM + glitch.

I went bak to glitch B6 and the settings are applied correctly. I will keep testing and reporting back.

EDIT: Flashed 0.67 again, but the settings still are not being applied.
[Galaxy S I9000 Android Development] folkg:
That never got updated either. I have found that if I live OC all frequencies then my phone will not freeze. Could it maybe be that when it is jumping from a non-OCed frequency to one that has live_OC it somehow freezes? It seems to me that might be happening.
[Galaxy S I9000 Android Development] habylab:
I've been on selective live oc for a day, perfectly fine.

Sent from my Galaxy S running Slim ICS 3.2 with Devils 2.0.67xl Kernel using the XDA Premium app
[Galaxy S I9000 Android Development] doc_2nas:
Yes, I think you are right, just got back from stock slim3.3 kernel, semaphore, and midnight. It's working on stock and semaphore, and not working on devil and midnight. I really don't have any ideas what's the difference but hopefully the devs might help.
[Galaxy S I9000 Android Development] fishears:
Will BFS return soon? I love that scheduler... ;)
[Galaxy S I9000 Android Development] MEEEE:
Is deepidle stable?

is there any disadvantage when i activate deepIdle? Some people reporting issues with this.

ty guys
[Galaxy S I9000 Android Development] dark_knight35:
Just enable it. If something doesn't work, disable it.
[Galaxy S I9000 Android Development] :
Is there any explanation of all the different versions of the kernel?

cmc = ?

vc = voodoo control

cfs = ?

bln = backlight notification

0.76 vs 0.76 b - difference?

xl versions?

Thanks for your help
[Galaxy S I9000 Android Development] worms:
Is in second post ;-)

I had some issue flashing 0.67b aka bootloops.

So i had to reflash a Samsung rom and after the Last build of cm9.. Now when i set deep idle the Phone dont come Back from it.. I have this issue with any night and devil kernel

How can i fax??

Sorrento for my por English.
[Galaxy S I9000 Android Development] XlAfbk:
all your questions are answered by the seconds post!!!
[Galaxy S I9000 Android Development] DerTeufel1980:
I took the boot init process from midnight, because i really like this user.log

probably is the init.d now started some time earlier than on other kernels. this way the settings get overwritten by sys init. at the first quick look at it, i don't know how to fix it in an easy way.

i'll look at it, when other (more important) things are done. just take scriptmanager to run these scripts untill it's fixed.
[Galaxy S I9000 Android Development] :
Either I'm retarded or they are not oO
[Galaxy S I9000 Android Development] XlAfbk:
cfs

xl

0.76 vs 0.76b, cmc
[Galaxy S I9000 Android Development] :
oO I guess I'm retarded then:eek:, thanks mate
[Galaxy S I9000 Android Development] saphirrot:
Same here
[Galaxy S I9000 Android Development] burakgon:
I'm waiting for another bigmem release. Currently super smooth with 67 bigmrm
[Galaxy S I9000 Android Development] doc_2nas:
Thank you so much Sir. I love the user.log too. Okay, will do that.

Really appreciate your work. Amazing as always :)
[Galaxy S I9000 Android Development] kamalmawa:
0.67b stock ram(377mb) works grate :) .. no problems with high bitrate 720p videos
[Galaxy S I9000 Android Development] MetalPainis:
Flashed 0.67b_cfs_bln_cmc_20120414 on pawitp's ICS nightly 0412 and 0415, on both roms the kernel killed the headset button controls. Since I could not find any option to trigger the headset button controls, I assume this is a bug. Just to be sure I flashed the kernel multiple times over both nightly builds. Switching back to stock kernel brings the controls back.
[Galaxy S I9000 Android Development] DerTeufel1980:
Thx. This really is a bug.
[Galaxy S I9000 Android Development] Vertron:
What's a good set up for min/max CPU load on Smartassv2 for battery life? Can't find any previous posts about it. Getting quite poor battery life atm with Elite 10.1
[Galaxy S I9000 Android Development] habylab:
The stock are pretty decent, maybe decrease down step time to around 2500.
[Galaxy S I9000 Android Development] dark_knight35:
For your GamerzROM patch? Seems that you can't decide which kernel to take :D.
[Galaxy S I9000 Android Development] burakgon:
Me and my gf, we are using devil kernel since about 1 month. We have no problems. But just need a agressive governor when we want a great performance. Even on a heavy game, cpu goes to 800mhz step too much. Conservative is most agressive governor on this kernel. Isn't it interesting? :D
[Galaxy S I9000 Android Development] purpleraintoxicity:
conservative is the "smartest" governor.

"one governor to rule them all"

you can tweak lulzactive... to your liking
[Galaxy S I9000 Android Development] DerTeufel1980:
i am also working on a way to make ondemand even more responsible (or: i was working, it's almost finished :) )
[Galaxy S I9000 Android Development] lerkin:
Really appreciate your great work. You have put so much time on improving our phone. Thanks again.
[Galaxy S I9000 Android Development] pckoloji:
i use cm9 nightly build 16-4-12 and devil2_067b

no problem with remote control while listening music, skip/play/pause working
[Galaxy S I9000 Android Development] doc_2nas:
Or tweak smartassV2, I found it has best balance battery/performance especially when combined with sio.....nice :D
[Galaxy S I9000 Android Development] kamalmawa:
I thought theoretically conservative supposed to be battery friendly. I know that devs are tweaking these governors. So what is the most battery friendly governor for Devil2 without any noticeable lags?

e.g: recommended setting for glitch v14 is conservative+ noop
[Galaxy S I9000 Android Development] purpleraintoxicity:
I would say the same.

maybe smartass would be good