yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Visentinel:
Theres 3 different wakelocks right?

The wakelocks with screen off and buttons off surely Couldnt drained much? I get home with 50% on average, but another thing importante using the full 18 steps frequency table. I setup 25mhz as lowest and phones still heaps smooth so if bln holds wakelocks at 25mhz and 875mv I think we could use breathing wakelocked bln 24/7 and maybe only loose like 20% over an 8 hour work day :-)
[Galaxy S II Original Android Development] umermajeed:
Anyone?
[Galaxy S II Original Android Development] Visentinel:
Its not like a car, technology is binary, a new kernel will be just be, the same tommoro as it was today, you can make judgements on it immidietly.
[Galaxy S II Original Android Development] desean:
Quick update on the download server from my host. Hopefully it will be restored soon.

For the benefit of those who doesn't read (i know it is ironic), alternative mirror is available as below and stop posting about download link is down. Everyone already knows that.
[Galaxy S II Original Android Development] daemien_:
Gokhan:

Regarding the recent touchscreen sensitivity changes, I noticed a dramatic reduction of movement precision in the 3.2b5 when compared to the 3.2b2 version.

I play the game "Draw Something" fairly regularly, so the changes were quite noticeable and drastic to me :).

To prove my point, I'm attaching two screenshots of the game - one running 3.2b2, the other running 3.2b5 -, that show the results of me trying to to draw the letter "e" a bunch of times on the canvas, as small as I could.

As you can see, in the 3.2b2 version, the drawings are really precise, and the line follows my thumb movement nicely. The result is that you can clearly see a lot of "e"s.

However, when running 3.2b5, the line doesn't follow my thumb quite well. Also, the drawing feels delayed, as if the input from the movement takes longer to be processed. The end result is that the letter "e" isn't even recognizable.

In both situations I did basically the same movement, but the results are really different.

Needless to say, I prefer much more the 3.2b2 sensitivity, which is very similar to what I had when running Gingerbread

. All ICS kernels I tried had horrible results,

except siyah 3.2b2

.

I tried fiddling with the sensitivity settings, but couldn't reach a similar result when running 3.2b5 at all.

So, in conclusion, is there any way to implement the 3.2b2 kind of sensitivity in the subsequent kernels (perhaps as an option in extweaks, if other people prefer 3.2b5)?
[Galaxy S II Original Android Development] Crescendo Xenomorph:
No offense: Move on to the latest release... :D

This is development thread, so we all talk about latest betas, not old release...

---------- Post added at 12:55 PM ---------- Previous post was at 12:53 PM ----------

+1 also with BLNWW

---------- Post added at 12:55 PM ---------- Previous post was at 12:55 PM ----------

+1 please do develop BLNWW with BreathingFX....

---------- Post added at 12:57 PM ---------- Previous post was at 12:55 PM ----------

So go on flash it... It got sooo many improvement.... C'mon be tempted... :D :cool:
[Galaxy S II Original Android Development] antoniosergius:
+ 1
[Galaxy S II Original Android Development] Crescendo Xenomorph:
But, is your phone usable? I mean, you can enter to Android without any error apart from that notice in the recovery?

if yes, then you can safely ignore that. It simply your CSC is unrecognized. Mine got the same error and gone after switching CSC (reflash CSC). That only mean the SEK directory is deleted, but it only contain customization from providers (a.k.a. bloatware). :D

---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------

This is a good idea, maybe this will help the draining issue. Because someone said that BreathingFX is accomplished by wakelocking the CPU to do the voltage changing... But since BLNWW can do blinking without wakelock, so.... Gokhan might know the answer... :cool:
[Galaxy S II Original Android Development] rlorange:
Yay! The first truly useful post in a while. This exactly what a development thread needs. Incidentally I've noticed this ICS "Elastic" thing we mostly all hate is prominent on Nova launcher and many stock Google apps but not scrolling on xda app... weird
[Galaxy S II Original Android Development] rlorange:
I like it too and certainly doable but only when BLNWW is fixed so that it doesn't increase standby battery drain all the time whether its used or not.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Yup yup... I would love too see that included in the kernel again... BLNWW(FX?) :cool:
[Galaxy S II Original Android Development] gokhanmoral:
v3.2b6 is up.

I have updated b5, b2-2 and 3.1.2 links. they are also available now.
[Galaxy S II Original Android Development] rlorange:
GM I'm seeing internal voltages for the GPU in nstools but not CPU frequency steps.
[Galaxy S II Original Android Development] sam razzy:
Will test it and I'll report you after 24 hours...

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] gokhanmoral:
they are bus freq steps, not GPU
[Galaxy S II Original Android Development] rlorange:
Oh I see. Its different that the sgs1. So I'm guessing the bus frequency scales with the CPU frequencies? Sorry I should probably know this. I saw a script for your GB kernel showing which frequencies used the three bus speeds
[Galaxy S II Original Android Development] rlorange:
So individual frequency internal voltage control is not possible?
[Galaxy S II Original Android Development] gokhanmoral:
no. cpu and bus frequencies scale independantly.

internal voltage is set for each bus freq step, not cpu.
[Galaxy S II Original Android Development] rlorange:
Oh ok. Is there a good information source you could point me to to understand this better?

1.6ghz is not stable even with +50mv on 400 MHz bus. Not a big issue but I thought it might be. Am I correct in thinking that 1.6ghz will always be running on 400mhz bus?
[Galaxy S II Original Android Development] luke05dee:
I am really sorry, but I am confused. What will changing the internal voltage do, will it ever allow us to get past 1.6ghz as suggested by a couple of people before, or increase performance at all, or anything else at all please? :)
[Galaxy S II Original Android Development] rlorange:
That was my hope based on my experience with the sgs1 but I don't think the two chips parallel closely enough to be comparable.

You can undervolt the lower bus frequency to save battery. Be sure NOT to have save on boot settings ticked on nstools until you find stable settings.
[Galaxy S II Original Android Development] gokhanmoral:
https://github.com/gokhanmoral/siyahkernel3/blob/update4-3.0.y/arch/arm/mach-exynos/busfreq.c
[Galaxy S II Original Android Development] gokhanmoral:
maybe there will be some power consumption advantage if you undervolt a bit.

I hope AndreiLux can make that advantage clear, if there is any.

if there is not a noticeable change in consumption I will remove those or make some changes to enable/disable bus freq steps. we can have 160MHz step in between and I may add a logic to disable steps if the voltage is set to 0.
[Galaxy S II Original Android Development] rauschkugl:
You're right the kernel will be the same but you still have to wait to judge battery on a kernel because the fuel gauge chip gets confused during flashing sometimes and needs time to recalibrate and settle.
[Galaxy S II Original Android Development] katestar:
I hope you don't mind me asking, but changing the internal voltages will it affect performance, as in lower it and you get lower speeds? Or could this result in any performance gains or make higher cpu frequencies more stable or need less voltage? Sorry if my english was not good :)
[Galaxy S II Original Android Development] AndreiLux:
I"ll do the measurements later in the afternoon/evening. I'm happy that I can finally clear my setup and free my desk after that :D
[Galaxy S II Original Android Development] rauschkugl:
Beta 6 feels really good according touch values. My phone feels more snappy overall as first impression. And i think you changed the bln breathing a bit. Looks more fluid now.
[Galaxy S II Original Android Development] coloxim:
Gm...is it possibile chooise if charge the phone at 97 and not 100% like nexus?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] gokhanmoral:
why do you need that?
[Galaxy S II Original Android Development] eric-filth:
GM

I installed nstools and cannot see internal voltages. Or i can only modify using scripts?
[Galaxy S II Original Android Development] alcurtis93:
GM will you still support s2 once the s3 is out?

Sent from my GT-I9100
[Galaxy S II Original Android Development] Appumon123:
fortunately, he would! :-)
[Galaxy S II Original Android Development] Rawi666:
Very good question and I'd like to ask a more detailed one:

What do you think of S3? Is it too big for you and you definately won't switch to S3 and you're going to stay with S2 for a year more?

Or maybe you have some thoughts to switch your phone because you're bored with S2 for example? :)
[Galaxy S II Original Android Development] rajarshi10:
Will I need to run kernel cleaning script before going from b4 to b6 ?
[Galaxy S II Original Android Development] AvRS:
Why ask about a phone that's not even out and there's no official specs on it lol

It gets announced at the Unpacked event in London at 19:00 UK time so just wait for that. Even if Gok decides to get the S3 we'll still have him around till that's released which may not be for a little while yet it's only getting announced today. And with all new devices he'll have to wait for the sources to be released which knowing Samsung won't be for ages for him to start real development so don't think you've got anything to worry about for a while yet.

I'm definitely getting one for my next phone but not till end of September when my contract expires.

---------- Post added at 09:04 AM ---------- Previous post was at 09:02 AM ----------

Kernel scripts aren't needed regardless of what kernel you go from and to. I've never used one in the 12 months or so I've owned the phone and never had an issue. It's the case of hype about nothing and I've even seen the dev of other kernels say not to bother it's just people will believe anything they're told, why do you think so many people buy Apple iPhone's :p
[Galaxy S II Original Android Development] ggogolewski:
I have this option at the bottom

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] superlik:
any posibility to enable bln for miss call using extweak instead of install another app (BLN pro) for that function? thanks
[Galaxy S II Original Android Development] MyLifeRocks10:
I don't think so. For me NSTools worked great.
[Galaxy S II Original Android Development] eric-filth:
hummm here dont have this option :-(

need remove voltage control?

Edit:

I have yes, but here is writing is gpu graphics not for internal voltages. Is correct?
[Galaxy S II Original Android Development] coloxim:
Because charge too much the battery is not good...I had got nexus s and the charge stopped at 97%...

Is a mistake?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] gokhanmoral:
yes.. fortunately cm9 supports it.

but in samsung roms, we need some other app (service) which polls content://call_log/calls such as this one: https://github.com/arifhn/NSTools/b...yann/nstools/services/MissedCallObserver.java

I don't know if it is possible to query that using a shell script but polling it in a script is not a good idea.

for sms, you can use another sms app and nstools already has that service to give you BLN for missed calls.
[Galaxy S II Original Android Development] bokil:
A little confusion in my mind:

I am using voltage control app for UC/UV and EXTweaks for BLN.

Now if i flash v3.2b6, then will i be able to UC/UV like i do in VC?

My understanding is that:

The UC/UV i do in VC is related to CPU (Different voltages for different freq of cpu)

and also GPU (frequency and voltage of GPU).

Now, v3.2b6 will similarly enable us to change frequency(?) and (internal)voltages of BUS?

This can be done through NStools.

So i can use Extweaks for BLN and NStools for cpu uc/uv and for internal voltage (feature of v3.2b6). So no need for VC.

Is that right? or i dint understand correctly?
[Galaxy S II Original Android Development] bleuxeon:
I don't have the voltage tab in ExTweaks:confused:
[Galaxy S II Original Android Development] alcurtis93:
Nobody does. Download nstools from the market

Sent from my GT-I9100
[Galaxy S II Original Android Development] fasst:
@gokhan

Any chance you will implement the remaining dual boot options soon?
[Galaxy S II Original Android Development] hawkerpaul:
I'm getting a little confused with VoltageControl, ExTweaks and NSTools.

Do we keep all three installed, or must we uninstall VC if NSTools is installed?

Do we enable BLN in ExTweaks AND NStools, or just in one of them?
[Galaxy S II Original Android Development] MyLifeRocks10:
Enable bln in extweaks and tick on NSTools service in settings for missed calls notification. If u enable in extweaks then in NSTools it will also be enabled.
[Galaxy S II Original Android Development] bokil:
I wanted to know the same thing (a few posts back)

I think (i may be wrong)

No need for VC if we use NStools and EXtweaks.

I wish everything was in one package :D
[Galaxy S II Original Android Development] Houselegend:
Hey, any idea how could i change my VolumeUP and VolumeDown buttons on my headphones to do next prev song ? My volume is 100% al the time so i dont have a use of it at all ... but changing songs would be nice.
[Galaxy S II Original Android Development] confusedmuse:
Anyone who thinks touch response is great in b6 and shouldn't be changed anymore should give a +1 to this post. :)
[Galaxy S II Original Android Development] lynx2k50:
Its not a kernel feature, its a rom feature.

Go and take a look at AOKP roms, or JKAY for Gingerbread or some other mods for ICS. You will finde them here:

http://xdaforums.com/forumdisplay.php?f=1059

For example:

http://xdaforums.com/showthread.php?t=1188201
[Galaxy S II Original Android Development] noobsgs2:
we want schedule BLN on siyah!!
[Galaxy S II Original Android Development] eric-filth:
We?

Not include me.
[Galaxy S II Original Android Development] AvRS:
Please don't there's already enough spam in the thread as it is.

What we do want is general discussion to be put elsewhere and leave this for development but that'll never happen! Just seems to be BLN or battery blah blah blah touch sensitivity wah wah wah

Thought I'd +1 to the useless posts.

Sent from my GT-I9100
[Galaxy S II Original Android Development] revaz:
Hi all!

I'm sorry to asking may be it was answered a lot of times but I didn't find - I got camera problem (hangs up) all the times I install version later then 2b1. could anyone direct me to solve that.

Tnx in advance.
[Galaxy S II Original Android Development] confusedmuse:
You think user feedback is irrelevant for development?

I can imagine it's hard for a developer to judge the outcome of any change by himself, especially if he had tried out endless variations, so i think he is glad if he gets a few comments about something he wasn't quite sure about.

You know, i have my opinion too but i'm not thinking it's the truth for anyone.

I rather think comments like yours about mine are spam.
[Galaxy S II Original Android Development] Houselegend:
When i get to CWM and do a Key Test the same key numberfor On Phone buttons for VolumeUP and VolumeDown and on my Headphones buttons. Thats why im thinking no app or ROM can make a difference between Headphones and phone buttons. That's why i posted it here, but maybe im wrong ...
[Galaxy S II Original Android Development] rlorange:
+1
[Galaxy S II Original Android Development] jim-bo:
Then use Tasker, or write an app to do it yourself.

Siyah is a kernel, and scheduling of something like that is a userspace application issue.

And before you ask, ExTweaks isn't appropriate for it, either, since it would need an ongoing service to monitor the state and time, and change it as appropriate.

ExTweaks doesn't have such a service, but all the information you need to control the state from scripts has already appeared in this thread (go and read the last many pages), and Tasker already supports running arbitrary user scripts based on any trigger you like, such as times of the day.
[Galaxy S II Original Android Development] xsillian:
+1
[Galaxy S II Original Android Development] rauschkugl:
Sod on beta 6. I don't know if something useful got logged. Happened two times while phone was sleeping. Will upload the kmsg when i get home.
[Galaxy S II Original Android Development] bokil:
Can someone please answer my query? Thanks :)
[Galaxy S II Original Android Development] sam razzy:
My hardware key button off is not working... light is on all the time... I tried with bln... but when my screen is on... my hardware button light is also on.. I tried to disable the screen backlight off by goin to Galaxy s ii settings to remove the tick.. but my try gave me no solution... is this kernel bug??? But I donn wanna c dis light when my screen is on.. I tried deactivatin bln but no help...

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] tolis626:
Well,touch sensitivity and the whole internal voltage thing on beta6 is great.I actually managed to get 1500MHz stable at 1275mV and 1600MHz stable at 1375mV(Didn't try lower yet),so it's working on the stability front,dunno and don't care about battery savings.

BUT,kernel panics.Lot's of 'em.Whenever I change internal voltages and,as it seems,clock steps,I get panic after panic after panic after panic.I measured 13 kernel panics in the last 30 minutes alone,so it's bad this time.

Gokhan,any help at all will be more than appreciated.I started thinking of throwing the damn thing out of the window... :mad:
[Galaxy S II Original Android Development] sam razzy:
Touch responsive is good... I mean better than all... :D

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] MyLifeRocks10:
Set led timeout so u ur light will be only on for that period
[Galaxy S II Original Android Development] bala_gamer:
Compared to siyah 3.1.2 the scrolling is poor. It was not noticeable in beta 4, but can clearly note the problem in scrolling with beta 5. You can scroll downwards normally, when you scroll upwards it doesn't moves freely at all.

Edit: seems b6 released, will try it soon

#*posted on the move *#
[Galaxy S II Original Android Development] omniwolf:
there's a workaround for getting BLN on SMS with the stock samsung sms app - i haven't tried it but it seems sound - you install SMS Popup, then configure it not to popup anything when you get an sms. it will activate BLN when you get an sms, and you can continue to use the samsung SMS app.

HTH
[Galaxy S II Original Android Development] Auridran:
This is correct. You do not need VC.
[Galaxy S II Original Android Development] sam razzy:
I did some play with this bln.. but no help..!! You sir saved me... Thank you ;)

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] wallaceff:
+1 on the up scroll
[Galaxy S II Original Android Development] wallaceff:
There's a free app "missed call reminder 2.1" that can bln on missed calls and txts.

Why not just use that?
[Galaxy S II Original Android Development] MyLifeRocks10:
No problem. But to set up bln u must enable backlight in device s2 settings and enable pulse notification light in display.
[Galaxy S II Original Android Development] sam razzy:
No my friend.. it use to work without enabling back light from the gsii settings... it was working on 3.2b5 version... will try on this and I'll report you in a minute...

Edit: its WORKING without enabling BACKLIGHT from the gsii setting

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] bala_gamer:
scrolling is back to awesome in b6, thanks gokhan.

why do we see/ notice poor scrolling when nothing related to touch response is changed in the kernel. im sure its not placebo.
[Galaxy S II Original Android Development] :
http://xdaforums.com/showpost.php?p=24851954&postcount=3941

has been working like a charm for almost three weeks:)
[Galaxy S II Original Android Development] akira888:
Seems my back lights are always on when the screen is on.

Before it used to be off after a few seconds...

Using AOKP ROM, resurrection 1.7....:confused:
[Galaxy S II Original Android Development] confusedmuse:
If something is mentioned the amount of placebo comments rises. :)

I too think it's awesome in b6 and shouldn't be changed anymore.
[Galaxy S II Original Android Development] Visentinel:
How do we change bus speeds in nstools? I have 3 frequencies in internal voltages, or how do I set them?
[Galaxy S II Original Android Development] MyLifeRocks10:
Set led timeout in extweaks app under bln tabs.
[Galaxy S II Original Android Development] MyLifeRocks10:
Did it worked when u receive notifications?
[Galaxy S II Original Android Development] sam razzy:
Okie.. again I'll get some notification msg and I'll check..wait.. will edit this post with the result... thank you

EDIT : Yes I tested with SMS + fb notification... yes its working perfectly...

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] rlorange:
Curious for more details. What internal voltages are you using. I was disappointed myself as I can see almost no effect at all. 1.6ghz is still unstable 1.5 might be a bit better.

Also I'm getting no kernel panics maybe your internal voltage settings are causing them?
[Galaxy S II Original Android Development] Visentinel:
Nevermind, the bus steps are 3 rigid frequencies that step up as frequencies step up.

One question, do the higher frequencies use 400 all the time or does the bus sometimes stay lower even if the cpu stepped up?
[Galaxy S II Original Android Development] :
Latest beta and extweaks now have bln test working, but for real notifications it still does not (stock aosp email and SMS). Any advice please?

I have lights off in sgs2 settings and led time out disabled as I want to use less only for notifications and otherwise always off.

Thank you!

Sent from my SGS2 - SlimICS Rom & Syiah Kernel
[Galaxy S II Original Android Development] rlorange:
I was wondering the same thing!
[Galaxy S II Original Android Development] AvRS:
User feedback can indeed be irrelevant unless useful information is provided. "It's better" doesn't class as useful feedback as probably the same number of people were happy with touch in b5 as those not happy and likewise in every beta/rc/stable since day 1 which means placebo and personal opinion can't really be used by developers. The only 1 useful post on touch sensitivity included physical evidence of repeated tests which showed a result. Even Gok said he has to take people's opinions with let's say a pinch of salt for better choice of words.

When you find a way to physically monitor, record and test each build you'll then be providing something useful to development but currently all +1's achieve nothing. I'm all for helping so please record your tests to backup your findings and development can progress. Also those kind of posts will make for better reading for people who come here to follow the development :rolleyes:

Sent from my GT-I9100
[Galaxy S II Original Android Development] confusedmuse:
Have you tried b6? Touch is just snappy and smooth. I like it and i think it should stay like this, therefore i'm posting it. It's as easy like this.

Btw. i'm sure GM knows what he has changed in touch thresholds. There is no information about this i could provide, but i can say that this values are working great.
[Galaxy S II Original Android Development] umermajeed:
Is there any scheduler in particular that works best with lulzactive governor? I am currently using lulz + VR on battery profile...was wondering if SIO will be any better
[Galaxy S II Original Android Development] rlorange:
GM I notice in nstools that there is now "max arm voltage" which is fixed at 1300mv but this can't be correct so we can just ignore it?