yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] vitoski:
DerTeufel1980 I do not know whether it's already there in 0.84 version or not, but do you plan to implement switch (either with Command Center or CWM) to enable or disable 'swap'?

I know it's by default enabled and I use it since you gave us that possibility. However wanted to try starting my Camera (Zoom FX) without swap enabled. Right now it stars so f... slowly (5 seconds to be able to take a photo)...

THANK YOU for great work. Before, I was waiting for Icy Glitch v7 to try it out. However this time I do not believe I am gonna check it even if they finally release it... Simply your kernel works for me the best!
[Galaxy S I9000 Android Development] FadeFx:
Oh, sounds like bad luck...

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] anuj_blaster:
having force close on voodoo after setting boot speed to 1300.

When I try to reinstall it.. asks me to free some space..

I also had Power Save setting under performance

SamsungGalaxyS - I9000

CM 9 [IMM76D]

Devil2_0.79_i9000_CFS_BLN_VC_20120501.zip
[Galaxy S I9000 Android Development] ingbrzy:
Is possible implement also 50MHz and 25MHz CPU freq...?

I am using it with SGS2 (Siyah) and no problem with stability... :-)
[Galaxy S I9000 Android Development] Ledanur:
I'm aware of its functionality with Galaxy S 2, I'm asking whether it can work on I9000
[Galaxy S I9000 Android Development] yahyoh:
any thing lower than 200 MHz will not save any battery trust me ;):D
[Galaxy S I9000 Android Development] Ledanur:
I'm not talking about <100 Mhz steps.

What I'm taking about are steps like this - 200, 300, 400, 500, 550, 600, 650, 700, 725, 750, 775, 800, 1000, 1025, 1100, 1125, 1200.

As an example
[Galaxy S I9000 Android Development] ingbrzy:
I think its working well and save some time for battery.... :-)
[Galaxy S I9000 Android Development] FadeFx:
Having so many stepps would create too much overhead for switching in my opinion. I dont think that it is worth the effort.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] .:Crack:.:
Afaik Smartass was developed on a HTC device and HTC devices have zillions of cpusteps. So somehow it cannot be bad?
[Galaxy S I9000 Android Development] Ledanur:
I understand.

I was curious to know if it was possible, not if it's worthwhile.

I probably sound like a nag right now - but it's a kind of multiple selective live OC's.

Think about it this way.

The specific frequency step would need a few less mV to operate, which - theoretically - could lead to lessened battery consumption. I understand that the overhead could cause for too much polling, which would render the benefit of the abovementioned technique redundant, but that's all in theory.

I'd like to test such a thing. I'd program it, if I knew how.
[Galaxy S I9000 Android Development] siky_dude:
Yeah.. maybe... but the idea would be if an app needs just the 500 mhz step, why should it go to 800 instead :). Talked about this with zacharias.maladroit in cm7 times and thought it would be a good idea, but didn't have the time to implement it. Talked to renauld to, and he said it wouldn't affect battery life but it would take more time to scale up. Now I don't know what to think, but it would be nice to have all the frequency steps... just as a experiment.
[Galaxy S I9000 Android Development] stratosk:
It would take more time to scale up on conservative. Using ondemand the max frequency will be used no matter how many steps you use.
[Galaxy S I9000 Android Development] FadeFx:
I think you can trust nikademus... also there is no occasion an operation would need the lower frequency, higher frequency means less execution time for the same task and thus les power consumption. Only thing that makes a difference is media rendering which is done in dedicated hardware anyway.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] siky_dude:
But what about zacharias.maladroit...^^…

Still, it wouldn't hurt to test this... of course, if the Devil has time :D.
[Galaxy S I9000 Android Development] FadeFx:
My info on overhead was from hardcore when some guy asked for more steps. Hardcore is is one more trustworthy instance of an advanced kernel dev whose word i take as law.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] burakgon:
I will release my own kernel this night. I hope. Just added overclock to stock cm kernel. That's what I need at all. Just for my personel use but sharing if people need it. But need help about how to make it 402mb RAM. I'm very noob at this point. I will update my kernel regulary with every nightly. Maybe dertoufel can help me.
[Galaxy S I9000 Android Development] atomixxx:
Hi

How can i adjust touch vibration ?
[Galaxy S I9000 Android Development] dark_knight35:
Read changelog. Via script or CWM.
[Galaxy S I9000 Android Development] Weedalot:
Ok i flashed to cm9 and than used it for a day than flashed devil again.the reboots started over,i believe they are oc related, when i oc it to 114% to 1300 it starts.sometimes right away sometimes at random intervals.
[Galaxy S I9000 Android Development] FadeFx:
You cant live-oc without raising voltages...

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] yahyoh:
i think the problem with voltage look at this post hope it help u

btw on 1.4 or 1.2 i feel the phone fast as my s2 and without live OC :p
[Galaxy S I9000 Android Development] Weedalot:
I did like you said, the 100 to 1100 mv should i raise the rest? Also i oced before on 79th version without any change and it didn't reboot. So how should i set voltage than on 114%oc?
[Galaxy S I9000 Android Development] FadeFx:
Raise the 100mhz voltage is neccessary for some, if not most, devices already without live-oc. If u use live-oc you most likely need to raise the other voltages as well, see the qoute before your post...

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] saszseb:
deep_idle: CPU is set to off.

deep_sleep: CPU is set to 0.
[Galaxy S I9000 Android Development] pl4cid:
yes, check the menu 'bln blinking' also. there is another checkbox which must be ticked for proper working :)
[Galaxy S I9000 Android Development] DerTeufel1980:
here are the kernels with voodoo color now. Sorry for the delay, was testing too many other things ;)
[Galaxy S I9000 Android Development] utsmaster18:
I have to say, being a first time user of this kernel, thus far pretty good. I've usually used platypus before but just as good.

perhaps its placebo but seems like bfs its actually faster, or maybe just the change of io scheduler but nonetheless faster.

nice work
[Galaxy S I9000 Android Development] DerTeufel1980:
i don't think its just placebo, because bfs is told to be faster. many devs were trying to use this scheduler before, but it seems like linux 3.x is making it possible :)
[Galaxy S I9000 Android Development] XblackdemonX:
I also activated bln blinking...

Press to test the leds, close the screen, no leds :[
[Galaxy S I9000 Android Development] Jaggle:
I have the same problem. Tried everything... but no leds :-(

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] DerTeufel1980:
ok, then i have to release a version for you, withou the need of bln ;)

wait a moment, please
[Galaxy S I9000 Android Development] XblackdemonX:
Thank you so very much!:D

Ps: if that makes any difference I have the Telus Fascinate
[Galaxy S I9000 Android Development] DerTeufel1980:
i don't know, if this makes a difference. I don't have one ;)

Of course, this kernel is not just only for you. Was testing it this evening. This is why voodoo color was delayed ;)

one can set blink timeout, etc. with nstools

please keep in mind, it's still in testing stage.
[Galaxy S I9000 Android Development] meisterlampe2000:
Here is my Logcat regarding the Bluetooth Problem:

I/bluedroid( 225): bt_enable: ret: -1, errno: 19

This get´s repeated until midnight once i toggle Bluetooth on/off

Maybe it helps ?

Thanks for your work so far !!
[Galaxy S I9000 Android Development] purpleraintoxicity:
Can you please provide a stock colors version to the "Devil_3-1.0-14_BFS_V(R)_LiveOC_DeepIdle_LED.zip" kernel.

I've reverted to it and I get constant didle (top= on only though)

Its little lied smooth then the latest, but I has (and never had) no problem with this version....

Nm.... Just lost it again haha

thanx man.

oh... By the way.

This version, add long as "Devil_3.0-13_BFS_V(R)_LiveOC_DeepIdle_LED.zip" is giving me great battery life. And some how more then the latest....
[Galaxy S I9000 Android Development] beat.kitano:
Installed. It seems great.

Later more info.

Inviato dal mio GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] wkh1113:
Hi,I have a question about governor.

What is the difference between ondemand and lazy?

Which one has better battery life and better??
[Galaxy S I9000 Android Development] gonova:
Live OC

This is a very great kernel, but I am very confused and lack of knowledge about Live OC.

I did google around and found the official Live OC thread:

http://xdaforums.com/showthread.php?t=1288015

But I still can't fully understand.

Can someone please let me know how we should set in TStools ?

Should I just keep max CPU frequency to 1000Mhz only?

And let Live OC to be 120% ??

or should I still have CPU max as 12000Mhz ??

what's the difference to do in setting CPU Max and Live OC % ?? :confused:
[Galaxy S I9000 Android Development] rlorange:
Glitch kernel aothor has the best guide.

***Vintage Galaxy S1 running ported Ice Cream Sandwich Android 4.0.3 by OneCosmic***
[Galaxy S I9000 Android Development] treyy:
That was the Same problem that i had. But i can say u my experience with it. When i set Live OC to 120% and let the CPU at 1000mHz. i got Reboots into CWM. But when i set only the CPU at 1200mHz or higher, i didnt get this Problems and the phone runs stable and fast.
[Galaxy S I9000 Android Development] rlorange:
Yes its because liveoc over clocks the bus and gpu. 120% is high. 112% is the Max for most you need to bump up internal voltages to match. So if normal 1200 step has 1150mv internal voltage then 120%liveoc on the 1000mhz step (giving 1200mhz) will need 1050mv internal voltage. Hope this makes sense

http://xdaforums.com/showthread.php?t=1419274

This should help explain liveOC for all.

***Vintage Galaxy S1 running ported Ice Cream Sandwich Android 4.0.3 by OneCosmic***
[Galaxy S I9000 Android Development] whaave:
Hey, thanks for your hard work!

I was just wondering if you could add a better versioning to your kernels? I'm not able to keep a constant eye on this thread, and I'm finding it hard to figure out what changes are made, and which version I want to test.

Again; thank you :)
[Galaxy S I9000 Android Development] dawidk750i:
when will be version with Deep Idle?
[Galaxy S I9000 Android Development] Weedalot:
tried it, same reboot persists. Don't know without live oc it works amazing once i live oc just a bit it goes bananas. couldn't even finish setting the voltage with nstools before a reboot. I just oced without live to 1300 with default voltage and it works great. Smooth and all. Might be a conflict with some smooth ui i enabled in control center.
[Galaxy S I9000 Android Development] Gaffel-K:
How can i activate the devil idle? I mean, where and how can i write the "echo ......"

Thx

Jan
[Galaxy S I9000 Android Development] anuj_blaster:
When trying to play videos.. my phone hangs and it automatically reboots..

Using mx player..

Plz help..

Sent from my GT-I9000

CM 9 [IMM76D]

Devil2_0.79_i9000_CFS_BLN_VC_20120501
[Galaxy S I9000 Android Development] kamalmawa:
Run this in terminal emulator:

echo 1 > /sys/class/misc/devil_idle/bus_limit
[Galaxy S I9000 Android Development] kamalmawa:
Are you running with any OC/UV values?
[Galaxy S I9000 Android Development] eyriiii:
Does this kernel work with Team ICSSGS RC4.2 rom?
[Galaxy S I9000 Android Development] MetalPainis:
Aye
[Galaxy S I9000 Android Development] eyriiii:
Thanks :) with overclocking? and bln?
[Galaxy S I9000 Android Development] anuj_blaster:
Governor: on demand

Min:100

Max:1300

Live oc: 100%

Oc trgt low: 100

Oc trgt high: 1300

Also have loaded power save settings in performance..

As per instructions bln vc version. everything works.. right?

Also if you can suggest me some stable live oc settings .

Sent from my GT-I9000

CM 9 [IMM76D]

Devil2_0.79_i9000_CFS_BLN_VC_20120501
[Galaxy S I9000 Android Development] Weedalot:
I don't know, for some reason the are no longer stable for me,i actually use same as you without live oc and it's flying.
[Galaxy S I9000 Android Development] eyriiii:
Alright which one to download from here? http://devil.haxer.org/

Kind of messy when there is no real download link...:confused:
[Galaxy S I9000 Android Development] swent:
What about reading first two posts?

There u'll find the info that CMC = CyanogenMod Colors, VC = Voodoo Colors and bm = bigmem (402MB ram, breaking 720p recording).

So its up to you what you choose. Don't blame DerTeufel for making multiple versions to fit everyones needs.
[Galaxy S I9000 Android Development] mk_ln:
i have the same issue...
[Galaxy S I9000 Android Development] kamalmawa:
First revert back to kernel defaults including normal in performance then try to play a video again (if I were you I would untick the NStools restart save settings and delete NSTools settings in cwm then run the kernel cleaning script & reinstall the kernel). If it's playing with no problems then it's related to unstable OC...use the search you'll find pretty good OC values posted by others..remember every device is different when it comes to over clocking..you gonna have to find your own perfect values for your device. ;)

kernel cleaning script: http://db.tt/y2gKhgXQ
[Galaxy S I9000 Android Development] eyriiii:
Thanks for the answers, it's not really my phone just doing a favore to a friend. I installed the bigmem one and it's really fast and awesome but why does it not vibrate when he recives a message? I already ticked for it to vibrate..very odd
[Galaxy S I9000 Android Development] FadeFx:
I think at the moment you are doing your friend no favour with cm9, there are occassional bootloops which we do not now what causes them. As long as those are not solved, I'd not install any rom based on cm9 to a friends device. If he could not do it by himself, he also wont be able to solve problems he might tap into.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] jelle2503:
since when have bootloops been isolated to CM9 only?

it happens on every ICS rom and kernel... :rolleyes: or do you not follow the thread made by Stratosk?

I flash new CM9 nightly and new kernels everyday. Never had any bootloop. I wipe dalvik and cache so often with or without usb plugged I can't remember. Why you terrifying people to use CM9 for no good reason? CM9 works fine. Just like any other ROM.
[Galaxy S I9000 Android Development] MoooN:
only because it didnt happen to you does not mean that there is no problem

the bootloop issue is really bad (and often encoutered) atm

fadefx really has a good point

i would not like to flash a friends phone under the dark clouds of giving him an unstable rom
[Galaxy S I9000 Android Development] FadeFx:
What do u think aokp and what they all are called are based on? They all except of onecosmics rom are based on cm9. So yes, bootloops are affecting all of them.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] dark_knight35:
Not really... we have many aosp based ROMs.
[Galaxy S I9000 Android Development] burakgon:
Bootloops? I'm using 0.79 since first day. I don't have any single problems. If you can't configure or if you don't know how to, you musn't use this.
[Galaxy S I9000 Android Development] dark_knight35:
What????? I never reported from bootloops. I just sayed that we've got many aosp based ROMs. Don't post if you can't read.

sent from bubbleGUMMYng GALAXY S
[Galaxy S I9000 Android Development] FadeFx:
Belive me, those bootloops have nothing to do with configuration, they even occure with stock kernel. It also seems like not all phones are affected...

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] flinkebernt:
Off topic, but just tested Aroma File Manager

http://xdaforums.com/showthread.php?t=1646108

and it works great.

I think this can be a good tool sometimes. (init.d script problems for example?)
[Galaxy S I9000 Android Development] burakgon:
Sorry brother tapatalk queted wrong post.
[Galaxy S I9000 Android Development] Roastmeat:
Does anyone have some really steep battery drain while browsing?

It's basically vertical for me, a bit of a slope when on wifi saving mode

7 hrs on idle drops ~1% battery, cheers for that!

Is it the kernel or Rom?

I'm using the latest ICS Slim
[Galaxy S I9000 Android Development] Kocai:
What's the file extension of the video? I tried 3 MKV movies and all played well with MX player. So maybe the problem is the video you're trying to view?

ROM: CM9 nightly build 20120510

Kernel: Devil2_0.79_i9000_CFS_BLN_CMC
[Galaxy S I9000 Android Development] Adyztofles:
WiFi sleeping

SGS I

ROM: Slim 3.5

Kernel: Devil2_0.79

Modem: XXJVU

When my phone goes to sleep with wifi on, it seems that the wifi connection breaks down - after I wake the phone up, everything seems normal (wifi icon etc.), but the connection is lost. Strange thing is, that for example when I try to get to Google play, I'm not getting the "No connection - Retry" message, the page just keeps loading indefinitely (it's the same with all other apps) :confused:

I then have to manually switch the wifi off/on to get it working again. Could it be kernel related?

In my wifi settings I have the "Keep wifi on during sleep" set to always, in the ASS settings the power saver is completely off.

Sorry if this is the wrong thread to post, but any help will be greatly appreciated.
[Galaxy S I9000 Android Development] km211121:
Similar problem here, can't play 720p videos recorded with the phone.
[Galaxy S I9000 Android Development] kamalmawa:
No its not a similar problem because your using slim ICS and he is on cm9... I also see your using cm9 memory kernel.. try XL version and report back
[Galaxy S I9000 Android Development] km211121:
Thanks, you are right, it's O.K. with XL version.
[Galaxy S I9000 Android Development] _PrEzi_:
Anyone noticed an increased batt usage with 0.84 ?

I've upgraded from Devil 2 0.74 (and I could easily reach 3-4 days without charging - the battery usage line with light usage was nearly horizontal).

Now when I've upgraded the kernel to 0.84 I have a lot of 'System Android' usage (earlier it was 'standby mode').

I've used exact same settings - only swapped kernels.

And it's not a ROM issue - when I've downgraded to 0.74 (without wipe anything) - the usage would be back to my 'normal' (awesomely low batt drain) and again - nearly 60% of time on 'standby'.

Noticed with BetterBattery that there a lot of kernel wakelocks (in 0.84) for 'vbus_present' and from process view - a lot of kworker/0:0 1 and 2s...

With 0.84 battery was barely able to hold for 1 - 1,5 day with similar 'light' usage.

And yes - I've used a combo of NSTools and Command Center - same settings for both.

P.S. Running on TeamICS 4.2 and JVU modem if that matters. Both kernels from devil were CMC.
[Galaxy S I9000 Android Development] jelle2503:
not me. lost 4% at night (7 hours sleep). Sure you use devil tweaks? Like devil idle?

I got some pretty weird behavior with init.d script I've made on latest 0.84 kernel.

Script is named 00boot and inside init.d folder, tested with Scriptmanager.

It doesn't execute whenever 00verifyinit is in the init.d folder. If I delete 00verify with file explorer and reboot, my script is able to execute. A second reboot results in not executing of since 00verifyinit is in there again. :confused: I tested this twice.

I test whether my script is executed by looking with Command Center.

I was wondering what I was doing wrong but I'm pretty confident it's not me since I tested script with Script manager it isn't me but kernel doing something wrong.

edit: it also isn't working in 0.83

so why does it execute fine on 0.84 if I delete 00verify from init.d ?

For now I use Scriptmanager to start script at boot. :sadpanda:

edit2: on 0.79 it is working, but I renamed to 99boot.

edit3: on 0.84 my script 99boot what does work on 0.79, does not work on 0.84... It works however if I delete 00verifyinit from init.d folder

Here's the script I use

#!/system/bin/sh
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 500 > /sys/class/misc/backlightnotification/blink_interval
echo 1 > /sys/class/misc/deepidle/enabled
echo 1 > /sys/class/misc/touchwake/enabled
echo 10000 > /sys/class/misc/touchwake/delay
echo smartassV2 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 440000 > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq
echo 220000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq
echo 440000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq
echo 80 > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load
echo 95 > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load
echo 400000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step
echo 100000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step
echo 10000 > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us
echo 30000 > /sys/devices/system/cpu/cpufreq/smartass/up_rate_us
echo 300 > /sys/class/misc/notification/bl_timeout
echo sio > /sys/block/mtdblock4/queue/scheduler
echo sio > /sys/block/mmcblk0/queue/scheduler
echo 100000 > /sys/class/misc/liveoc/oc_target_low
echo 1000000 > /sys/class/misc/liveoc/oc_target_high
echo 100 > /sys/class/misc/liveoc/oc_value
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1400000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 110 > /sys/class/misc/liveoc/oc_value
echo 1 > /sys/class/misc/devil_idle/bus_limit
echo 100000 > /sys/class/misc/devil_idle/user_min
echo 400000 > /sys/class/misc/devil_idle/user_max
echo 0 > /sys/class/misc/devil_tweaks/smooth_ui_enabled
echo 300 > /sys/devices/virtual/misc/backlightnotification/blink_maxtime
echo 1 > /sys/class/rfkill/rfkill0/soft

edit5: There's selective OC now... But what about OC per each cpu step? :)
[Galaxy S I9000 Android Development] erpurohit:
From where i can download .84?

Sent using i9000 running Doc's Master 4.0.4
[Galaxy S I9000 Android Development] jelle2503:
please no. enough of these questions

go view DerTeufel his profile, and view his posts. Find it there, or start reading this thread. In reverse. Around page 450