yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] kevin2516:
dude sasha gray is my girlfriend back off! :rolleyes:

and +1 on that boot splash minus the cm9 thing :p
[Galaxy S I9000 Android Development] ak:
init.d

I have a problem with init.d scripts that seems they don't work.

Phone configuration is:

aokp rom

devil kernel bfs 1.1.6

Permissions configuration under installation are:

set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");

set_perm(0, 0, 0755, "/system/etc/init.d");

With stock kernel and semaphore works all well.

Some of you have the same problem? :mad::mad::mad::mad:
[Galaxy S I9000 Android Development] FadeFx:
Man, besides my gf Sasha Gray looks like an old shoe, and she is mine for real... ;-)

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

tapatalked from vizio vtab1008
[Galaxy S I9000 Android Development] Ashtrix:
Any one getting a green flash for a "millisec" while powering on the device during charging via USB ??

Just for the info ADB's also enabled..

Edit: Just disabled it and it's all fine now..!
[Galaxy S I9000 Android Development] DerTeufel1980:
uploading 1.1.6b right now.

Changelog:

- reverted commits related to memory management and No_Hz mode --> stability of 1.1.5 should be back

- because development never stops: modifications to live_oc (by default live_oc only applies to frequencies at and above 400 mhz, script for changing this will be added later this day)

- changed boot logo again

freqencies affected by live oc can be changend by echoing a value to sys/devices/virtual/misc/liveoc/oc_target

if one writes 800000 into this file, live_oc is applied to 800 mhz and all freq above this
[Galaxy S I9000 Android Development] lightning18:
Thanks DerTeufel1980, I guess it's uploaded now and downloading.

BTW, have you checked on the init.d issue? It seems that the scripts aren't executed (on 1.1.6).
[Galaxy S I9000 Android Development] habylab:
Any reason as to why we still can't change the min CPU to 100?

Sent from my Galaxy S running Slim 2.8 using the XDA Premium app
[Galaxy S I9000 Android Development] sago62:
sorry, I'm in aopk 27.3, is best the bfs or cfs? the cfs seems faster ... right?:confused:
[Galaxy S I9000 Android Development] purpleraintoxicity:
Bfs is the faster. i mean, think about it - B(rain)F(uck)S(cheduler)

cfs suppose to be more battery efficient
[Galaxy S I9000 Android Development] DerTeufel1980:
Init.d is depending on ramdisk, and this is the same since first release with init.d. So it can't be a kernel issue.

Maybe your rom uses another bussybox version as before / others.

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] purpleraintoxicity:
1. great work

2. thanx for the info!!

3. did you get my reports?
[Galaxy S I9000 Android Development] Wendigogo:
Same question again and again ... :mad:

Who cares ! Voltage are quiet the same between 100 / 200 MHz and while increasing frequency seems to increase (how much ?) cpu consumption your battery is drained when you use your phone not in idle mode ! And when it's used cpu's NEVER à 100MHz (or 200MHz).

Enabling 100MHz frequency to gain 10 minutes in idle mode, what a performance !!!

I think there're much more important way to improve kernels than this one ...

PS : nothing with you but I'm tired of reading this "request" in each Devil release.
[Galaxy S I9000 Android Development] lightning18:
I thought it is kernel related, minor issue for me though. I use script manager as a workaround. Thanks anyway. :)

Initial report:

Memory management is indeed better - android.process.media still sucks

The new boot logo is very nice
[Galaxy S I9000 Android Development] FadeFx:
I got a problem after updating to 1.1.6b-cfs-bln-cmc kernel. The cpu is stuck on highest frequency due to kworker/u eating up all cpu time. No idea what causes this.

Edit: forfet it for now, solved by a reboot. Will keep an eye on this...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] Rootax:
Je suis globalement d'accord avec toi, mais sous CPU Spy, y'a du temps passé à 100mhz (200 maintenant, du coup). De mon coté je crois que c'est poweramp qui s'en contente.

(In short I agree but 100mhz is used and enough for some apps)

---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------

Did you do a wipe dalvik cache ? If yes, cpu is used a lot at first reboot.
[Galaxy S I9000 Android Development] XlAfbk:
just had one of my "usual" freezes with Devil_1.1.6b_BFS_BLN_VC_20120306.zip

Unlike the previous time where the screen froze and I had to remove the battery it rebooted to recovery this time after sitting with the frozen screen for like 1 min (or more, not sure when exactly it froze)
[Galaxy S I9000 Android Development] The Broken:
Is it called 1.1.6B because it´s only for the I9000B? Or can i use it on the I9000?
[Galaxy S I9000 Android Development] tobiasth:
LOL ................ :D:rolleyes::D
[Galaxy S I9000 Android Development] Ashtrix:
Check this.
[Galaxy S I9000 Android Development] Rootax:
Another kernel reboot with 1.1.6b. Hope the last kmsg helps.
[Galaxy S I9000 Android Development] rotemkk:
new release working great, no more crashes here for now . great work!!!
[Galaxy S I9000 Android Development] Luka321:
guys i cant find the download link for the new devil kernel 1.1.6 any help pls?

Thank you!
[Galaxy S I9000 Android Development] Rootax:
First post.
[Galaxy S I9000 Android Development] Luka321:
sry m8 but i dont see any download links :/ not messing around i dont see it :(?
[Galaxy S I9000 Android Development] rotemkk:
http://devil.haxer.org/
[Galaxy S I9000 Android Development] siky_dude:
And the Award for blindest character on XDA goes to...
[Galaxy S I9000 Android Development] sago62:
with 1.1.6b bfs vc, when you unlock / unlock the phone background image is a strange flash ...
[Galaxy S I9000 Android Development] Rootax:
At the very end :D
[Galaxy S I9000 Android Development] Luka321:
yea yea make fun of me :P you must me very bored :D
[Galaxy S I9000 Android Development] ak:
I have tested my rom with 3 kernel and the init.d directory don't work with devil.

DerTeufel1980 could you advice busybox version that i can use?
[Galaxy S I9000 Android Development] FadeFx:
Yes, probably thats the case, however i thought the dalvik cache is built during updating apps screen so it should be ready when the system is up.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] siky_dude:
you have no idea ^^
[Galaxy S I9000 Android Development] DerTeufel1980:
well, i am using version 1.8.1, but i do not run any init.d script at the moment.

will test it later, but it should work with this version, as it was working before.

edit: just tested, and working
[Galaxy S I9000 Android Development] Luka321:
Yea guys i have u question regarding devil 1.1.5 bfs, i flashed 1.1.5 bfs and when im charging and using ,y phone at the same time my phone gets hot?

somebody told me that it had to do with the kernel and not the rom, so im talking to you guys? any ideas?
[Galaxy S I9000 Android Development] siky_dude:
This is just pure logic... stop using your phone while its plugged in :)
[Galaxy S I9000 Android Development] ak:
busybox

can you share busybox 1.8.1 please.
[Galaxy S I9000 Android Development] purpleraintoxicity:
dude. Its in the market.

Search busy box
[Galaxy S I9000 Android Development] ak:
busybox

which is in the market you're right, but such an old version you have to compile from source.

The advice you gave is not the best.
[Galaxy S I9000 Android Development] habylab:
I only asked because I thought it was weird disabling the ability to choose it. Thanks for the reply though.

Sent from my Galaxy S running Slim 2.8 using the XDA Premium app
[Galaxy S I9000 Android Development] Eliranu:
Why does the FPS in devil 14.2 is higher than 1.1.6?.. like 5-10 higher
[Galaxy S I9000 Android Development] saszseb:
"Busybox installer" not "Busybox".

Grab "Busybox Installer" from Market and you'll be able to install 1.8.1.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] Mangus_U*RA:
1.1.6 + th alpha 17

compass still not works

depp idle top off doesn't work too.
[Galaxy S I9000 Android Development] Rootax:
Vsync was 65 then, it is 55 now.

Vsync @65 can cause weird colours and others strange stuff sometimes.
[Galaxy S I9000 Android Development] ak:
init.d

I installed Busybox installer from the market and not "busybox".

The older version is 1.8.4.

I solved by changing the kernel, including why you should have everything up to date.

Devil kernel for me is the best, but I need for my rom dell'init. D.

thank you very much :cool::)
[Galaxy S I9000 Android Development] lightning18:
So, is init.d working after replacing busybox?

There are different versions of busybox in zeppelinrox's thread (http://xdaforums.com/showthread.php?t=991276). You might want to try that. :) I tried the latest but still it does not work. I guess I'll have to change ROM.
[Galaxy S I9000 Android Development] cink40:
Use Busybox Installer app (not Busybox app) from the market and downgrade to ....3 and then upgrade back to ....4. That helped me on Slim ROM.
[Galaxy S I9000 Android Development] Wendigogo:
100MHz could be enough for some apps but seeing voltage differences it may not draining your battery really more at 200MHz. And as soon as screen is on frequency couldn't be lower than 200MHz. So the 100MHz stuff is used only when screen is off (aka where deep-idle should work :D). Imho, a working d-idle is more interesting (in draining point) than lowering frequency.

Agree with that. There is an option available you couldn't use : frustrating.

Imho, this option should be removed. Increasing frequency to have more power and decreasing voltage to have more autonomy is usefull but lowering frequency (from 200MHz to 100MHz) when idle is pointless (for me) as explained before.
[Galaxy S I9000 Android Development] drew071:
Hi all

I installed devil kernel and noticed I was not getting didle with it selected on in nstools so I did some invest. Using OS monitor I killed each process one at a time and then monitored the phone for didle.

I found that two things were keeping my phone from entering didle.

1. Beautiful Widgets.

2. Persistent Google search bar in nova launcher.

The later of the two surprised me.

Just thought I would share what I found.

Drew071
[Galaxy S I9000 Android Development] dark_knight35:
That's interesting... but you have this problems with other kernels too, haven't you??
[Galaxy S I9000 Android Development] doc_2nas:
If you really liked to have 100MHz while screen is on just don't use NSTools, that's NSTools bug. And you can use NSTools feature (you can choose cpu governor,io scheduler, activate didle, live oc, undervolt) by writing some script and put it in init.d folder. To check the freq you can use cpuspy or go to system setting->performance->processor

Here's the sample to activate touchwake and set delay to 5 seconds:

#!/system/bin/sh

echo "1" > /sys/devices/virtual/misc/touchwake/enabled;

echo "5000" > /sys/devices/virtual/misc/touchwake/delay;

I've tested it on cm9 build16 and it worked.

And for bln just use bln control app.

Hopefuly it might help. Thanks (credit goes to stratosk, pikachu01, TK-Glitch, and DerTeufel1980)
[Galaxy S I9000 Android Development] Bonvaz:
dev this kernel is great but I continue to have a strange problem,that I report a lot of time :)..my problem is that after open an app like facebook,gmail or whatssapp,using the keyboard is laggy as hell....I don't know why,it's not a keyboard problem because on semaphore all is ok..really,I love your kernel,and it's very good,but this problem doesn't allow me to use it :(
[Galaxy S I9000 Android Development] saszseb:
I tried it on Slim but it didn't work: uninstalled NSTools and used Voltage Control and SetCPU.
[Galaxy S I9000 Android Development] imrock:
ok, i activated deep idle, it worked for some time and then deactivated on its own, and i feel that deep idle gave me a battery drain instead of better battery, so is deep idle worth using on ics??:confused::confused:

Also, could anyone help me get more juice of my device:o, my current settings are:

lulzactive (min 200mhz, max 1000mhz)

deep idle - off

inc CPU load -80%

pump up step - 2 steps

pump down step - 1 step

screen off min step - 6@200mhz

up sample time - 15000

down sample time - 40000

It hardly runs a day's usage but is buttery smooth:p:p and thanks for this awesome customizable kernel:D:D
[Galaxy S I9000 Android Development] doc_2nas:
If I'm not mistaken slim still has a problem with init.d, right?

Have you tried the script using script manager?

Have you named the file for example S35EnableTouchwake (like the rule for naming init.d scripts) and set correct permissions?

I don't know about setcpu but voltage control give the same 200MHz lock when I tried.

Or maybe it's just ROM related, since I managed to liveoc'd and uv'd my phone using scripts in init.d, and I've confirmed those by nstools and voltage control ( I uninstalled them after confirmation).
[Galaxy S I9000 Android Development] DerTeufel1980:
I don't know about slim, but I can tell for sure, that init.d is working well with icssgs and team hacksung build 16 and 17

Sent from my I9000 running Android 4.03
[Galaxy S I9000 Android Development] saszseb:
...and with Slim,too.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] doc_2nas:
Thank you so much DerTeufel.

Just a humble request...would you mind adding 'clear init.d" and "clear nstools" feature in your kernel recovery mode? I really love your kernel, but I miss the features I found in semaphore kernel recovery, I think those features come pretty handy.

I'm really grateful for your work to our SGS. Thanks again DerTeufel. :)
[Galaxy S I9000 Android Development] saszseb:
-No, it doesn't.

-Script Manager? For what?

-What kernel are you talking about?

If the init.d folder is empty and then you flash Devil kernel, the init.d folder will be empty after kernel-flash.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] DerTeufel1980:
yes, i think, i have to add this, but i have to take a look at stratosk's commits before, because i don't know, how to modify recovery menu, so it might take a bit longer
[Galaxy S I9000 Android Development] nemanja066:
Why Touchwake doesnt work (Devil 1.1.6b: BFS_BLN:CMC)?! Team ICSSGS RC4.2! I activate it in NSTools! Previously i used Semaphore :)
[Galaxy S I9000 Android Development] pwlj:
(sry, my fault here)
[Galaxy S I9000 Android Development] Rootax:
Found my phone in recovery mode this morning :-/

I can't post a kmsg right, I rebooted another time after that... I think I'll go back to 15.1 once again... or maybe do a full wipe & a clean install.
[Galaxy S I9000 Android Development] saszseb:
I used Devil only on Slim. I flashed Devil more times over Glitch/Semaphore, but this kernel-flash had never put any script into /etc/init.d.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] saszseb:
You should look at Glitch,too.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] thestudent00:
Can i use the framework-res from this thread from cm build 16 for the cm build 17?
[Galaxy S I9000 Android Development] grzybiarz91:
Does Devil 1.1.6 work with Miui v4?
[Galaxy S I9000 Android Development] doc_2nas:
Oh... I'm so sorry mate, stupid me I didn't get what you meant before:(....

Yes devil kernel doesn't include init.d script, but you can use your own script to control things that nstools does. I just did some mod to semaphore-kernel's scripts to use in devil.

I'm sure devil is the most feature rich kernel, and I really love it :)
[Galaxy S I9000 Android Development] purpleraintoxicity:
can you share the script you have made?
[Galaxy S I9000 Android Development] Loshme:
OC 1.4

Using it with ICSSGS rc4.2 @ 1.4 ghz ... Rock stable! thx
[Galaxy S I9000 Android Development] sthomas38:
Hi,

Using this kernel for a while now. Great work mate! :)

I've just a (noob) question: what are the differences between changing the CPU max frequency and LiveOC? Because when I change to 1.4 GHz it's rock stable but when I use LiveOC at more than 115% around my phone keeps rebooting after typing the PIN (when NSTools starts I think).

Have to flash another kernel to **** up NSTools settings and then my phone can boot normaly.

Thanks, and sorry for my bad English :D.
[Galaxy S I9000 Android Development] dark_knight35:
With liveOC, all frequencies are higher, so you must increase voltages(use nstools). Normal OC only adds a frequency with higher voltages, you needn't change voltages.
[Galaxy S I9000 Android Development] sthomas38:
Ok thanks for your help :).
[Galaxy S I9000 Android Development] saszseb:
If you don't want to use liveOC and Deep Idle, you can uninstall NSTools.

Sent from Slim_ICS_2.8
[Galaxy S I9000 Android Development] doc_2nas:
I don't make the script, I just use it with some mod. Credit goes to ezekeel, stratosk and pikachu01 and also derteufel1980 for this great kernel. It is far from perfect. This is not flashable zip,use rootexplorer to copy the files to /system/etc/init.d and change the permissions to rwrxrwrxrwrx. For the addon please use script manager and execute as root. For minfree, touchscreen, sdcard_readahead please copy the one you choose to init.d folder and change permissions. Reboot after that.

I also use thunderbolt script.

To check clockspeed,voltage,cpu governor, io scheduler use voltage control but don't apply anything (after that you can uninstall+clear data). To check deepidle use the show_didle_stats script. To check touchwake just try it (let the phone screen off by itself, don't use power button to screen of). Or you can use nstools but don't get confused by 200MHz lock (you can uninstall+clear data afterward)

Forgive me if there're errors happen (But I didn't experience it on my phone :)). Thank you.

Edit:add enable bln script (missed called works!!)

http://db.tt/x2ycirhM
[Galaxy S I9000 Android Development] :
Bug Report:

Didle causing music to skip, pause, stutter on screen off.

Steps to reproduce:

Play .ogg file (I have 96kbps) from emmc. Ensure didle TOP=off is working. Let phone enter sleep state (ie, screen off). Music play back will stop, glitch or skip current track.

System:

THS Build 17 (problem exists in all builds). No scripts, no tweaks. Tested with different media players. Tested with Glitch kernel, problem there too. Devil_1.1.6b_CFS_BLN_CMC_20120307
[Galaxy S I9000 Android Development] purpleraintoxicity:
can't reproduce it with aokp m4
[Galaxy S I9000 Android Development] dark_knight35:
Do you use any script to make didle TOP=off working? When yes I think that's the reason.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] :
No, I don't use any scripts. Turned Bluetooth off via console, but that's not the problem. It seems that deep idle, or maybe external sd is not tuned properly yet.
[Galaxy S I9000 Android Development] dalton8:
I've had the same problem since it's been out. My solution, don't use didle.
[Galaxy S I9000 Android Development] :
That's not really a solution...
[Galaxy S I9000 Android Development] Ashtrix:
Works flawlessly on LiveOC and faster Schedulers, coolest boot splash...! ;)

Thankyou DerTeufel :D !!
[Galaxy S I9000 Android Development] roundbelly:
anyone tried it on teamhacksung's build 17?
[Galaxy S I9000 Android Development] purpleraintoxicity:
there isnt suppose to be any prob as it a cm-based kernel.

and i dont recall cm9b17 has any major upgrade.

why wont you go with it and just try?
[Galaxy S I9000 Android Development] karapoutsoglou:
works perfectly
[Galaxy S I9000 Android Development] purpleraintoxicity:
OffTopic: whats up in greece this days?

im not updated for a long time.

'and OnTopic: how is the THSb17?
[Galaxy S I9000 Android Development] karapoutsoglou:
offtopic: just waiting israel to back up cyprus for the natural gas and oil so that we will continue drilling :D:D:D

ontopic: i found it somewhat laggy, so i decided to do a clean install and voila,everything is superfast.

after many updates over updates from version 14 and kernels after kernels flashing the phone became laggy.

did a super clean install and everything feels like galaxy2 :D
[Galaxy S I9000 Android Development] purpleraintoxicity:
offtopic:

i agree. :P

ontopic:

i agree
[Galaxy S I9000 Android Development] Falloutboy2000:
wrong section :-)
[Galaxy S I9000 Android Development] Bonvaz:
derteufel sorry..Is it possibile like on semaphore kernel add some different brightness driver?stock automatica brightness is horrible..too much dark..maybe is impossibile,sorry..anyway the kernel works great,but sometimes becomes laggy without reason,maybe for some minutes..sometimes seems that it's not weaking up from the deep sleep..strange..
[Galaxy S I9000 Android Development] Ashtrix:
Hmm, well the brightness part is an issue from CM rom & yeah we will be happy if we get a driver like that...:o.
[Galaxy S I9000 Android Development] Bonvaz:
yeah :)..it would be great..
[Galaxy S I9000 Android Development] FadeFx:
I don't know what u guys complain about autobrightness, just adjust the levels to your likening and feel good.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] dark_knight35:
:thumbup:Just as I turned auto brightness on, I recognized how strongly we need other drivers for that.
[Galaxy S I9000 Android Development] Bonvaz:
mmm yeah but don't think this is the problem..and this is not a complain man,only a tip ;)..I have nothing to complain because derteufel is doing this for free and I cant want anything..but I was talking about automatic brightness,I know I can simply regulate it,but when I walk on the outside,and maybe there are place that are more illuminated than others ,everyone go from dark to bright side sometimes,and it's a little anooying open everytikme the settings to regulate the brightness manually..automnatic brightness is a great feature in our phone,we can take advantage of it in a better way,I think..but really,if we are talking about automatic brightness and not about fc or real problem this means that kernel is working great ;)..
[Galaxy S I9000 Android Development] FadeFx:
You can even adjust the steps and values that autobrightness uses.

Go to settings -> display -> automatic brightness and check use custom, then go to edit other levels and do your settings...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] Bonvaz:
Tried a lot of times but never reach something good..
[Galaxy S I9000 Android Development] FadeFx:
Then you are doing it wrong... try harder.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] XlAfbk:
I'm not getting any Deep Idle with b14, is working fine with b13 kernel.

Using teamhacksung_galaxysmtd-ota-eng.BUILD14.zip and framework_deep_idle_build14.zip.

Devil_3.0-2.1_BFS_V(R)_LiveOC_DeepIdle_BLN.zip -> Deep Idle TOP=Off working

Devil_3.0-14_BFS_V(R)_LiveOC_DeepIdle_BLN.zip -> No deep idle at all

Otherwise identical settings
[Galaxy S I9000 Android Development] treyy:
Dont kill me for that stupid question. But how can i See if i got deep idle in the nstools.
[Galaxy S I9000 Android Development] sunra0815:
Ok guys, here we go again (hopefully successful this time ;-))

It´s fully based on perkas mod, so go to his thread an say thanks!

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

Furthermore I´ve added all .png´s from this guy:

http://xdaforums.com/showpost.php?p=20951108&postcount=611

I decided to take whose mods because they are already known as stabel and I don´t have so much time now.

I´ve added:

- BT-Fix for DeepIdle

- 2 eastereggs :-)

I´m curious who will find it out first :) (Let me give you a tip: I need it in my car because I prefer to have the cable on the bottom side of the phone ;-))

If you don´t like it be patient, I will make some more mods when I have time to.

Please tell me if something is not working correctly and be merciful with me :)

(Make a backup before you install it to be secure)
[Galaxy S I9000 Android Development] cspiby:
Basically TOP=OFF has numbers next to it, so you have deep idle :)