yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] KennyLegend:
I doubt it.... You'll have to get the voodoo louder app first.
[Galaxy S II Original Android Development] KennyLegend:
It underclocks the cpu and gpu to make it more battery friendly.
[Galaxy S II Original Android Development] KennyLegend:
V2.6.1 with conservative governor is bloody insanely fast !!

Smooth too...
[Galaxy S II Original Android Development] hwwr:
Thank you kennylegend.

if i. would like to revert bak towthe default clock speed after flashing the battery zip wad shud i do?

Do i also hab to do any special stuff whn flash to newer kernels? like making it bak to default.
[Galaxy S II Original Android Development] KennyLegend:
You could use voltage control app to alter the clock speed. when changing kernels just click menu, remove boot settings in voltage control app.
[Galaxy S II Original Android Development] Entropy512:
If the phone enters deep sleep, and is unable to wake up for whatever reason, it's called the sleep of death. It can be caused by a variety of things:

1) Bugs in suspend/resume code that directly cause a kernel panic/crash (Haven't seen this yet on the S2. Happened a lot for xdandroid because all of the drivers were reverse engineered)

2) One of the CPU or bus voltage settings is too low, and the CPU hangs

3) This is sort of related to 2), but Samsung processors always come out of deep sleep at 800 MHz. If the regulators are set to a voltage that doesn't support 800 MHz, the CPU will hang. 90% of SiyahKernel SoDs are in this category.

The reason people keep mucking about with suspend frequencies/voltages despite the high risk of SoDs when you mess around with that code is because in the situations where the phone wakes up to take care of a very quick task (like battery polling), it may spend around 800 msec at 800 MHz even if it only has to do a few milliseconds of real work.

A number of people have done testing on this - The logging facilities used for dmesg and logcat have negligible effects on performance. You're averaging a couple of bytes per second to a resource that is capable of on the order of a few gigabytes per second.

People forget that unlike desktop Linux systems where the log goes to a filesystem on disk, on Android devices the logs for both dmesg and logcat only go to a circular buffer in RAM. The only way these will have a significant effect on performance is if a driver is WAY too chatty and spams the log - in this case the driver needs to be fixed (such as, for example, the AFTR code needs a healthy dose of STFU when AFTR is enabled, otherwise dmesg gets filled with AFTR entry/exit printk()s), disabling logging entirely is throwing the baby out with the bathwater.

The benefits of logging for the purposes of debugging greatly outweigh the negligible penalties.

Background processes don't actually run during deep sleep (after all, they can't since the CPU is totally stopped) - they set timers that will fire an interrupt to wake them up when they need to run.

In addition to all this, the CPU will shut off many peripherals. This is where the bulk of the power savings comes from. It's why a phone in deep idle (but not deep sleep) such as AFTR mode still consumes quite a bit of power compared to deep sleep. This is the main reason it takes a while to wake up from suspend, some peripherals (such as the radio, which interfaces with the CPU via an internal USB bus apparently) take a while to resume. Apparently Motorola was working on a "quickwake" mechanism where a device waking up for a background task would only resume the peripherals it needed - I'm not sure if any existing device has this yet.

Modern CPUs can clock-gate the CPU core even when idle - I think this is why power consumption actually seemed slightly worse when I experimented with 100 MHz support on my phone - 100% duty cycle at 100 MHz was worse than 50% duty cycle at 200 MHz, with the CPU clock-gated in deep idle 50% of the time.
[Galaxy S II Original Android Development] hkfriends:
Bug, cannot long pressed icon in the main screen
[Galaxy S II Original Android Development] MPKO:
Thanks for the great kernel. 2.6 with bat optimization.zip + UV and no problems at all.

Cheers
[Galaxy S II Original Android Development] radicalgel:
which scheduler u on?
[Galaxy S II Original Android Development] chetasus:
what condition your phone stays over night i.e WIFI on/ off. Data on/off etc please?
[Galaxy S II Original Android Development] spelaben:
The voodoo control app tells me that 2.6.1 is not a supported kernel, I thought the driver is enabled in the new version. Am I missing something?
[Galaxy S II Original Android Development] shahulvm:
Thanks Entropy, this is what I was precisely looking for..few more queries

1. deepsleep_cpulevel -> does this parameter define the mhz that the cpu should use while coming out of deep sleep or does it indicate that it should be last set freq before going to deep sleep. Whats the impact of having this at stock and having it lowered to 800

2. Do you intend to say that 100mhz isnt really good in idle mode as i feel its quite useful during active state. (ie use off-screen profile setting without 100mhz and on-screen profile setting with 100mhz)
[Galaxy S II Original Android Development] bala_gamer:
Yes you are missing a lot. Supercurio has only enabled louder volume with modified drivers for s2, it is not voodoo sound and it will never come to s2.
[Galaxy S II Original Android Development] DirkTeur Velserbroncx:
Then i must be missing something to because mine sounds the same as before

can't tell any difference with or without the drivers
[Galaxy S II Original Android Development] melorib:
I also reverted, but to CM7 original... :rolleyes:
[Galaxy S II Original Android Development] iron@ss:
Am on v2.6.1 and loving it... however, I now have 3 versions of the siyah_battery.zip.

The first was downloaded when v2.6_S99 was released.

The second is the amended battery.zip fro the same kernel

The third is one I downloaded from v2.6.1 blog early this morning (just in case there was a difference).

Using the 3rd version with Automatic Brightness, in Display, as I usually do... it is much darker than either versions 1 or 2.

I have reloaded all 3 to test again and 3 (the latest from the v2.6.1 link) is definitely a lot dimmer.

I have now switched back to the amended battery.zip from the last kernel.

I was just wondering if anything had been changed in version 3?
[Galaxy S II Original Android Development] melorib:
Wifi, data and BT OFF, service, widgets, alarm, etc ON
[Galaxy S II Original Android Development] minidou-77:
Look by yourself into the etc/init.d folder -> 01siyah.sh if there is anything related to brightness ;)
[Galaxy S II Original Android Development] minidou-77:
@iron@ss

You're right the last battery.zip changes the brightness :

echo 70 > /sys/class/misc/brightness_curve/min_bl

echo 0 > /sys/class/misc/brightness_curve/min_gamma

echo 19 > /sys/class/misc/brightness_curve/max_gamma
[Galaxy S II Original Android Development] iron@ss:
Thanks.

The 3 brightness settings in version 2 of the siyah_battery script start... echo 50, 0 and 20.

Whilst the latest version 3 (from the 2.6.1 blog) script has... echo 70, 0 and 19.
[Galaxy S II Original Android Development] minidou-77:
Sorry my ability to answer you stops here I don't know anything about the settings ^^
[Galaxy S II Original Android Development] sadonlyone:
on v2.6.1 it seems to happen (like every time phone "boot faster" than other kernel versions), that wifi cannot connect anymore to my router. I assume that is not a router problem (linksys wrt54gl and works wonderful). I did dalvik cache wipe but no success. rolling back to v2.6_S99 and wifi working fine.

I repeat, in every kernel that appears "faster boot" wifi cannot connect anymore to router. I hope it helps.

edited: after reflashing steps: v2.6.1, v2.6_S99, v.2.6.1 wifi work after a couple of tries in phone wifi settings (but it does not connect automatically)...

re-edited: after a dalvik cache wipe again and flasing v2.6.1 works fine everything. best kernel so far
[Galaxy S II Original Android Development] radicalgel:
I use the battery.zip ver3 with Siyah 2.6 and noticed the same thing. Lowest brightness was much lower than stock or even speedmod (which has reduced lowest brightness lvl). I also realized that auto brightness no longer worked and just dimmed the screen to lowest brightness when it was turned on. can you tell me auto is working for you?

I however, didn't test auto brightness outdoors. Could be that the auto brightness has been made less sensitive causing it to bump up brightness only at much higher lux level readings.

I am currently on 2.6.1 defaults with no issues. Does the battery.zip really help that much? I am in a dilemma as to whether to flash it or not. :p
[Galaxy S II Original Android Development] iron@ss:
Mine too! :D

Know your limitations is my motto.
[Galaxy S II Original Android Development] radicalgel:
Haha. I think most people know by now that voodoo sound will never come to the S2, but a lot of us, me included, don't wanna believe it. :p
[Galaxy S II Original Android Development] nk7:
Damn is it not possible at all? Even if we did a bit of tweaking ourselves for the S2 - just that everything else in the S2 is so customisable. I would have loved this voodoo control app.
[Galaxy S II Original Android Development] vnvman:
Basically it won't come because it would be pointless: sound quality on this sucker is too poor to bother with. In the end i got tired of raging against this phone and got a dedicated music player, now i'm finally happy ;)
[Galaxy S II Original Android Development] malavan:
do we have this on 2.6 better sound.

https://github.com/project-voodoo/mc1n2_voodoo
[Galaxy S II Original Android Development] manyakurt:
we have nearly 17 second boot time with 2.6.1 on miui
[Galaxy S II Original Android Development] bala_gamer:
here

http://xdaforums.com/showpost.php?p=20583527&postcount=14233

and yes it has been included in the latest 2.6.1 kernel
[Galaxy S II Original Android Development] WebReaper21:
If you want to know more about how those settings work, they are explained in droidphile's thread:

http://xdaforums.com/showthread.php?t=1369817
[Galaxy S II Original Android Development] Cygnuss:
Just flashed 2.6.1 + performance.zip and wowww this is really fast and i am only 100-1000MHz
[Galaxy S II Original Android Development] donchen:
Can anyone share SiyahKernel 2.5.1 GT ?

I used 2.6 and didn't really like it. I want to revert back to SiyahKernel 2.5.1 GT but i can't find the download link either on the first page or on Siyah's website.
[Galaxy S II Original Android Development] xsycox:
2.6 was great.

2.61 is draining again like 2.4 and 2.5 did before.

Everything else works like before.

I used cleaning, then kernel and then battery from 2.6.
[Galaxy S II Original Android Development] hwwr:
Hi all, i would like to check if theres more battery drain with 2.6 and 2.6.1 as compared to GT 2.5.1
[Galaxy S II Original Android Development] Shinfei:
Gokhan lower the 0 level of brightness. Put 1 instead the script to have the stock one or near ;-)
[Galaxy S II Original Android Development] KennyLegend:
You won't hear any difference till you install the "louder" app that Supercurio is about to release !!!!!!!
[Galaxy S II Original Android Development] KennyLegend:
Lowest brightness level is definitely a lot lower on 2.6.1.
[Galaxy S II Original Android Development] Shinfei:
With a battery script ? Cause for me at 0 gamma, it's the same that 2.6
[Galaxy S II Original Android Development] oxwald:
Same here (2.6.1 + battery)

Very very low brightness level. For me maybe too low..

Is the maximum level also affected? Because I think so.
[Galaxy S II Original Android Development] squall_kay:
do i need to flash lionheart script after installing 2.6.1 or defaults it's good enough?
[Galaxy S II Original Android Development] Molitro:
For all the ones whining about the brightness, just copy the old battery.zip brightness settings on the new one. Not that hard.

Actually, the explanation it's a bit diferent.

The first SGS had a sound chip that was very unexploited. supercurio made that chip give all it has.

S2, on the other hand, has a worse chip, that sounds worse than the SGS' one with voodoo, but better that stock SGS. The problem is that samsung already exploited the chip, so there is nothing else for supercurio to do.

It was a bummer for me going from voodoo to what S2 has, but I don't think it sounds that bad.
[Galaxy S II Original Android Development] KennyLegend:
I actually prefer it ;)
[Galaxy S II Original Android Development] droidphile:
1) If no background processes runs during deep sleep and CPU is completely powered off, how are the wakelocks from alarm manager and power management handled during deep sleep. And how does system respond to an incoming call or message. How are these handled without any cpu activity? Without CPU, can these kind of interrupts wake/resume needed background processes? I can digest CPU 'mostly' powered off, but can not understand completely powered off.

2) Obviously all idle modes except deep sleep will consume comparatively more power since no hardware is shutdown during IDLE, or AFTR, etc

3) Idle cpu may use clock-gating for eliminating the need for switching by flip-flops. But when i said cpu does not clock anymore during deep-sleep, i meant the frequencies are not scaled up or down anymore.

4) If CPU itself is completely shut and it shuts many other peripherals down, what cause the gradual and slow battery drain during deep-sleep. (not considering wakelocks/scree-on, because we're talking about only drain in deepsleep time, ie elapsedRealtime minus uptimeMillis).

This is no debate/justification, but my genuine doubts.
[Galaxy S II Original Android Development] haroonasla:
Defaults vs no script

Guys, I just want to know if i don't flash any script i.e. battery, default or performance, what will the kernel default to ? Will it be equal to settings of "default script" ? or will there be any difference if i flash "default script" over the kernel ?
[Galaxy S II Original Android Development] donchen:
Anyone please?
[Galaxy S II Original Android Development] el_liberator:
here : http://dl.dropbox.com/u/26340739/Siyah-GT-v2.5.1-CWM.zip

;)
[Galaxy S II Original Android Development] radicalgel:
Well I don't know if it's just me but with good IEMs the S2 is not bad at all. Just fiddle around with the PowerAMP EQ and also add the equalizer app settings. Sounds pretty dang good to me. :)

Check my sig for further details! :p
[Galaxy S II Original Android Development] donchen:
Thank you sir very much
[Galaxy S II Original Android Development] oxwald:
Actually I think I now prefer the new setting too. :p

But anyway, the option to customize it is awesome!! : )

Edit: 2.6.1 + battery = No problem so far & the best kernel tried till today! : )
[Galaxy S II Original Android Development] b2rdetor:
i sets max CPU to 1400mhz and cant understand anything.

1. my antutu score now 4500-5000 (always different)< but with 1200 max its 5900-6000+

2. CPU can scale down freq to 800mHZ but loading is a 100% (can see with cool tool app) during CPU and other tests!!!!!! it can be not only with antutu - GTA3 (during game CPU sets to 800 and game became like slideshow) and every app too.

3. tryed to remove any boot settings (battery like) but its cant help me.

4. with 1200mHz CPU freq scales down to 800 (with 100% CPU load) too but not so often

tryed all governors, but only performance bug less

reverted back to 2.4.2 and bug is gone, but now freq scales down from 1400 to 1200.
[Galaxy S II Original Android Development] Shinfei:
Just put an higher min_gamma 1 or 2 instead of 0 and the min_bl at 30 like stock ;-)
[Galaxy S II Original Android Development] haroonasla:
Anyone ?? do i need to flash defaults script ? or just the original kernel only will suffice to get on defaults ?
[Galaxy S II Original Android Development] bala_gamer:
The touch response is much better than any other version of siyah. Is it just me or is there any real changes?
[Galaxy S II Original Android Development] stylez:
As long as u remove boot settings from set CPU or VC before install and wipe dalvic & cache before flash there is no need to flash default.zip...

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] b2rdetor:
can anybody test 200-1200, 200-1400 conservative with antutu???
[Galaxy S II Original Android Development] SilverMist1:
i want to know that too..
[Galaxy S II Original Android Development] iamsmallpang:
Turkbey v29.4 flashed v2.6.1 add performance zip

smooth and very fast

battery life is good
[Galaxy S II Original Android Development] droidphile:
Not just you :)

Touch sensitivity is set to 40 as threshold and the 'vitalij value' as usual, is set to 5.

You can control both values. 2nd param using Touch Move app and first using:

echo "50" > /sys/devices/virtual/sec/sec_touchscreen/tsp_threshold

Possible values between 40 & 80. Higher value = lower sensitivity :)

I find 50 to be more friendly for me in situations like scrolling a text file and trying to set cursor in between words.

No need to flash defaults.zip as long as other init.d script/voltage control/setcpu or any similar app does not override some tweaks.
[Galaxy S II Original Android Development] veyka:
There will still be battery drain in deep sleep as enough hardware will be on to give the cpu 1000mv across the electrodes when it needs to wake up to, lets say, take an incoming call, etc.

Basically the main bits of the soc are powered down, but there are "life support" parts that consume minimal (but still some) power.

I don't know the technical details but this is what I get the impression happens.
[Galaxy S II Original Android Development] KcDaRookie:
Siyah 2.6

Conservative

Deadline

Antutu Benchmark v2.5 (newest atm)

200-1200: 5952

200-1400: 5264

With OndemandX and bfq

200-1200: 5955

200-1400: 4387

Hmm.. lower scores on higher freqs?

Anyone else can confirm this?
[Galaxy S II Original Android Development] b2rdetor:
not only that bug

CPU scales down to 800, 1000 when 1200 100% load. cant understand WHY???

if you set max CPU1400 CPU will scales down to 800 much more agressive (that is cause why antutu1400<antutu1200)

i am cool tool user and that utility show current CPU freq in real time

example:

i launch 3d game (need for speed, gta3) and when its launched CPU works with max freq, but after a few min playing CPU scales down to 800 even if it was loaded with 100% at max freq. WHY???

its governors independed...

with 2.5.1 bug is appears.

2.4.2 scales down to 1000mhz but only when its need (CPU load too small)
[Galaxy S II Original Android Development] droidphile:
That 'enough' hardware which are not powered down and which separates the two states: device powered-off and in-deepsleep, is what i'm wondering about. What hardware handles interrupts such as pressing home button to wake the screen and/or resume suspended services, if cpu is completely powered off like entropy says.
[Galaxy S II Original Android Development] stylez:
2 posts above yours really can't be that hard to read responses? :eek:
[Galaxy S II Original Android Development] SilverMist1:
do we need an app in order to use "mc1n2_voodoo sound module" and boost the volume? or does it boost volume automatically?

---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------

sorry, i must have missed it.
[Galaxy S II Original Android Development] lpsi2000:
I am glad you are in here checking things out but you will much more of the same:D
[Galaxy S II Original Android Development] Bushido76:
Hey droidphile,

I found the following links, which could proof entropy being right:

http://developer.android.com/reference/android/os/SystemClock.html (section uptimeMillis)

http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_PortingGuides (Section Introduction).

It seems, that device controllers and device drivers can handle things independently from the CPU.

Bushido
[Galaxy S II Original Android Development] lrbpereira:
Is it possibile to enable multitouch in CM7 roms? Found that multitouch works well in the app multitouch visualizer but it don´t work in the desktop ou appdrawer.

?

Thanks
[Galaxy S II Original Android Development] Bushido76:
Hey Entropy,

thank you for your response and your opinion. I used the word "philosophical" because I think the influence is marginal too. But like your example with the AFTR source code I'm not completely sure that there are no other parts, which "overdo" the logging. In my eyes all parts which are critical for runtime should get an optimization - not only in reference to logging... ;) So I try to keep (almost) everything slim. ;)

Bushido
[Galaxy S II Original Android Development] luizffgarcia:
Let me see if i understand this.

Every time you wipe cache / dalvik and then flash a new version of the Kernel, it will use default settings? So, flashing the kernel replaces the scripts?

Also, will this current battery / performance zips will work with future versions of the kernel?
[Galaxy S II Original Android Development] Bushido76:
- Flashing the kernel just replaces the kernel. The kernel itself uses it's default settings.

- But after the excution of the kernel code, the scripts in the init.d folder will get executed one by one. These scripts can overwrite the kernel defaults. So if you really want to use the kernel defaults, freeze setcpu and clean your system/etc/init.d-folder.

Bushido
[Galaxy S II Original Android Development] RyanParty:
thanks, good info!
[Galaxy S II Original Android Development] KennyLegend:
I've answered this twice already since last night...

You need Supercurios "louder" app to make use of the new voodoo drivers. Its not released yet but Supercurio is hoping to release it shortly.
[Galaxy S II Original Android Development] TecQuality:
where? :p

10chars
[Galaxy S II Original Android Development] stevehkim:
did 3 tests siyah 2.6.1 defaults zips all 7050-7090. at 1.4ghz.

supercharged sgs2 i777 galnet rom/siyah kernel = beast
[Galaxy S II Original Android Development] stylez:
Just type it into the dialler and bada bing all fixed :p

_____________________________________________

On topic 2.6.1 is awesome battery.zip now with more UV and stable, don't play games just has to be smooth and boi it is.. With battery life never seen before! :)
[Galaxy S II Original Android Development] pikachu01:
Hey gokhanmoral,

Any way we can see the update of the sources for 2.6.1 in bitbucket anytime soon? ;)
[Galaxy S II Original Android Development] duff91:
hy guys, i've this rom --VK--™ Stable XWKK5 [v2.3] Final, with kernel 2.6.35.14-Siyhah-v2.4.2+gm@ubutu #52 but the phne doesn't read NTFS pen drive why?

Edit: i've flashed 2.6.1 but the phone doesn't read a NTFS usb pen
[Galaxy S II Original Android Development] xuxuzao:
how big should be the difference between default and baterry.zip settings on battery drain and performance?

tks
[Galaxy S II Original Android Development] smitna:
Hello Gokhan,

only one question: Your are now using the older toolchain Sourcery G++ Lite 2009q3-68 to build the kernel. Are there some advantages with this and not to use some CPU optimizations for armv7-a (e.g. march and mfpu)?

I have updated from 2.4.2 and the new version seems to be very stable and feels very fast even with default settings.
[Galaxy S II Original Android Development] Harsha Raj:
I don't know if this would work. But try enabling the USB debugging mode in settings> applications> development. And then connect the mtgs USB pen.
[Galaxy S II Original Android Development] duff91:
debugging mode usb is active, but anything change
[Galaxy S II Original Android Development] Hannibal226:
Hey buddies,

surely often asked, but anybody can tell me how yo disable battery.zip things?

reflashed kernel but I've also this bad brightness, which really sucks me!

Ty in advance ;)

Reflashed Rom but ty anyway...