yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Raptor svs:
Ok guys, I thought some of you might find this helpful:

I made a table giving some frequency/voltage values that shows the effectiveness of uc/uv. See the image in the attatchment.

The values mean: 1=100% of power consumption at stock maximum freq, smaller values correspond to less consumption. I hope some of you find it useful.

f=frequency [MHz], u=voltage [mV], p= power consumption relative to 100% stock

Cheers!
[Galaxy S II Original Android Development] olifee:
Who knows what ICS will do to our phones ;).

<offtopic>

If you want to burn some RAM, do some multi-dimensional simulations using big lattices, if it still does not help, run a thread for each core. This easily fills up even my 16 GB including 4*256 MB zrams :P.

</offtopic>

The zcache-improvements are something I can even feel on my 16 GB-rig, suddenly complete videos + big apps can reside in the file-cache. This should also vastly increase Firefox and Opera starting on our phones, that's why I guess zcache will be the most likely change to 'feel' :).
[Galaxy S II Original Android Development] tolis626:
Well,I'll make sure to try it! :D

Although I doubt my PC can take it if yours can't will all that ram-zcache.But it won't hurt to try. ;)

Anyway,from my understanding too,zcache would be the way to go if we are to use such stuff.I will read more on it though... :)
[Galaxy S II Original Android Development] Fox05:
Hi,

I have a question.

Should I flash SiyahKernal.tar in DarkyRom2 app or should I unpack the SiyahKernel.tar and flash the zImage through DarkyRom2 app?

My phone is Galaxy S II with Android 2.3.4 XWKI4 and rooted with DoomLoRD's Easy Rooting.
[Galaxy S II Original Android Development] tolis626:
Both will be ok.I've been flashing tars through Darky for more than a month and I never had a problem. :)
[Galaxy S II Original Android Development] Fox05:
Thanks, but is the flashing safe? Can something bad happen when flashing the .tar through DarkyROM2 app? :)
[Galaxy S II Original Android Development] tolis626:
Guys,I have absolutely no idea if this is relevant,but thought I'd ask,as the most probable place for such things is the kernel. :)

Is it possible to change the output resolution when using mhl tvout?Because,as it seems,it mirrors the phone's display and what is displayed on the external screen is only an upscaled(And that not for sure) image from the phone's screen.I'd happily sacrifice some performance for being able to output in 720p or even 1080p.Or at least change the aspect ratio,as the TV is 16:9 whereas the phone's screen is 15:9 and the top and the bottom are a little "cut".

So,anyone has any ideas? :)
[Galaxy S II Original Android Development] incubus_fr:
Thank you for this.

Is this from experiment, calculation or external source?
[Galaxy S II Original Android Development] tolis626:
Well,the two worst things that could happen(I give you a 99.9% chance they won't happen) are:

1)The efs gets corrupt.But hey,you already have two backups made by the kernel.

2)Something goes bad with the flash and you end up with a phone not booting.In that case,just reflash a kernel with Odin/Heimdall.

Problem solved. ;)
[Galaxy S II Original Android Development] Fox05:
Should I enable USB Debugging before flashing? :)
[Galaxy S II Original Android Development] tolis626:
Well,I ALWAYS have USB debugging enabled,so I'd say yes... ;)
[Galaxy S II Original Android Development] Fox05:
Ok. Thanks for your help! :)
[Galaxy S II Original Android Development] :
"integrated new Mali-400 drivers released on 21 Nov 2011."

Whats the good use with this?
[Galaxy S II Original Android Development] KennyLegend:
WHY? is this an OCD thing or what? Cause its not a necessity for flashing this kernel dude.
[Galaxy S II Original Android Development] tolis626:
I didn't say it has anything to do with flashing the kernel.But try using adb without USB debugging and you'll see why I leave it enabled. ;)

It also doesn't do anything bad if you enable it without needing it. :)
[Galaxy S II Original Android Development] tolis626:
If you don't know what newer and,hopefully,better drivers can do fod you,don't ask.Just enjoy the ride. :cool:
[Galaxy S II Original Android Development] :
All I can think of is GPU acceleration but that aint gonna happen? I think :p

No, really. what can we benefit from it?
[Galaxy S II Original Android Development] :
hmm lets see: better battery management, better performance.. need more?
[Galaxy S II Original Android Development] :
anyways out od the country in 3.. 2.. 1.. see you in a few days, enjoy the siyah ride.
[Galaxy S II Original Android Development] :
Great! Why didnt I get that answer in the first place?
[Galaxy S II Original Android Development] vnvman:
Hmm well, actually i'm a bit unsure about what those drivers will actually do...the last time the proprietary gralloc drivers were swapped for the open source ones performances actually got worse in normal use conditions, both with this kernel and in the cm stock one. Nevertheless i'm looking forward for the update, who knows what they'll bring to the table? Fingers crossed ;)
[Galaxy S II Original Android Development] olifee:
Did you try to playback a 1080p movie? :P

In case the video can be decoded by the hardware-decoder of our Exynos, it is also output in Full 1080p. The limitations of the hardware-decoder (as far as I found out) are (for h264) High Profile L4, so sadly, L5.1 and Hi10p are not possible :(.

In case you want to see the difference, you can take a 1080p recording meeting the requirements and switch between Software and Hardware decoder. I found this to be very easy in MX Video Player (free), but YMMV. Of course, it also shows whether the HW-decoder was activated or whether it automatically fell back to SW decoding.

Apart from that, which makes me think this is by design: According to the things I read about the Exynos, it should even be able to provide three independent video outputs at the same time. Maybe they (Samsung) decided that rendering all Android apps twice for both resolutions is too expensive (CPU wise).

Personally, I would be happy if the internal screen is switched off (to prevent further OLED-burnin and conserve some power to charge faster) and the external screen is used with FullHD-resolution. I guess this might be some kind of problem, because Android itself might not see much of the MHL-stuff happening in the kernel. At least, it would need some deeper ROM changes to switch the rendering resolution.

In case there is a way the kernel communicates the display-resolution to the OS, maybe gokhanmoral finds it ;). Then, it might be easy to turn of the internal screen and completely switch to FullHD. Nevertheless, FullHD-decoding is a bit of a speed-problem unless hardware decoding is avaílable, even with our dual core (for 'nice' bitrates). And if it is available, you already have FullHD ;).

In case gokhanmoral takes a look into this:

Is the video-decoding part freely available in the driver and can be edited (i.e. is it somehow GPGPU-based), or is it somehow in the graphics-firmware / some proprietary blob?

In case there is a chance to add Hi10p-decoding / L5-profile somehow, this would be a first.timer (I do not know any consumer-device that can decode these without using a full software-decoder, sadly). And yes, that means my Core2Duo-laptop with nVidia-VDPAU / -PureVideo fails to fluently decode 1080p with Hi10p :(.
[Galaxy S II Original Android Development] AndreiLux:
AFAIK the video decoder isn't part of Mali and is something separate on the Exynos, and the drivers are proprietary / part of the ROM.
[Galaxy S II Original Android Development] jgrimberg1979:
Any thoughts?
[Galaxy S II Original Android Development] Ferdimage:
Just wondering if No service bug for MIUI builds is kernel related?

Im on 2.2b16 and i seem to get alot of No service....
[Galaxy S II Original Android Development] droidphile:
Thank you. Again you have proved that my point is right. What you said in this post http://xdaforums.com/showpost.php?p=19663428&postcount=11152 is theoretically correct, but practically impossible.

From your table, the lowest power consumption of 1200 mhz (in uv 150mv table) is 0.78 and highest power consumption for 1000 mhz (stock voltage) is 0.71.

I hope you can see .71<.78 and hence underclocking saves more power than undervolting, because too much uv is a fantasy in our phone.

Considering 2 frequencies f and f' such that f' is half f (200 mhz and 100 mhz may be). Let power consumption be P and P', with voltages v and v'

P ~ f * v* v

P’ ~ f’ * v' * v' ~ (f*v’*v')/2

V’ = root(2)*root(V)

Which is an impossibly low voltage.
[Galaxy S II Original Android Development] marbulas:
How about put the module '2nd core' of Tegrak?

It's very awesome thing to save life of battery :D
[Galaxy S II Original Android Development] cmd512:
Not too good at reading, are you?
[Galaxy S II Original Android Development] gekkonaut:
So I flashed v2.1.1 onto my phone and it worked great. I even rebooted a couple of times. Then, I went into ROM Manager and selected "rebooting to CWManager". then it froze on the yellow triangle screen. left it for a few minutes - wouldn't boot. Now everytime I try to reboot, I'm stuck on this. The only thing I can seem to get into is volumedown+home+power, which is is the bootloader for ODIN.

am I going to have to recover with ODIN now?
[Galaxy S II Original Android Development] minidou-77:
I think so...

Did you tried to boot into CWM (volume up+home+power) '

?

I stopped using ROM manager a long time ago because the same happened to me --'
[Galaxy S II Original Android Development] nerotix:
Was just listening to music and it suddenly random rebooted.. had it 2 or 3 times in 1 day..
[Galaxy S II Original Android Development] gokhanmoral:
rc3 is up.

I hope that this will be the last release candidate and I will work on linux kernel 3.1...
[Galaxy S II Original Android Development] bala_gamer:
Nice! Waiting for it to test.
[Galaxy S II Original Android Development] pixiebob:
gokhan: good to hear that you work on 3.1.

good luck for your work.i know it's not easy thing to upgrade branch kernel.

you are the best
[Galaxy S II Original Android Development] bala_gamer:
@ gokhan

I want to know what is causing the problems in integrating the new drivers once you solve it.

And also would love to know the advantages of new kernel branch you are going to use.

Edit:

Flashed rc3, its running good with the same smoothness, rc2 had less wakelocks, hope this will travel in the same path.
[Galaxy S II Original Android Development] gokhanmoral:
it was a 30-minues integration and it is possible that I could have made some mistakes.

I am very sick and spent the last night in bed without touching any kind of keyboard or screen :)

It won't be long until I solve that problem. after all it is the official driver and can be ported :)

oh, by the way, I have uploaded the sources to bitbucket. my username is gokhanmoral there and if I make any changes on v2.2 branch it will be uploaded there.

I am sorry that the repository is mercurial because I like it more :)
[Galaxy S II Original Android Development] harrynghiem:
I am trying rc3 and lag when hits draw of ADW launcher. Governors are used lulzactive and smartassv2.

go back to rc2, smoother than rc3.

anyway, thks your hard work
[Galaxy S II Original Android Development] droidphile:
Get well soon Gokhan. You need some rest and get away from us flash maniacs for a while :)
[Galaxy S II Original Android Development] vnvman:
Yep, apparently the mali drivers are causing this. It puzzles me how open source drivers actually perform better than proprietary ones :rolleyes:
[Galaxy S II Original Android Development] frankcilo:
With rc3 I not have folder conservative in sys/devices....

Why?

Edit: I use conservative governor
[Galaxy S II Original Android Development] gokhanmoral:
You should choose conservative governor first
[Galaxy S II Original Android Development] frankcilo:
Yes, I have choose conservative governor...but nothing, folder "conservative" not is present:confused:
[Galaxy S II Original Android Development] antt00:
No problem here. I see conservative folder when i choose it. Try reflashing the kernel again.
[Galaxy S II Original Android Development] aegeuss:
How about schedulers?

Gökhan, get well soon, I think a hot chicken soup with lemon and pepper on it would be perfect for this flue or cold :)

On another issue, I have decided to alter my settings, leave OC and more UV alone and use the standart values of the dev. So I set my cpu to 100 - 100 mhz and chose lulzactive instead of smartass2. I have a question though, we generally talk about cpu governors but seldom discuss I/O schedulers. So I wonder as non techician guy, is it because it's less important than governors or does it have less effect on the performance. I only remember past discussions on using sio scheduler for better hd video performance, that's all. I am also using it but would like to hear other thoughts on this as well. I can see the governor in Gokhan's signature but not the scheduler for example.

Regards.
[Galaxy S II Original Android Development] melorib:
RC3 seems ok... :rolleyes:

I installed SiyahKernel to try to improve touchscreen, wich is the only weakness of SGS2...

It improved, but after a while it started not responding, same as with standard kernel, after installing RC3, improved again, hope it is not only for a short period... :confused:
[Galaxy S II Original Android Development] b2rdetor:
iam sorry but what the real difference between rc1 & rc3???

ondemand tweaks unlikeble - it can make every single user youself, default stok ondemand - its a best governor! 500Mhz sleep - why? 200 - good for batery???

i can see any real differences between last realises.

i just seen a changelog and may bee iam wrong

---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------

touch move free app by tegrak - set it to 0 and you will happy
[Galaxy S II Original Android Development] kalpik:
RC3 is still laggy, even though up threshold is now 85. Did you change something in the ondemand governer?
[Galaxy S II Original Android Development] vnvman:
Imho it only has to do with the gpu drivers, which for some reason don't perform well in some apps like launchers.
[Galaxy S II Original Android Development] kalpik:
Did he not revert the drivers to the old ones in RC3?
[Galaxy S II Original Android Development] vnvman:
Nope, he just updated them to the latest release (21 november), but for some reason they still make everything laggy.
[Galaxy S II Original Android Development] kalpik:
From changelog:

"REVERTED the integrated Mali-400 drivers released on 21 Nov 2011. I had the same problem that I had in beta5. I need some more time to find out what is causing it. I’ll try to solve it in v3.0"
[Galaxy S II Original Android Development] Bartapuce:
Using RC3 Ondemand 100-1200 > seems ok and no lag

As everyone is concerned by battery life (including me) i investigated a little.

I found this thread on the "Battery Monitor Widget" site:

http://www.3c71.com/android/?q=node/109

And found that Hacre before quitting was investigating ths:

http://xdaforums.com/showpost.php?p=16303093&postcount=1358

If i understood well battery level is actualy only an estimate on the SGS2.

And the hardware may be able to report accurate reading from the battery with kernel/driver modifications.

@gokhanmoral

I would really like to have your point of view on this.

Thanks for all your hard work and get well soon.
[Galaxy S II Original Android Development] melorib:
Thanks, installed... :D
[Galaxy S II Original Android Development] age9990:
it is rc3 now but the internal sdcard mounting problem is still not fixed...

i hope in the final version it can be revolved.
[Galaxy S II Original Android Development] frankcilo:
I downloaded rc3 kernel again, I flash it again, but to no avail... I still do not see the folder "conservative".

If I flash rc2 again, "conservative"folder reappear!

Gok, please, help me!
[Galaxy S II Original Android Development] bala_gamer:
You are right, he didnt integrate the new drivers
[Galaxy S II Original Android Development] b2rdetor:
rc3 and i cant see any lags with ondemand.

some question:

we have 2 situations:

1. 200MHz/850mV and 500MHz/850mV and load 0%

whether in both cases, the same power?

2. 200MHz/850mV and 500MHz/850mV and we have load 100% for a 5 min for 200Mhz and 100% 2min for a 500Mhz = same work

whether in both cases, the same power?

i think than 1. yes???

2. no - 500MHz will more Energy Efficiency because less time too work (device not in sleep and other moduless and chips of s2 will drain the power and for 200MHz it will longer for 3 minutes)
[Galaxy S II Original Android Development] vnvman:
Sorry about that, the changelog was edited since the last time i read it.
[Galaxy S II Original Android Development] gcrutchr:
Am using RC3 and getting jerkiness while scrolling through my apps.

Same with RC2.

Am on XWKJ3 deodexed rom with ADW Launcher Ex.

RC1 works great - no jerkiness while scrolling apps

Edit: tried all the governors on RC2/3 - same problem
[Galaxy S II Original Android Development] woodyxxl:
ondemandx

Missing ondemandx... no insmod possible.... thats bad

(setcpu and screen off profile will lock phone....)
[Galaxy S II Original Android Development] Vaedryn:
RC 3 lags like Hell for me , have tried all governors , all have lag.

RC1 no lag with all Governors.
[Galaxy S II Original Android Development] Shluggity:
I can confirm this. Also seeing noticeable stuttering with ondemand and lagfree governors. Even performance isn't as smooth as RC2 was.

ADW Launcher EX on DlevROM 3.1 (KI4). RC3 @ stock clocks/volts.
[Galaxy S II Original Android Development] gokhanmoral:
Wait for the version that I will post here. I will post the release today. Rc3 has some testing code from new mali drivers.
[Galaxy S II Original Android Development] droidphile:
ondemand in this release has a sleep profile integrated to it. It's same as ondemandx, no difference apart from the spelling.

You need no screen off profile, since max screen off frequency is 500 mhz.

If you prefer 200 mhz

echo "200000" > /sys/devices/system/cpu/cpufreq/ondemand/suspend_freq

in your inti.d script instead of a screen off profile.
[Galaxy S II Original Android Development] jellyb:
siyah beta 6 is best kernel i ever tried, its packed with so many features and yet is awesome on battery life and smoothness at the same time :D
[Galaxy S II Original Android Development] gokhanmoral:
I am now at work and now working on the release.

some changes:

- ondemand is now screen-off profile. It was harder to manage both ondemand and ondemandx and the only difference was the screen-off profile. it will perform better in v2.2 release but if you want to make it scale up faster, lower the up_threshold. there is a fact: if you use high frequencies your battery will not last long. so, I think 85 is a good compromise between battery life and responsiveness.

- another fact is that you CANNOT tweak deep sleep consumption. so, please do not post "deep sleep power consumption is high/low/whatever" type of messages. that means if you let your device sleep it will consume more or less the same amount of energy no matter which kernel or rom you use. if there are some reasons that cause your device to wakeup those needs to be solved. in other words, if you have 5% power consumption during night with another kernel, you won't have 6% with this one if the starting point is the same.

- lulzactive may be slow during waking up from sleep. I want to have ondemand behaviour close to default. I want to have lulzactive & smartassv2 for powersaving modes and lagfree for snappiness & games. lagfree uses min 500MHz when the screen is on and 200-500 when the screen is off and based on conservative, but it will have bad screen-on battery performance.

- the kernel uses XZ compression but it is still big because we have ntfs-3g and some other binaries (su, Superuser.apk etc) in initramfs but those will in no way make the kernel slow. it may only effect the boot performance but it is 1second at most.

- I will release two versions for v2.2: one with logging and printk disabled and another one will have those enabled. you decide if those features cause any lags.
[Galaxy S II Original Android Development] android_888:
How is smartassV2 on Syiah 2.2? I am currently on 2.1.1. and smartassV2 is the best option I think..

How is on 2.2?

P.S. Please don't tell me you must find it yourself, I like to hear peoples' experiences..

Cheers
[Galaxy S II Original Android Development] iamsmallpang:
v2.2 beta rc3 battery drain very fast

waiting .......v2.2
[Galaxy S II Original Android Development] gokhanmoral:
wait for the release and then ask :)
[Galaxy S II Original Android Development] BULL3TPR00F:
Just installed 2.2 RC3 and my battery just began to drain like crazy. And also I'm experiencing extremely heavy lag when scrolling the app drawer. Never had these issues on the other betas or rcs.
[Galaxy S II Original Android Development] alcurtis93:
Is there something wrong with these new Mali drivers or is it something to do with you patching them in @Gokhanmoral?
[Galaxy S II Original Android Development] gokhanmoral:
as I said, please wait for v2.2 release

I will post it here. I have removed download links for rc3
[Galaxy S II Original Android Development] BULL3TPR00F:
Cool, you are a machine my friend. I always wondered how you could put out like 3 updates a day lol.

This is the best kernel out there imo
[Galaxy S II Original Android Development] woodyxxl:
Thx a lot. This is what I need! So ondemand is the "new" ondemandx :-)
[Galaxy S II Original Android Development] skiflyer:
all people who former had the ondemandx governor should check their settings in voltage control / setcpu. because after flashing RC3 the governor is changed to another one, in my case lulzactive. that could be the cause for your lags.
[Galaxy S II Original Android Development] therion21:
change default?

is it possible to change the default gov without the use of setCPU? I would love to have smartassv2 as the default one
[Galaxy S II Original Android Development] gokhanmoral:
good point. maybe the app you are using to change governors keep the index of the selected governor. now we have +1 and -1 governors (lagfree added ondemandx removed).

check your governors after flashing v2.2 (will be up in half an hour, you'll find it in the first post)
[Galaxy S II Original Android Development] xan:
I keep the name of the governor, it might FC when its missing ;p
[Galaxy S II Original Android Development] skiflyer:
yes, via xan's voltage control.

in my profiles of setcpu were "ondemandx" set, but when opened to manually change values, "lulzactive' was in use. so it might be a bit confusing, but that shouldn't be your worry gokhan.

i think the users are able to check and change their governors in the profiles of setcpu, if there are any.

concluding: people check your governor after flashing RC3 and siyah v2.2 final. especially in the profiles of setcpu, if there's the one used you want!
[Galaxy S II Original Android Development] bala_gamer:
I dunno , what to say, my s2 is perfectly smooth with canditate 3, many of you people are having problems.
[Galaxy S II Original Android Development] sasho36:
I still have some reboots, e.g.: while mounting a ntfs drive (not always). My settings are: smartassV2, 200-1200, no UV...

Thanks for your support!
[Galaxy S II Original Android Development] gokhanmoral:
do you still have them, reboots and freezes?

unfortunately I have disabled almost all logging in the kernel.

maybe I will make another version with logging and debug infos...
[Galaxy S II Original Android Development] gokhanmoral:
any reboots except for the ones during mounting ntfs drives? and do you get the reboots only with smartassV2?
[Galaxy S II Original Android Development] netchip:
Lol, You think ?

My code is very easy and neat.

Im not jealous because my code is nice write and has features what people like.

Sent from my GT-I9100