yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] DaXmax:
@Derteufel

What is the different between 3.1.10 kernels and 3.0.20 kernels? Seems that Nushor (in ##icssgs) compiled those kernels, and some of the members says that it booted faster... So im kinda confused... what are the differences?

*beep**beep* IMDriving...
[Galaxy S I9000 Android Development] ryanmat:
Thanks Der!

Quick update, I decided to switch to the CFS kernel from the BFS and all seems to be working so far. Could it be that BFS is causing some of the trouble?
[Galaxy S I9000 Android Development] FadeFx:
I had the same feeling, i still get some fc's occassionally, but this is the same as with stock kernel. Seems to me like there is some problem with memory management.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] pl4cid:
hi,

have you wiped dalvik cache? you shouldnt do that.

flash again without wiping, do a factory reset and perform a reboot after each zip, better safe than sorry, just to figure out what leads to your bootloop ;)
[Galaxy S I9000 Android Development] AceofSpades90:
Does this kernel has Audience Chip support? I mean i'll be using the captivate kernel(whenever it'll release?) but till then im spamming on this post if that's alright? :p
[Galaxy S I9000 Android Development] FadeFx:
I think you are on the wrong forum, audience chip is built into iphone 4s afaik...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] prbassplayer:
Wrong Captivate, Infuse 4g and probably all the samsung devices on AT&T have audience chip.

One step at a time. Only kernel none native i897 to have audience is the 1 for i9000 GB made by MtCarey. Its not exactly easy to do. Id be happy with just Devil on i897 xD
[Galaxy S I9000 Android Development] tobiasth:
thank you for this great kernel, works great with SlimICS v2.5 :D:D
[Galaxy S I9000 Android Development] lohho:
Some interest facts regarding top on and off.

Iam on 1.1 bfs @ 16 smartassv2 noop.

original framework

Nearly 75% of my di time is t off.

How it's this possible?

Edit: wlan is on and working flawless. Airplanemode is not in use
[Galaxy S I9000 Android Development] cspiby:
Just to reiterate what others are saying, 14.2 is also the best performing for me. 1.x has exhibited lagging once the phone has been running for a while. A reboot usually solves it but it always returns.

Most notable in games and the launcher.
[Galaxy S I9000 Android Development] revthanki:
I can report that this bug is also present in TH 16 using the Glitch kernel. So this appears ROM related and not kernel related...
[Galaxy S I9000 Android Development] FadeFx:
Today out of the blue my wifi stopped working, first i got the on/off loop, and after a reboot it refuses to connect. Here is a log, hope it helps...

http://db.tt/6QF7oCCz

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] spoonymoon:
Everything is working very fine here. had slightly lagging sometmes, but after wipe dalvik and cache...i (not kernel) rebooted couple times on CodeNameAndroid 1.3.3 and the V.1.1bfs

set Nstools scheduler/noop governor performance

Min:default max:1300 OC108

And i goes to deep sleep immediatly recording to nstool/cpu spy..:eek:

Uses no% at sleeping

I think its Absolutely your most brilliant kernel to now Devil.

no other mods..then it´s like fresh made Chinese silk no lags even after use/sleeping :D

You rock Devil Thx :P

---------- Post added at 03:48 AM ---------- Previous post was at 03:33 AM ----------

Had that to once, wiped dalvik and cache,,all gone and working then.

:)
[Galaxy S I9000 Android Development] ryanmat:
Further update...after switching to 1.1 CFS, the touchscreen worked for a bit and then started the freeze on me again. For testing purposes I reverted back to 14.2 to see if it was the ROM causing the issue, but so far 14.2 has been flawless, no freezes. So it doesn't seem like it's ROM related...

I don't know what changes were made that TK-Glitch and Devil both used for the new kernel, but whatever they are, it's causing the freezes on my touchscreen. The only thing I really see in common on both changelogs is the Wifi optimizations and maybe the GPU optimizations.

Der-let me know if you need anything from me to help you try and debug this issue. Thanks again for all the work!
[Galaxy S I9000 Android Development] fylim:
Can Semaphore's auto brightness driver be integrated?

It seems like the only one that works properly ie screen brightness changes according to light levels.

Currently on v1.1 toggling to Auto only measures/adjust it once upon toggling and stays until toggle again.
[Galaxy S I9000 Android Development] rlorange:
Devil 1.1 so far outperforming 14.2 for me too.

I believe the change helping things is min freq set to 200mhz. Will 100mhz engaged as soon as the gpu is engaged then the phone needed to kick up to 200 because the gpu requires this. However this caused lag as the governors are nit set up with this specific requirement.

***Vintage Galaxy S1 running ported Ice Cream Sandwich Android 4.0.3 by OneCosmic***
[Galaxy S I9000 Android Development] traian4u2005:
Hy , Sorry for the question but i have used Slim ICS 2.5 with [KERNEL] Semaphore ICS 0.8.1 and now i want to use the devil Devil 1.1 KERNEL , i have flashed it in cwm and now the problem I have is that : where i can change configurations of kernel because in the semaphore kernel it was that app .,.,
[Galaxy S I9000 Android Development] FadeFx:
Get nstools from market.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] rlorange:
Yep ns tools is THE app for ICS kernels including Semaphore

***Vintage Galaxy S1 running ported Ice Cream Sandwich Android 4.0.3 by OneCosmic***
[Galaxy S I9000 Android Development] TheNikkoMan:
This confirms what I've been testing myself.

Some pages back I proved that you could get TOP=OFF time with airplane mode on. I've now found out why, thanks to jcolinzheng. In this thread, he said he only could get deep idle by

echo 1 > /sys/devices/platform/bt_rfkill/rfkill/rfkill0/soft

I tried this with stock framework, and I got TOP=off time. Moreover, it seems that entering airplane mode does this for you, explaining what I found.

It's important to note that, after applying this, your Bluetooth will not work until you set it back to 0.
[Galaxy S I9000 Android Development] FadeFx:
Thanx, that did it for me as well...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] MasterJam882:
Hey all

today I flashed from 1.1 LED to 1.1 BLN...after that I wiped cache and dalvik cache, entered nstools and wiped cache there too...

But when I enter NStools now I have both settings...for CMLED and BLN

Dimming function from earlier versions is not there anymore as well and blink intervall is not available...

and minimal frequency is 200 and not 100 anymore and when I want to set it to 100 nothing happens.

is this normal?

greetz
[Galaxy S I9000 Android Development] .:Crack:.:
Teufel,

I took this from a git commit (1.0_fixes branch):

"When the GPU is active the minimum frequency is adjusted to the second

lowest frequency taking into account the current OC value."

So when the GPU is not active it should use 100mhz shouldn't it? So for example when listening to music the GPU actually doesn't have a purpose to be active, so the CPU freq should be 100 mhz, shouldn't it?

If that is the intention (IMO it would be the best and most rational) it does not work. The CPU is at 200mhz while listening to music (screen off).

Can you make it work correctly?

Thanks
[Galaxy S I9000 Android Development] NickDunn:
just installed Devil 1.1 BFS BLN VC in Asnet MIUI v4 v1.3,

its showing Kernel version "unavailable" in the about phone.

thanks for the kernel.
[Galaxy S I9000 Android Development] prbassplayer:
That's good in theory. Remember using music app will make the OS use cpu.
[Galaxy S I9000 Android Development] .:Crack:.:
Sure, CPU but not GPU. And in order to play the music the cpu does not need mor than 100 mhz ;)
[Galaxy S I9000 Android Development] DerTeufel1980:
It is working correctly. The overclocking apps aren't.

I will upload screen state scaling script to correct this behaviour, as soon as I have enough time today.

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] .:Crack:.:
Echoing 100mhz - 1000mhz while screen off?
[Galaxy S I9000 Android Development] DerTeufel1980:
Echoing 100 as min freq while screen off :)

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] fabrizioguess:
Thanx a lot...I've re-flashed without doing a dalvik-cache and it's all right!
[Galaxy S I9000 Android Development] pl4cid:
youre welcome :)
[Galaxy S I9000 Android Development] DerTeufel1980:
ok,

i just edited the screen state scaling sctipt, which i found on my pc.

all it is doing, is echoing min freq when screen turns off.

i do not have the time zo check if it is working, but in worst case, it just dies nothing ;)

remove extension and place it in init.d (check the permissions) and then reboot. after that, min freq should be "fixed"

if you already have a script in int.d, named like this one, just rename it ;)
[Galaxy S I9000 Android Development] fylim:
Thanks. Works fine
[Galaxy S I9000 Android Development] demon_da:
I Enabled Deep Idle And After the Night I Checked Idle Stats On NSTools & Deep Idle & It Was Like (Top Off = 0) , I Dont Know If That's Ok?!?! (Top On) Wasn't 0 By The Way.
[Galaxy S I9000 Android Development] qpakao:
I have problem

I9000 RC4.1 Devil CFS 1.1 LED2

When I'm on 2g and start to download or upload something (example browser use) my screen starts to behave strange horizontal fluctuation.

Is it kernel or rom related?

Want to ask before I start switching kernels ;).
[Galaxy S I9000 Android Development] tomatenjungee:
Deepidle kinda not works for me (looking at the nstools stats). I put the your scaling script in init.d (without extensions) ... gonna try flashing the modded framework.

tried something else ... could it be that deep idle only works with LAZY gov ? I read that in your faq but you wrote he gives the tip to use it. SmarASS was more snappy for me ... but ok gonna try lazy ;)

With lazy deep idle works for first 9ms till screen turns off itself :/ then it doenst ... really confusing. I closed all apps. Swype service is running but mh
[Galaxy S I9000 Android Development] {Angel}:
Cool. Another thing that can be done in this script is switch governors also. Thanks for the script.
[Galaxy S I9000 Android Development] FadeFx:
Ok, so after your hint solved my problem (thou i were on an older kernel version when wipeing) it was ok for a day using 1.1 kernel, but then came back, possibly due to a reboot while connected to a charger. I tried a few times to wipe cache/dalvik cache, but wifi kept power cycling. So i flashed back to 14.1 led kernel and wifi was starting up normally. I think i will stay on 14.1 for now untill next version comes out.

DerTeufel, you possibly should have a look at how nikademus handled the fugumod kernel for cm7, he pushed every change to github, so he had a full changelog throught commits and he released a new version containing only a few changes, this way it is easier to track down bugs.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] purpleraintoxicity:
i agree too.

its the best way to keep the kernel at best shape
[Galaxy S I9000 Android Development] ryanmat:
I don't know if you saw my post a few pages back, but it looks to me that the biggest change that was both on Glitch kernel and Devil kernel in the recent changelogs is the Wifi optimizations. I know someone mentioned that they were getting freezes on Glitch too.

I'm on 14.2 and it's been flawless for 24 hours. So, I think maybe the cause of my touchscreen freezes and your wifi issues could be those new optimizations. Just a thought, but I'll wait to hear from DerTeufel as he knows best :)
[Galaxy S I9000 Android Development] DerTeufel1980:
you are right. the change of wifi driver is the only thing, what we both have changed (as far as i could see it on glitch's github).

but it's not very obvious, that wifi is causing freezers of lockscreen.

i push every single change to git, but i pushed it to github the-devil by fault. it will come back to my normal github, but at the moment i need the time for other things (fixing min freq, bln, ... ) ;)
[Galaxy S I9000 Android Development] .:Crack:.:
Teufel,

if echoing 100000 on screen off it stays at 100000 even on screen on.

Don't we have to echo 200000 for screen on?
[Galaxy S I9000 Android Development] DerTeufel1980:
not sure about the echoing, did not try it by myself.

at the moment i am working on really fixing this, without a silly script.

edit: min 200 is set by gpu, no matter what you echo before
[Galaxy S I9000 Android Development] FadeFx:
If those wifi optimizations were not present in 14.2 it cant be tge fault, as i could reproduce it now with 14.2 as well, only difference was that a unpluged reboot solved it now. But it could also be related to a strange timeing issue triggered by tasker enabling wifi in a wrong moment together with bluetooth but i think i will not find out today as it is late and i have no more passion for testing today...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] :
This works in respect to activating DIDLE TOP=OFF, but I get soft reboots when activating wi-fi after running this command. Not really a workable fix :-(

Shame, because it really boosts battery life a lot for me
[Galaxy S I9000 Android Development] rlorange:
I added this script to the screen state scaling script and then echo 0 revert command so it only deactivates bt when screen is.

Works great top off all the way

***Vintage Galaxy S1 running ported Ice Cream Sandwich Android 4.0.3 by OneCosmic***
[Galaxy S I9000 Android Development] rlorange:
****Bluetooth Disable for DIDLE Idle full top-OFF enable script***

NOTE! This can be used on ALL ics roms running a kernel with deep idle and init.d support.

This zip will add a modified screen state scaling script which will disable bluetooth every time the screen is off to enable full deep idle mode. Rc4.1 came with a modified framework which did the same thing however this causes the infamous "wifi bug" because the mod was permanently on.

With this script Bluetooth is re-enabled when the screen turns on so it should eliminate the problem. Deep idle only engages when the screen is off anyway so hopefully this is the ideal solution.

NOTE: this may cause wake up issues and I'm still testing so if it bugs out simply delete the screen state scaling script in /system/init. d

Note: flashing many kernels will clean this script from init.d folder so you will have to re-flash the zip if you change kernel.

To test if it is working switch on wifi and then turn the screen off for 30 seconds. Using NS tools look for didle stats if it shows Top-OFF activity then its working :)

http://db.tt/hQeYRaxz

Bluetooth Disable for DIDLE

***Vintage Galaxy S1 running ported Ice Cream Sandwich Android 4.0.3 by OneCosmic***
[Galaxy S I9000 Android Development] pckoloji:
b16 clean + devil 1.1 bfs bln (touchwake disabled, diddle enabled, sio, lazy)

1-performance is great but sometimes during unlocking screen freezes and cant detect touch. anyone?

2-can anyone tell what is advantage of enabling touchwake. screen can still detect touch but what is it good for? faster wake?
[Galaxy S I9000 Android Development] Tilgi:
1: Sorry, haven't had that problem with 1.1

2: That is for the case when your screen turns off by itself (not by pressing the power button), then you are able to turn it on again only by touching the screen instead of the home button
[Galaxy S I9000 Android Development] xBenny:
1. i have same problem with unlocking
[Galaxy S I9000 Android Development] pckoloji:
1-i guess glitch 14b3 has same problem because in the list for b4 plan it says fix for touch screen unlocking freeze.

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

2-yes i got it but isn't it sucking more power during touchwake enabled period (ex 45 secs). pushing home button is not much different for me than touching screen.
[Galaxy S I9000 Android Development] DerTeufel1980:
if you don't like touchwake, you can just disable it. also you can reduce the time to save some batterie.

the big point of touchwake will be, when roms are implementing a lockscreen, which activates after a defined period of time (after screen off).
[Galaxy S I9000 Android Development] tomatenjungee:
I dont know what i am doing wrong :/ didle for the first 9ms when screen turn itself of after reboot. Then no didle when turning off the screen manually.

Sio, Lazy, DIDLE on in nstools .... no top-off.

Flashed your screen stalte scripted (everything mounted), checked init.d folder.

Killed all apps ...dunno what i missed :confused:

:/
[Galaxy S I9000 Android Development] rlorange:
I'm on CNA ICS... did you flick wifi on? This will instantly enable didle. You will still see some top-ON before the script kicks in.

Remember didle doesn't kick in unless something is active while the screen is off. If nothing is happening like wifi or music playing it will go to the deeper idle of deep sleep

***Trusty old SGS1 running CNA ICS and Devil kernel***
[Galaxy S I9000 Android Development] FadeFx:
I think this script is no good practice, at least for me, as i use my device in car connected to my parrot enabled car stereo via bluetooth. This means the connection will be lost as soon as the screen goes off... ?!

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] rlorange:
Yeah its not good if you use bt. Maybe someone with more knowledge and skill can improve it to detect if bt is in use?

***Trusty old SGS1 running CNA ICS and Devil kernel***
[Galaxy S I9000 Android Development] GreatVortex:
I'm on CNA ICS and devil 1.1, flashed script but didle not working. If i enable wifi than it works perfect but with wifi off it is not working.
[Galaxy S I9000 Android Development] rlorange:
It is working didle will only kick in when something is running while screen of like wifi or music.

Did you get Top-OFF stats? That's what the script is supposed to do allow the deeper top-OFF mode when didle kicks in... just like the modded framework did but without screwing up wifi

Try the script playing music with headphones plugged in. If you get top_OFF stats then this means the deepest didle is working. It saves me 30% battery drain playing music

***Trusty old SGS1 running CNA ICS and Devil kernel 1.1BFS***
[Galaxy S I9000 Android Development] GreatVortex:
ok it's working. I have another question. Why i have a green screen popup when i want to unlock phone?
[Galaxy S I9000 Android Development] rlorange:
Green screen popup? I'm guessing its voodoo colour related. I don't have it.

Everyone this script def kills Bluetooth completely even after waking up I'm going to see if I can find a way to at least have bt working when screen is on.

***Trusty old SGS1 running CNA ICS and Devil kernel 1.1BFS***
[Galaxy S I9000 Android Development] id.goPLAY:
Hey people,

did somebody know the Change log for Devil 14.2 LED and why is this kernel faster (not at all) that other vesrions?!
[Galaxy S I9000 Android Development] kamalmawa:
Yeah I'm definitely getting both Top= Off & On after running this script. This is awesome for me at the moment as I hardly use Bluetooth. Hopefully you will figure out how to get the Bluetooth working after screen is on so everyone else can use this. I usually listen to music 5hrs straight on weekends will let you know how it goes with DIDLE. Thanks again for this.

PS: couldn't use modified framework as it always broke my Wi-Fi
[Galaxy S I9000 Android Development] GreatVortex:
Thx for the help. i flashed devil 1.1 bfs led2 with no vodoo colour and green screen is gone.
[Galaxy S I9000 Android Development] xBenny:
Same problem with BFS BLN version. VC make green screen when locking phone. without VC is locking OK.
[Galaxy S I9000 Android Development] festr:
I'm on ICS build 15 and devil 1.0 cfs. I've fleshed 1.1 CFS BLN VC and screen state script. after boot phone is freezing and softrebooting whole system. I've spot that kworker process is taking all the CPU. I've tried clean cache and dalvik. I've flashed back 1.0 cfs and screenstate - same behaviour, kworker taking all the cpu and system is frozen. I've flashed 1.1 cfs bln vc WIHTOUT screen state script and system is OK and wifi works.

Now tell me, why screen state script is causing this? Also modified framework casuses wifi to not work.

---------- Post added at 02:46 PM ---------- Previous post was at 01:52 PM ----------

what does it mean if I've 64000ms in TOP=off after 30 minutes?
[Galaxy S I9000 Android Development] cspiby:
In 14.2 was the GPU definitely overclocked?
[Galaxy S I9000 Android Development] XblackdemonX:
I don't think it ever was overclocked in the first place
[Galaxy S I9000 Android Development] cspiby:
Just I've heard this multiple times and the AnTuTu scores kind of support this, but I wondered if this is indeed the case, what clock speed it was set to in 14.2

Found the post, the GPU was clocked at 250mhz rather than the default 200mhz in 14.2
[Galaxy S I9000 Android Development] traian4u2005:
how can I remove that kernel animation from the phone startup ? because in the beginning I have the samsung i9000 logo , kernel animation and after that the animation of the startup , i think i too much.,,,.,or how can i keep just the third animation(startup animation)?
[Galaxy S I9000 Android Development] Sacob:
yesterday i had a soft reboot. does this happens to someone else or is it just me?
[Galaxy S I9000 Android Development] siky_dude:
Afaik, the gpu WAS overclocked.
[Galaxy S I9000 Android Development] ShadedCyan:
The change log wrote something about the CPU being set to the second lowest frequency when GPU is active. Doesn't this kills more battery life? And is the gain in performance in this substantial?

Does didle top off work with AOKP? Anyone tested the script on the kang rom?
[Galaxy S I9000 Android Development] FadeFx:
You cant, except if you compile the kernel by yourself...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] rlorange:
f

No problem some smarter peps than me figured out the command in this thread and all I did was use the thunderbolt script to make it work.

I'm actually pretty noob with code of any type so PLEASE if anyone knows more improve upon this.

No idea what the command is but some kind of command could check for Bluetooth activity and stop it deactivating when in use

***Trusty old SGS1 running CNA ICS and Devil kernel 1.1BFS***
[Galaxy S I9000 Android Development] rlorange:
No problems... this is a long standing bug if VC.

If you are on CNA ICS 1.3.3 Then it comes with the updated "galaxy s settings" app or "Aries parts". You can control colour settings just like voodoo control app does with a voodoo colour kernel.

Until recently full gamma control like you get in voodoo colour was only available to cm9 users. Will full control cm colour is on par with VC but not green flash glitch...

I am a fan of voodoo from froyo days and the dev, supercurio even said VC was and ugly hack he never really held in high esteem so it's no disrespect when I say that with full gamma/nDMIe control cm colour has made it obsolete ...

In my opinion:)

***Trusty old SGS1 running CNA ICS and Devil kernel 1.1BFS***