yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] duykhang524:
Wow touch is now so good compared to b5 I wasn't even able to unlock my screen with b5 cause swipes would register as taps and the lock would follow my finger...
[Galaxy S II Original Android Development] :
Mine is at 1450, you sure you havent played around them:)?

Just about from a full wipe rom kernel install, all defaults
[Galaxy S II Original Android Development] bala_gamer:
i would like the same.
[Galaxy S II Original Android Development] akira888:
To make the best use of BLN, should I use the combination of:

1. extweaks + nstool

2. extweaks + BLN control

3. extweaks + nstool + BLN control

:confused:
[Galaxy S II Original Android Development] tolis626:
Well,my phone was never stable at 1.6Ghz below 1.4mV.And even so,it was relatively stable.For 100% stability I had to go at 1425mV or 1450mV,but it probably never was 100% stable that high.1375mV always made the phone freeze instantly.The moment I pressed apply was the last moment my phone would spend at 1.6GHz with 1375mV.Even lower was completely out of the question.Same goes for 1.5GHz.My phone needed 1375mV for anything in the 1496MHz<f<1554MHz range(I studied this behavior thoroughly) and from that point on,everything was as uncertain as space time near a black hole's even horizon.This time,1.6GHz was stable at 1375MHz and 1500MHz was stable at 1275MHz for long periods compared to previous tests.Longest one was about 10 minutes,in which I ran a stability test without crash.Short after a kernel panic occurred again though.

I can provide a log and last_kmsg from these panics if needed,but I already posted one some pages ago and I didn't get an answer.Gokhan might have missed it or ignored it,I don't know.If needed,I'll provide another one.It's easily reproducible here anyway. :)

I think that bus scaling is dynamic,which means that bus frequencies scale depending on load.However,using lower than 400MHz for frequencies>=1200MHz would probably choke the CPU,causing a bottleneck,so high frequencies probably do use 400MHz all the time.I could be wrong as I didn't check the accompanying source code,but if my memory serves me well,it was this way in Gingerbread. :)
[Galaxy S II Original Android Development] bokil:
I use only extweaks. I dont need scheduling.
[Galaxy S II Original Android Development] MyLifeRocks10:
NSTools works with missed call so I use extweaks and NSTools.
[Galaxy S II Original Android Development] AvRS:
I've not tried it yet because I prefer the old backlight standard of only activating on touch of the buttons not the sammy way in b4. That and I only update when I feel there's a feature I'll make use of and as I never change voltage, clock speed etc I've not actually been using Siyah at all until BLN breathing was introduced and now I'm hooked on it so I'll stay on b4 until something else that's useful for me changes. Alternatively I'll use the stock kernel in the ROM I'm on if breathing ever makes it's way over to it. Stock settings have always done me well so I stick with what's working for me :D I do enjoy following real development, hence why I follow Siyah and also CM9 which I also don't use or plan to they're just of interest to me.
[Galaxy S II Original Android Development] alexis_p3300:
B6's touch is much improveved from b4,but 3.1.2 is top when running cm9
[Galaxy S II Original Android Development] bleuxeon:
I don't anderstand what NSTools offers as new tweaks.

All I can see in it (I dont talk about BLN stuff since I dont use that) can allready be set in VC and ExTweaks.
[Galaxy S II Original Android Development] rlorange:
In nstools does anybody else see max allowed voltage fixed at 1300mv? Ie if you change it it reverts back? I know it can be accurate otherwise 1.5ghz is running stable at 1300mv!
[Galaxy S II Original Android Development] tolis626:
1300mV is,by default,the max voltage you can throw at the bus,the internal voltage in other words.The voltage for the CPU is the other option,the max ARM voltage or whatever it calls it.
[Galaxy S II Original Android Development] bleuxeon:
but what is different from using Voltage Control?

I don't anderstand:confused:
[Galaxy S II Original Android Development] rlorange:
No no the Arm max also says 1300mv
[Galaxy S II Original Android Development] confusedmuse:
For me b6 works best on CM9 when setting the screen sensitivity in CM9 to 30 and the touchmove sensitivity in extweaks to 3 pixels.

Any click is recognized as a click and any stroke as a stroke.

Had no single misinterpretation of any move so far.

The scrolling distance is proportional to my stroke speed & length and there is no trace left of that annoying "elastic back jumping" behavior.

The operability of the phone was never better for me.
[Galaxy S II Original Android Development] rlorange:
Internal voltage control
[Galaxy S II Original Android Development] omniwolf:
there's nothing much. people are just too cheap to pay for BLN Control Pro, nsTools gives you BLN with missed calls for free.

Voltage Control is more complete than nsTools IMO.
[Galaxy S II Original Android Development] wallaceff:
If i want the best battery life, can someone suggest any internal voltage settings that would be worth trying? Or is all the undervolting stuff not really likely to give a big difference to battery life at the end of the day?

Also, I've read in places that 200mhz is more efficent than underclocking to say 25mhz? Can someone explain this or point me to an accurate source of information on this? Seems counterintuitive that my phone should sleep at 200mhz rather than 25mhz?
[Galaxy S II Original Android Development] rlorange:
Hmmmm only nstools will interface with the new Internal voltage control in b6
[Galaxy S II Original Android Development] gokhanmoral:
if you set it it becomes 1300. it is my mistake.

I will fix it in the next version.
[Galaxy S II Original Android Development] rlorange:
Ok. So is the actual voltage capped at 1300 or is just reporting it that way?
[Galaxy S II Original Android Development] Vaedryn:
Battery with b6 is very good for me. Great job.

Cyanogen (mod) 9
[Galaxy S II Original Android Development] wallaceff:
Oh, and if I can change topic, I for one really like the SecondRom option.

GK, is there any chance of a simple widget to chose which rom to launch at start up (so I don't have to tap away at the home button? I've missed the countdown quite a few times). The widget restart option would also have to be able to be over-ridden at start up in case something went badly wrong with the second rom (or some setting in CWM to force which rom to boot into in the event of a stuff up).

This could be expanded if you chose to enable more than 2 roms (which I personaly would like to see, so I can test out different roms easily - yes, I know, I could rename the secondrom directory, but I'm asking for a more elegant solution).
[Galaxy S II Original Android Development] rauschkugl:
It doesn't sleep at that value it is the lowest value for the phone being awake and a lower value would mean more time is needed for a task so it would take longer for the phone to get asleep again. I can't remember the thread or post where it was measured exactly though. Undervolting doesn't save you much battery at all. Maybe 10 minutes more.
[Galaxy S II Original Android Development] wallaceff:
Ok, then what about battery consuption of 1 core vs 2 cores? Does anyone know what Mhz its more efficient to have 2 cores running at rather than 1?

what about everyone trying to get 1.6Ghz speed out of their phone? Surely that would burn through battery life? Does anyone here need that speed?

Is it more battery efficient to cap my max speed at say 800mhz? Or better to be able to get to 1.6Ghz to (lets simply things for just a minute) run the process twice as quickly? I dont think there's merit to argue that screen would be on for half as long as most processes finish in under 1 second generally anyway.

Is there a science to work this out? Or just more "try it and see how your battery life goes?"

I'd love someone to spell out some detailed battery life consuption parameters based on what I've listed above.
[Galaxy S II Original Android Development] d3l1:
Can the kernel prevent me from being able to accept a phone call? I could normally accept calls this morning with 3.2b4 and 2 hours ago I flashed 3.2b6. Half an hour ago I recieved a call and I couldn't answer it. Neither via the touchscreen nor via the home button, the phone was completely unresponsive so I had to call back after the caller hung up. I will test this further later when my gf is home but it was strange and the only thing that changed since this morning was the kernel.

Not blame anything, just curious!!!
[Galaxy S II Original Android Development] tolis626:
It is and it is not science.It's no science to understand that 1.6GHz will be quicker in both executing tasks and depleting the battery.But it kinda is a science trying to figure out how a phone behaves at different frequencies etc.Best solution is to leave these things stock if you don't know enough.
[Galaxy S II Original Android Development] JAG131990:
Its never going to be more efficient to run your phone at 1.6Ghz in the hope it will do jobs faster to save battery.. fact is you provide human input and provide plenty of wasteful time perusing and taking information before responding. You end up with wasted clock cycles at high speed and voltage
[Galaxy S II Original Android Development] wallaceff:
I guess what ideally I want is a govenor that sets the upper limit to say 800mhz, then only when really pushed, or somehow noticing the system to be somewhat unresponsive, increases in steps, but should almost never hit a predetermined maximum, except in extreme circumstances.

I've tried playing around with this to some extent.

Using lulzacive, set min to 200, max to 1000.

pump up 1 step

pump down 2 step

screen off min 4 (not sure what this does, can someone elaborate?)

up sample time to 100,000 and down samale to 20,000

When looking at cpu spy, it would appear that it tries not to jump up too quickly.

Does this seem about right?
[Galaxy S II Original Android Development] sam razzy:
I'm having battery drain.. but no a big... its not a issue... I just love this all build... great contribution... ;) just wanna know what is multipdp and what is secril_fd-interface????

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] jim-bo:
It is all about choosing the correct frequency for the task at hand.

For example, if you are computing the checksum of a large file, then there is no user input and 1.6GHz could be ideally suited to doing it with the minimum power expenditure.

After all, people argue that 25MHz (or even 100MHz) is bad for battery since the phone has to stay awake longer than if it was at 200MHz, but if you are, for example, processing data for a sync that is downloading at a very low bitrate due to poor connectivity, then I'd rather my CPU was idling at 12% load at 25MHz than 1.5% load at 200MHz, or even at 80% load at 25MHz than 10% load at 200.

In an ideal world, that would be what the governor was for, and in fact that is why there are so many different govenors available, and so many different opinions as to which is the best.

Stepping up your CPU to the point where it can completely cope with the workload and always just about be waiting on something else, should minimize the time that the phone is awake, thus minimizing the CPU battery use.

Of course, doing that in practice is where this all becomes an art rather than a science, and where so much of it depends on what you do with your phone.

If all you ever do is make calls and keep your google calendar up to date, you're not looking at anything like the same usage profile as someone who runs 3D games, processes mathematical models, watches movies, reads ebooks, etc. etc. All different usage patterns, all different optimum CPU frequency patterns.

The only way to really know what's best for you is to try them all out and see how you get on.
[Galaxy S II Original Android Development] wallaceff:
Was worried you were going to say that! :D

Any suggestions on where I can find some information on what settings people are using for examples you listed?

eg. make a few calls, browse web a bit, check email, whatsapp etc vs the power hungry user
[Galaxy S II Original Android Development] tolis626:
Well,a good starting point would be ondemand,as it's pretty standard and its configuration is pretty straightforward.Take default ondemand and using a script or your favorite app(SetCPU,SysTune or nsTools to name a few) and set powersave bias to,say,200(max is 1000 but you don't want it that high).Also wait for Gokhan to bring smooth scaling parameters back,that'll give you more of what you want.Set your maximum clock to no less than 1000MHz if you want my opinion.You'll be saving quite a bit of battery from CPU-related stuff this way. :)

On second thought,you can also mess with frequency step and set it to something like 40 and see how it goes...
[Galaxy S II Original Android Development] wallaceff:
Thanks, I'll give this a go. I'm using NSTools.

I never really understood the smooth scaling parameters and what they meant, could you clarify?
[Galaxy S II Original Android Development] pangiotis24:
sorry if this has already been asked but why we can't set the maximum screen of frequency for ondemand from extweaks.I remember that in previous releases we had that ability
[Galaxy S II Original Android Development] lyndonguti:
noob question guys...can i save the dualboot second rom into my external?
[Galaxy S II Original Android Development] tolis626:
Simply put,these just "force" ondemand to use the between frequencies more instead of just jumping from minimum to maximum frequency and backwards all the time.
[Galaxy S II Original Android Development] rlorange:
Use ns tools set lulzactive 66% up threshold and down sample time to 60000 the rest leave as is. I get an even use of frequencies and amazing battery life. Try it!
[Galaxy S II Original Android Development] tolis626:
Me?I don't give a crap about squeezing a little more life of my battery,so you're referring to the wrong person. :p

Unless you directed this to the other guy.Then ok. :)
[Galaxy S II Original Android Development] rauschkugl:
You shouldn't think about cpu stuff too much. Set a low display backlight and watch for wakelocks of apps. These are much higher battery drainers. If you just use ondemand or lulzactive and play a bit with extweaks settings for cpu and use 1000 as max frequency you should be fine.
[Galaxy S II Original Android Development] wallaceff:
Yes, I'm that 'other guy!' Over here... hello... this way! :P

Do you think that wakelocks are more likely to be app created or rom dependant? ie. is it worth trying to switch to different roms to minimise wakelocks? Or they're all essentially the same other than some extras here and there.
[Galaxy S II Original Android Development] rlorange:
Oh yeah the other guy. Lol! Lulz is rad tho for battery and performance :)
[Galaxy S II Original Android Development] KennyLegend:
Anyone using smartass v2 with this? I'm getting pretty crap battery life since b4, but I like the bln feature. I was using rc6 before that with good results.

I switched to smartass v2 last week since Lulz just wasn't responsive enough for me and jittered a bit. Its super fast and smooth but wondering is it playing havoc with my battery or is it the bln feature.

I've got a pretty good CPU spy pic.

Has anyone compared battery life with bln on V no led or stock notification settings?

Anyone got any input on this?
[Galaxy S II Original Android Development] rlorange:
Rouge wake locks are the worry and can be fixed usually by clearing app data and/or fixing permissions. Make sure you set auto sync and notification or app updates at a reasonable rate. If you don't need Gmail waking your phone up every half hour through the night to check email then change it.

Kernel wake locks are different and harder to trace and fix. But siyah is fine.
[Galaxy S II Original Android Development] tolis626:
Gokhan,if you can please take a look at my last_kmsg and tell me what's happening before I throw the goddamn phone down the sewers,I'd deeply appreciate it.I get kernel panics out of the blue,with absolutely no consistency.They only occur consistently when messing with NStools.On a friend's GS2 this doesn't happen,but I don't know what bootloader he is using(neither does he in fact).

I really am sorry for insisting,but I can't think of anything else that might be related.If you can't suggest anything,maybe I'll try old Gingerbread bootloaders or returning to stock rom and see how that goes...But I'll avoid these if I can.

Anyway,thank you in advance man. :)
[Galaxy S II Original Android Development] Happy_Jack:
My battery life seems OK (currently using SmartassV2 and sio with BLN enabled through Siyah). 1 day 16 hours on battery so far and only down to 29% with just a couple of hours charging while the phone was in my car cradle. It's not a scientific measurement but I'm happy with it. BLN doesn't seem to make a huge difference if you set a reasonable timeout. Obviously if your backlights are flashing all night long that's going to flatten the battery...
[Galaxy S II Original Android Development] redrumsilence:
BLN not working at all?
[Galaxy S II Original Android Development] Happy_Jack:
Works perfectly for me.
[Galaxy S II Original Android Development] fantom2007:
On my AOSP base rom + beta6

i set led time out to 1.5 sec, it work

but every time touch the screen led is on too, Is normal?
[Galaxy S II Original Android Development] hawkerpaul:
I've pm'd you Gokhan but just to let you know on here, I'm still getting SODs on b6. I enclosed last_kmsg. Phone totally dead and red hot.

Its still only ever seems to be happening when on 3g outside of my wifi range.
[Galaxy S II Original Android Development] lesp4ul:
Yes it is in b5 changelog, but i hope gokhan would add an option to it (screen touch, capacitive, or both)

Sent from mySwagga SGS2™ using ToiletPaper®
[Galaxy S II Original Android Development] sam razzy:
BLN is working perfectly ... ;)

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] redrumsilence:
It's not working with Hookt, G+, instagram, XDA, or Twitter

Seemingly its only working with Facebook :(
[Galaxy S II Original Android Development] gokhanmoral:
it is not related with kernel.

you have to report that problem to those application's authors.

if bln works in a single application, even in test mode, then there is no problem with the kernel.
[Galaxy S II Original Android Development] MistahBungle:
Guys, show a bit of respect toward Gokhan by reading the thread before asking basic questions. These questions have been answered already, even in the case of a build that was released a few hrs ago. This is a development thread after all.

The constant 'how do I get my recovery back' without reading the first page of the thread, the changelog on Gokhan's site & indeed the last 10 pages of this thread is starting to get really old :-|
[Galaxy S II Original Android Development] superleeds27:
Installed beta5. NO CWM ...it doesn load , and start normally

Just kidding! Working fine matey. :)
[Galaxy S II Original Android Development] andrewin:
Don't empty your clipboard; you will for sure need it again one or two pages later :-)
[Galaxy S II Original Android Development] johnny8910:
Working great for me at -50mv 200-1400
[Galaxy S II Original Android Development] bragon2010:
The colors are OK in new beta5!
[Galaxy S II Original Android Development] Flasher8:
Guys, anyone already try for cm9?
[Galaxy S II Original Android Development] bandit79:
Siyah v3.0beta5 installed on Hydrogenics and now the Softkeys won't work :/ ... so BLN does'nt work here
[Galaxy S II Original Android Development] gabx:
You are wrong mate. On Tuesday 20 late afternoon, some users found a link from codeworkx website server with a new 0320 nightly. This ROM has been downloaded a few times when indeed it was not intended to go public.

A few hours later, the CM build from buildbot came out, but in fact with some differences :broken MTP and not the new CM bootanimation.

---------- Post added at 02:22 PM ---------- Previous post was at 02:13 PM ----------

Not really a Syiah issue!!

What dpi you guys are you using? Had this problem with CM and a lower dpi than the stock 240.

---------- Post added at 02:27 PM ---------- Previous post was at 02:22 PM ----------

Fine, but what about plegin for any hardware stuff, like a debug board for example? It is always more easy for donators AND you to buy or accept a useful tool instead of money.

I was thinking too to the board from the website we have been talking earlier in PM.

What do you think of such idea?

---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------

Cyberpunk, maybe try to post your issue in the thread below my signature. It is dedicated to CM9/SyiahKernel specific issues.

Who knows?

---------- Post added at 02:43 PM ---------- Previous post was at 02:30 PM ----------

YES. Go and visit the thread link below my signature
[Galaxy S II Original Android Development] tolis626:
Now I'm really surprised.Kudos to you man.Selflessness is something I always admire. :)

So,Siyah has been ok for me till now on ICS(I too had the bugs people mentioned about,yes,blah blah...),just missing responsiveness.It exhibits some jerky movement,no matter what my settings are in exTweaks etc.It's not slow,but CyanogenMod stock kernel runs smoother.I suppose you already know that,so I won't analyze it further.Once that is ironed out and CM9 fixes video recording,I'll kiss Sammy roms a big goodbye,hoping I'll never to use these again. :)
[Galaxy S II Original Android Development] gokhanmoral:
It will be better in beta6 (I hope :) )

and I am already backing up my data. I'll move to cm9 tonight.
[Galaxy S II Original Android Development] zekurosu:
good for us CM9 lovers then :D
[Galaxy S II Original Android Development] bleuxeon:
yep : great news!:D
[Galaxy S II Original Android Development] Karpfenhai:
Just my 2 cents, im on Beta 4, all Voltages -100 DPI set to 216, no issues at all..
[Galaxy S II Original Android Development] sansunggalaxys2:
Works on Slim ICS(finally:))
[Galaxy S II Original Android Development] almaalma74:
"no slogan yet" - it's a perfect slogen :)

or simply "without any slogan" would be the new slogen, a little paradox
[Galaxy S II Original Android Development] gabx:
Do you set your dpi with an app or with any .prop file?
[Galaxy S II Original Android Development] daveuk87:
Having some issues with CPU frequency jumping around erratically. Anyone else experienced this? For example, I set 200-1400Mhz in SetCPU and run stability test, the cpu frequency jumps between 800-1400Mhz every 1 or 2 seconds. Everything is working fine otherwise and it isn't causing the phone to freeze so it's no huge issue right now.
[Galaxy S II Original Android Development] luexi:
woohoo! pls try to make MTP work in b6!.

Thanks!:D:D
[Galaxy S II Original Android Development] chungtau:
BLN dose not work with wanamLite!
[Galaxy S II Original Android Development] RodzynR:
What is the best governor for this kernel ?.. Actually i use SmartAssV2

Wysłane z mojego GT-I9100 za pomocą Tapatalk
[Galaxy S II Original Android Development] coloxim:
For me the touch were better before...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] PedroMRP:
OMG... stop nagging about touch... it's impossible to please everybody :\
[Galaxy S II Original Android Development] coloxim:
No battery life

No bln

No touch.

What do you want talking about?

I've again the problem with conservative governor...stay too much at 500...

Don't know why

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] steve17360:
And me. This thread's full of whiners.
[Galaxy S II Original Android Development] rauschkugl:
same for me, here are two kmsg from today. hope they help to fix the sod issue.
[Galaxy S II Original Android Development] sam razzy:
I will make a good report about what is working with bln what is not working ... wait... ;)

TapaTalk Gnex Galaxy Sii