yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] eybee1970:
find attached:
[Galaxy S II Original Android Development] bandit79:
So i'm finished. Thanks to eybee, it works now and i can switch between andrev_oc and virtuous_oc. Also both folders located in /system/etc

Now i have a 80aroc and 83oc script in /system/etc/init.d

Are both nessecary?
[Galaxy S II Original Android Development] Pfeffernuss:
I already got the file but thanks for the effort anyway! Very kind... :D
[Galaxy S II Original Android Development] tonysac:
What is the difference between andrev and virtous oc?

Is it let's say different profiles for daemon app?

Save water..drink beer!!!
[Galaxy S II Original Android Development] tvhak:
great work. thanks

tjeerdos
[Galaxy S II Original Android Development] eybee1970:
keep 83oc and delete the other one
[Galaxy S II Original Android Development] estebitanpn:
init d

I have not found init d, if i go to system/etc/i dont find it. Other question: HOw can i change the sheduler in set cpu? Do i need another app?. Thanks

Edit: I´m on stock KI3 with Siyah 1.8
[Galaxy S II Original Android Development] ebliss:
gokhanmoral, before you release beta7, can you remember to update cwm to 5.0.2.6?
[Galaxy S II Original Android Development] peachpuff:
I kinda wish the vibrations would be broken again, i got a nasty vibration alert in the middle of the night letting me know the battery was charged. Is this a kernel or rom feature when the phone is turned off?

Sent from my GT-I9100
[Galaxy S II Original Android Development] hedayat7:
setcpu cant change scheduler .. but you can use no-frill cpu .. download it from market .. you can change governor, cpu speed and scheduler
[Galaxy S II Original Android Development] dethx:
i left my phone untouched for about 2-3 hours and it "died" for unknown reason...

it didn't power on so i had to take the battery out and in again, and then it worked.

battery was on 68% so it ain't a battery issue i guess...

i'm using beta6, on romkitchen ki3.
[Galaxy S II Original Android Development] hedayat7:
i suspect it maybe due to suspend lock .. do you undervolt ? raise the voltage a bit, or maybe you should use stable version 1.8 ..
[Galaxy S II Original Android Development] gokhanmoral:
sorry, generally I don't like to sound rude but this is just an excellent example of giving lack of information.
[Galaxy S II Original Android Development] Denwa:
Nope. Been using just OC Daemon for ages. Works fine with prior siyah versions.

OK, Thanks for that. I will try than upon the morn. Er.. if you haven't released 2 more betas (and fixed the issue) by then. :D

I almost threw up in my mouth there for a second, but then I thought.. apple probably "borrowed" the code from some linux guru in the first place! ;)

Uhm.. does that make my phone a crabapple-droid?
[Galaxy S II Original Android Development] Lennyuk:
Sounds like you clocked too low what were your CPU settings, and which governor?
[Galaxy S II Original Android Development] dethx:
my screen off profile is set to 100-200 mhz, conservative governor.
[Galaxy S II Original Android Development] Lennyuk:
then that is why it failed to wake
[Galaxy S II Original Android Development] chadouming:
Most of the code does not work on CM7, including this one.
[Galaxy S II Original Android Development] roymustafa:
Hi man, i have done everything as you said...The problem still remains...That is frastrating...:confused:

Edit: Huraaaaaaayyyyy...The problem solved after wiping dalvik cashe and flashing again....
[Galaxy S II Original Android Development] Denwa:
My screen off us 100-100 and I have no wake problem.. least with 2b4. Haven't got clocking working yet with b6 as per above.

Night all...ZZZzzzzzzzzzz

--sent from a faster than light sub-atomic particle via subspace communications tapped in binary by a finicky evil dragon with a broken wing hurtling through space while playing chess and sipping tea all while sitting in a rattan chair wondering why those dreams about being a bipedal huminoid seem so real...
[Galaxy S II Original Android Development] d3l1:
why should it? I use those screen off settings on two devices myself so do many others and the phone never gets the "sleep of death". Either it's due to the beta stage or something else freezing your phone / preventing it from waking up from deep sleep. No idea how to check what caused it, sorry :(
[Galaxy S II Original Android Development] Lennyuk:
1) not every phone is the same, some handle different clock levels better than others

2) in b6 it now switches to a single core on screen off so that 100mhz becomes 100mhz single core, i.e. a lot less powerful.
[Galaxy S II Original Android Development] m2smoe:
And how does this explain why the phone doesn't wake? It doesn't, because clock frequency has nothing to do with it. The problem is voltage. Raise your voltage little by little until the screen wakes properly.
[Galaxy S II Original Android Development] Lennyuk:
if you end up putting it at 100mhz stock voltage and it is still not waking then there is no point you being in 100mhz at all, just stick it at 200mhz stock voltage and never worry...
[Galaxy S II Original Android Development] dica:
i agree i had the same problem when i set <800 mv at 100mhz the cell doesnt wake so the solution is to rise up the voltage values
[Galaxy S II Original Android Development] m2smoe:
Sorry, but that is completely ridiculous. If the phone won't wake up at 800mV @ 100Mhz, it sure won't wake up at 800mV @ 200Mhz.
[Galaxy S II Original Android Development] adyscorpius:
Just to add to the discussion, I think when the screen wakes up, it activates a core now, which would need more voltage than running a core...

Anyways, I find 100 mhz running best at 800 mhz, 200 at 825 mhz and above... While some GS2's might be doing lower voltages, havent heard of anyone getting it stable enough below this...
[Galaxy S II Original Android Development] coolfire:
mv, you mean. :)

Sent from my SGSII
[Galaxy S II Original Android Development] jim-bo:
I find that running 100MHz at 800MHz makes my phone about 8 times faster than normal.... ;)

Seriously, though. I can't get 100 or 200 MHz stable on my phone at anything less than 850mV. Every phone is different, and unless you run a stability test for a good long time, you won't know if your phone will stay alive or not at a given voltage.

As for why you shouldn't run at 100-100 screen-off, or why it works for some people and not others, when I run a stability test at 100Hz, the load average on my phone climbs steadily, easily reaching 30-40 or more before I abort the test and let the CPU scale back up to something normal.

If you run at 100-100, and you have background activities that wake and try to operate, it is possible that there will be more of them running than the phone can actually process at that clock speed, and it will end up timeslicing between then, and lagging to hell and back. Which means that when you try to wake it, you're just adding one more job to the task list, and it'll get to it... sooner or later... in a few minutes... unless the lockscreen times out and goes back to sleep before it displayed it... and then you're well sunk.

The moral of this story is... if you have apps on your smartphone, you probably should think twice about setting a LOW max for screenoff. In fact, why are you setting one at all? If you have apps that wake your phone, find them and reconfigure them so that they don't. Just choking them to slow speeds will actually harm battery life, since the entire phone will be awake far longer than it needs to be while the task completes.
[Galaxy S II Original Android Development] m2smoe:
No no, voltages you set are PER CORE, obviously. You're not setting an overall voltage for both cores, that would be completely idiotic.
[Galaxy S II Original Android Development] Lennyuk:
of course it would as you have given it another 100mhz!

Also it was my understanding that voltages scale with the clock speeds, therefore why would 100mhz stock voltage be the same as 200mhz stock voltage?
[Galaxy S II Original Android Development] terenceleechan:
how to increase voltage values if you set voltage too low and phone won't wake?
[Galaxy S II Original Android Development] Lennyuk:
you can adjust the voltages in SetCPU
[Galaxy S II Original Android Development] DimICE:
Rom manager works fine with codework kernel..

But with SiyahKernel I can't boot into CWM or flash anything from ROM Manager..

It boots into standart recovery..
[Galaxy S II Original Android Development] m2smoe:
LOL! And you're a recognized developer? Wow. There is just nothing to respond here, other than you should learn how a processor works.
[Galaxy S II Original Android Development] Lennyuk:
I have not touched the voltage levels on my phone and I can see that on 100mhz (as stock) it is lower than that of 200mhz (as stock) i.e. not touched.....

If the person who original had sleep issues had also not touched his voltage levels at all, and in fact his only change was from beta 5 to 6 (meaning the drop to single core when screen off) then that lower power will be the reason for his lack of waking up, the CPU is trying to do far too much on this limited power and is not able to get to the "wake up" process before the screen times out again.

If as you are saying his 100mhz is set to the same mv as his 200mhz then yes it would not matter which he is using, but I am suggesting that they are different voltages anyway!

Aside from the fact I may be wrong in my assumption that they differ in voltage as stock what else have I said that is factually incorrect?
[Galaxy S II Original Android Development] moepkid:
so guys how's the battery life on cm7 with this kernel????
[Galaxy S II Original Android Development] Hacre:
Perhaps you should learn how Android waking up works instead of trying to be a smart arse.

CPUfreq isn't designed for people to arbitrarily lock the CPU clocks at 100-100 or 100-200 and when you try to wake the phone up, various things try to happen. The OS wakes up, SetCPU wakes up and attempts to start changing the min/max clock values and the governor if need be. The OS needs processing horsepower to accomplish this, if it doesn't get it, you get stuck in a 100% cpu usage situation and an io queue out of your arse, resulting in a phone that doesn't wake up.

It's a long known issue, underclocking too far/being too harsh on the max frequency speed when screen off will cause waking issues, on a plethora of devices. Instead of letting the governor handle cpu speeds and load, things go wrong when humans interfere and start thinking they're smarter than the code written to handle the CPU speeds. This can result in problems like the phone not waking up. Shocking, I know.
[Galaxy S II Original Android Development] m2smoe:
You are implying that to wake up from deep sleep, the phone needs a minimum of 200 Mhz. That is completely wrong and besides the point. The problem has absolutely nothing to do with clock frequency but with the amount of power required for a certain clock frequency to work properly. Your posts are completely misleading people as to how the whole thing works, and it would be better if you let someone who actually understands how things work explain it to others.

Case in point: Kernels are locked to 800mV MINIMUM, no matter the clock speed. I use 800mv with 200Mhz, and the phone wakes up just fine here. So it doesn't matter if your voltages between 100Mhz and 200Mhz are different, the point is that at 800mV, even for 200Mhz, the phone should wake up properly. And sure, you can say every device is different, but if for me 800mV is sufficient to wake up the phone at 200Mhz, you will never have me believe that it is insufficient to have 800mV @ 100Mhz to wake up the phone. The difference cannot be that great between two devices with the same hardware.
[Galaxy S II Original Android Development] Hacre:
Except the guy was running at stock voltages...which is not 800mV.

Also, if it's a voltage issue can you tell us all why it worked fine on two cores at the same voltage please professor, if the speed/system load has nothing to do with it? Thanks.
[Galaxy S II Original Android Development] kalpik:
Phone not waking can be due to two things:

1. Not enough voltage for the frequency (in which case, your phone is practically frozen).

2. Having enough voltage, but not having enough clock speed to wake up the screen. In this scenario, your phone is technically alive (you should get notification sounds, your phone may ring, but the screen may not turn on etc).

Lenny/Hacre are talking about the second scenario, you are talking about the first.

I think the second scenario applies more here since he is ALREADY on stock voltage, which should be sufficient enough for each frequency step.
[Galaxy S II Original Android Development] jim-bo:
I'm afraid that you really need to learn how underclocking and undervolting differ.

There is no difference whatsoever in the speed / performance / call-it-what-you-like made by the voltage. All that the voltage affects is the power consumption (and heat generation) and stability.

The potential issue due to voltage is that if you take it too low, the phone will crash and thus never wake up, and yes, please do your research, there are big differences between devices. Some people can happily hit 200MHz at 800mV, others need as high as 875mV to be stable, some possibly even more. My particular phone isn't stable below 850mV at 200MHz. Simple fact of life, I got a CPU in mine that is less stable. I also can't get mine to run reliablly at 1600MHz, even at stock voltages... though some people can get up as high as 1700 or more with tweaked kernels.

For the wake problem here, there are two probable causes.

1) he has undervolted too far, and his phone is crashing

2) he has locked his cpu at too low a frequency for the set of apps that he has on it running in the background, and it is lagging back to sleep before it can awake.

The fixes are

1) always check your voltages with stability tests before running them live

2) don't set stupidly low screen-off profile maxima.
[Galaxy S II Original Android Development] peachpuff:
Don't use rom manager, manually boot into cwm by holding vol+up/home/power.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Lennyuk:
or Quick Boot app

or Chainfire's CWM-Manager app
[Galaxy S II Original Android Development] gokhanmoral:
I object :)

In theory, theory and practice are the same; but in practice they are not.

also, the logic behind that is not that simple.

just consider this: you have 200MHz set to 800mV and 500MHz set to 850.

before going up from 200 to 500MHz, you first set your voltage to 850mV and change the frequency.

but if you have 100MHz and 200MHz both @800mV, "maybe" the transition cannot be completed @800mV and you have a sleep of death.

This may not be the reason, this is just an example.

The reason may be completely different and even "unknown" for that specific device.
[Galaxy S II Original Android Development] kalpik:
Exactly. Some frequency steps are so touchy on some devices, that they instantly hang even if you change stock voltage by +/- couple of mVs!
[Galaxy S II Original Android Development] moepkid:
somebody with this kernel on cm7??? i get battery drain with stock kernel from cm7 because it let the cpu run on maximum......
[Galaxy S II Original Android Development] AndreiLux:
No need to act sarcastic around here. Hacre and Lenny are right on the issue. Even if I find Lenny silly :rolleyes::D

And the 800mV limit has been removed long time ago, btw. Things can happen as Gökhan just said above, that's also why I raised my voltages up to 850mV recently, I was getting what seems to be exactly the behavior Hacre said, by having the device fall into a loop, not being to wake up the phone, it heating up, and rebooting with empty battery or major loss if I happen to catch it in time. It happened to me about 3 times now. And it seems to have more to do with the voltages than with frequencies, 200 maximum is not a problem in my opinion.

As I've said, I've had issues with it before the single core patch, but seemingly nobody else had the same experience.

@Hacre: how's the house & car going? :D Still searching for someone to actually look into the AOS issue.
[Galaxy S II Original Android Development] CA3iR0:
Im using CM7 nightly #82 and im getting 2 to 3 days of battery with some internet use. Its amazing! I charged my mobile yesterday and now i still got 74% of battery :D
[Galaxy S II Original Android Development] galeej:
best rom

i have been using this ROM for few days and it rocks... good work developers..
[Galaxy S II Original Android Development] Bene2k11:
It seems like there aren't any heavy bugs in beta6 mh? Got it running one day now, unbelievable battery durability. :)

To previous posts: I got 800mV on 100Mhz and 200Mhz and a Screen-off profile with 100-200Mhz smartassv2. :)

With best regards from my ExynosROM-powered SGS2 always running the newest version of Siyah-Kernel.
[Galaxy S II Original Android Development] energie:
is there any reason to use daemon with this kernel?

doesnt it already set a lower frequency and limit 1 core only on sleep mode?

im only using setcpu for undervolt, no profiles.

I gave a try to smartassv2 gov and it really make my phone lag or stuck for some ms, quadrant bench gave me low resuslts.....im using on demand now.

any suggestion?
[Galaxy S II Original Android Development] :
B6 seems to run quite well cm7.1 stable. Haven't switched back to nightlies yet lol. Battery life seems better at 200-1600 on smartassv2 than 200-1200 on ondemand in stock kernel

Not a single crash yet. Actually first time my phone has been stable for over 24 hours when overclocked....other ROM/kernel combos (AOSP & Samsung) I seemed to get crashes. Even earlier siyahkernel builds running same voltages, and governor...
[Galaxy S II Original Android Development] :
I do seem to notice some slight lag it seems. My guess was GPU as it was more during graphics rendering that it was noticeable

I haven't run quadrant but cf bench and antutu gave normal results as with other governors...
[Galaxy S II Original Android Development] kwerdenker:
And you should learn how one uses arguments and proofs in a rational discussion to convince other people of your own view of things instead of ridiculing the other participants of said discussion.

You assume that if two devices have a chip of the same name these devices work in the same way. Concerning voltages and frequencies this assumption is not true, since both these characteristics have a very close connection to the actual silicon die that chip is made of and that can differ greatly between two devices. I already made a - not so serious - post explaining this in hacres thread a long time ago.

Concerning the whole discussion about voltages and one or two core wakeup: voltages that worked with a two core sleep could lead to problems with a one core sleep depending on the way the voltages are supplied. if both cores are fed by the same regulator the sudden activation of a second drain could increase the stress on that regulator which could lead to a slight drop of the supply voltage. if that voltage already was on the very edge of what the cores needed this drop could be enough to send the whole thing into the land of the undead.

but this is just a possible scenario i cooked up in my mind. without the data sheet of the chip, the supply voltage regulator and/or the circuit diagram this is hard to judge :)
[Galaxy S II Original Android Development] m2smoe:
What are you responding to with that first sentence??

Obviously system load has something to do with it, you're missing my point here. What I'm saying is that under minimal system load (a STOCK ROM for example) 100Mhz is plenty enough to wake up the phone. Proof is that my phone has no problem waking up with 100Mhz @ 800mV. It's not a good idea to tell people that the phone needs a minimum clock frequency to wake up, especially when you don't know the user's system load to begin with, and people in the Recognized Developer "group" should be the first ones to give proper advice and not send users into a confused state where they'll end up spamming the forums and threads like this one, asking stupid questions because of a misunderstanding from half assed explanations like Lennyuk seems to enjoy giving. This isn't the first time I read posts like this from him.

Andreilux: I'm not being sarcastic, and everything you just said is exactly what I've been saying. The major problem here is how Android handles switching voltages for clock frequencies, not the maximum clock frequency for screen off profiles. Instead of raising their frequencies, people should test voltages until they get something stable, starting from stock voltages and going down in 25mV steps.

gokhanmoral: your whole post is repeating exactly what I've been saying. The problem has nothing to do with clock frequency but how Android handles raising voltage at the "wake up" moment. I don't see what it is you're objecting to :confused:

Let me repeat myself then since I clearly wasn't understood: The problem here has nothing to do with clock frequency. The phone CAN wake up at low frequencies, such as 100Mhz. The problem is that people are too lazy testing voltages on their devices and would rather copy someone else's settings and complain about getting wake up issues. So rather than telling people to raise their profile's frequency, you should be telling people to test voltages for each frequency and figure out what works best for their own device. Simply telling them to raise clock frequency is not going to solve this issue.

When I said to Lennyuk that if the phone won't wake up at 100Mhz @ 800mV, it sure won't wake up at 200Mhz @ 800mV, he replied:

So yes, I laugh hard.
[Galaxy S II Original Android Development] Black Dwarf:
This kernel is amazing.

Can someone explain the extra governors available though? Braxillianwax and SavagedZen?
[Galaxy S II Original Android Development] CA3iR0:
Now on CM nightly #83
[Galaxy S II Original Android Development] Lennyuk:
I am going to call you on that, please please please share with us quotes of me doing "this sort of thing" many times in the past, sure I might fail to get my point across occasionally or very rarely actually get things wrong, Christ I am only human, but the majority of the time, and more importantly this time I was correct and you simply tried to make me look a fool and it backfired.

You also seem to be missing the point, there will reach a point on any phone where you can be asking it to do too much on a particular clock limitation, this has happened lots on lots of android devices, especially older ones when CPU's were not as good. In this case it is highly likely this is what has happened here, the phone is just simply not getting to the wake up call before it times out.

100mhz in reality is too low for the majority of people to operate when the phone is being used properly, this is why samsung don't clock that low...
[Galaxy S II Original Android Development] m2smoe:
My words were: Obviously if the phone won't wake up with 100Mhz @ 800mV, it won't wake up at 200Mhz @ 800mV.

Your reply was:

So either you misread me or completely misunderstood, or you have no clue what you're talking about and shouldn't be helping people out. As for hunting every post you've made that has sounded as ridiculous as this one, thanks, but I have better things to do. You should take the amount of users who have stopped taking your posts seriously as a clue towards this. Someone asking for donations in his signature and under his avatar should at least have a rough understanding of how their device works and help people instead of throwing them off track.
[Galaxy S II Original Android Development] Lennyuk:
not trying to be unhelpful but google really does provide a good answer for both those governers simply by googling "[governor name] governor"
[Galaxy S II Original Android Development] :
Hmmh the samesetup and no problems.. Using setcpu or similar? Delete data data from app.
[Galaxy S II Original Android Development] hausmanis:
is beta 1,7b2 optimized for touch-x power+ ?
[Galaxy S II Original Android Development] gokhanmoral:
Not yet but it can be used on touch x power and recommended