yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Hacre:
Not for a lock up. Sounds like something in the different ROM isn't playing nice with your 1.6GHz overclock. Or your voltages. Or both. Or what you're using to set voltages. A solid lock like that sounds like unhappy hardware rather than the kernel.

If you grab a last_kmsg I'll take a look for diagnostic purposes for you (largely because you're not a tool) but I'll be surprised if there's anything useful in it with a hard lock. Maybe get a couple to see if there's a trend.
[Galaxy S II Original Android Development] dirobeshploppy:
Maybe he was looking in the mirror when he wrote it
[Galaxy S II Original Android Development] Major_Sarcasm:
Headline: "Hacre in non-insulting post shocker"

I wondered about KG6 not being so hardware-friendly and will play with the OC/UV if it persists.

Quite. I don't mind people calling me a wanker for a reason ;)
[Galaxy S II Original Android Development] EarlZ:
Yes some phones do have different voltage per clock speed, its like the VID you get from current generation Intel CPU's
[Galaxy S II Original Android Development] tolis626:
Well,I had some reboots,but the bloody phone hasn't crashed again since early yesterday.

Hacre,reboot kmsg's are welcome I suppose?I can't properly understand how they work.Perhaps I shouldn't be checking it from the phone. :p
[Galaxy S II Original Android Development] Hacre:
adb shell cat /proc/last_kmsg > last_kmsg.log. As per the first page of the thread. *slap*
[Galaxy S II Original Android Development] veyka:
Bloody wanker ;)

(I saw what you did last night)
[Galaxy S II Original Android Development] Hacre:
Had an overzealous self appreciation session resulting in injury? :confused:
[Galaxy S II Original Android Development] Major_Sarcasm:
You all saw that? ****. Note to self: Turn off webcam.
[Galaxy S II Original Android Development] veyka:
Not quite enough lubricant!

Im in ur video devices haxz0rzing ur streamz
[Galaxy S II Original Android Development] JAG131990:
Unsubscribed.
[Galaxy S II Original Android Development] inkyadrian:
I have these uv's

200@800

500@850

800@950

1000@1050

1200@1150

1400@1250

Running Revolution 2.4 & Ninph 2.0.5.

No problems.
[Galaxy S II Original Android Development] Major_Sarcasm:
And your CPU voltages are relevant to me how exactly?
[Galaxy S II Original Android Development] JDouce:
what toolchain do you use to build this kernel,

when I try to build from your source I get invalid option "-mno-unaligned-access"

tried with various toolchains

all I want to do is build the usb serial modules.

usbserial.ko

ftdi_sio.ko
[Galaxy S II Original Android Development] dirobeshploppy:
No you mean uncircumcised
[Galaxy S II Original Android Development] Hacre:
Do I look like tech support for how to build stuff? Hint: I actually do not.

Well you see because
[Galaxy S II Original Android Development] AvRS:
Oh no, don't do it, your phone may explode!!!! :eek:

Thanks for this useful post but you could of just done it without expressing your lack of a sense of humour! Obviously not everything is to people's taste but it certainly does fill in the gaps between annoying, stupid, noobish, repeated, already accessible (the list goes on) questions being asked. Your post does nothing except to show your need for attention and hope that someone reading it actually cares. Yes I replied but only because it's more annoying then people asking the aformentioned questions, as for you being subscribed to this or any thread.....oh look a rainbow.....sorry what was that?

Rant over.
[Galaxy S II Original Android Development] Hacre:
Ha niiice.
[Galaxy S II Original Android Development] sonic9:
Thanks for cifs.ko path ! works great with cifsmanager !
[Galaxy S II Original Android Development] mrabcx:
Kernel generally works very well .. .. but I have experienced a couple of unexpected crashes under different conditions. This one happened while using Google Maps, have attached a zip of last_kmsg....
[Galaxy S II Original Android Development] tolis626:
Yes?I know how to do it,thank you but I wasn't asking.I just wasn't near to a PC,so I checked it through root explorer,that's all.I just don't completely understand what everything in there means.I'll make sure to upload it next time something happens.

Irrelevant:

Any news on the FM transmitter or GPU control?
[Galaxy S II Original Android Development] jeedjaad:
thank

:D:D:D:Ddownload now
[Galaxy S II Original Android Development] CaspaTheGhost:
Can you just do it anyway mate?

You know what, I actually read his post as being a bit of deadpan humour?!?!

Guess we'll have to wait to see if he replies to you.... We could be here for a while if he's no longer subscribed though...
[Galaxy S II Original Android Development] JDouce:
#1 the time it took you to be an ass you could have typed the toolchain

#2 forget it I just switched kernels

#3 you ****ed up your makefile with moronic placement of comments midway through commands.
[Galaxy S II Original Android Development] galanakop:
go be a legend kernel ... and this is no exaggeration ... Give us a good time on the battery with as little as possible fc Continue the hard work ...
[Galaxy S II Original Android Development] Hacre:
Bye then! o/
[Galaxy S II Original Android Development] inkyadrian:
Move on!
[Galaxy S II Original Android Development] JAG131990:
Didn't know straights were the minority here, my mistake! By all means I apologize sincerely please do continue in the little flirtatious to and fro you fellas call "ill masturbate while you watch", and we can all just have our little giggle

Also good to know I have annoyed you more then the aforementioned noob questions that plague this thread. Maybe you can request my presence in post five.. as for persuading the right people to do so.. well im sure ur creativity will take u there. 8==D O: ???

Edit: as for what Caspar said, thankyou good to see someone gets it. Afterall I am back here aren't I. I suppose not everyone appreciates a tad of sarcasm and a dry sense of humour.
[Galaxy S II Original Android Development] pspilot:
Are you serious? I thought that's common knowledge. Ok, I assume underclockers want to save battery and not just watch their toy working a bit longer on the same tasks. But that exactly is happening when you have a given software structure and things have to be done. In other words, you save energy per time, but you need more time with the slower clock. So underclocking alone doesn't help alot to save energy. But undervolting reduces the loss currents on the gates (when switching, basic CMOS technology) and even more, stray currents on the chip. So there's the potential to save. But you have to underclock, when you want to undervolt - that's the logic, not the other way round.

P.S.: Oh, all of the above if considering of course a modern power management, which sends the CPU to sleep or idle most of the time.

P.P.S.: Nice link for the truly curious ones, section "Power: switching and leakage"
[Galaxy S II Original Android Development] Hacre:
Yeah great. Lift yourself out of wikipedia for the moment and back into the real world.

Running at 800MHz is a lower voltage setting than 1000MHz and 1200MHz.

The vast majority of tasks your average phone user such as myself and many others who have taken various pains to actually test these CRAZY theories out, are more than adequately performed at 800MHz (or even in some cases, 500MHz).

Your points have some merit, but saying you HAVE TO is a complete fallacy. I will add here, that after those tests were carried out, I then undervolted, because I can and because I can the further additional power savings make sense. But if you're unlucky enough to have a phone that you just can't really touch the voltages on and remain fully stable, there's still lots to be gained via a simple underclock. People can take my word for it, or test it all for themselves. Many did before we got various undervolting tools and came to the same conclusions.

So to answer your question, yes I'm serious.
[Galaxy S II Original Android Development] pspilot:
My real world consist of hardware development on chip level in my company. I don't need wikipedia for that, it was a friendly link for people who do.

And? That's what I said. When you run slower, you can lower the voltage and THAT'S what safes energy. That's the reason for running slower, the possibility to lower the voltage.

You can run any speed you like or need, but as long as you don't set the voltage not higher than necessary, you don't safe alot.

Well, of course you don't HAVE to - but then you don't safe. Why do think are there different voltages for different clocks? You could run all speeds let's say at 1400mV, from 200-1600MHz, the CPU has no problem with that. But then you waste alot of energy with the slow clocks.

The longer we talk, the more I have the feeling we're talking about different things. For me 'undervolting' is just the fact of lowering the voltage with the clock.
[Galaxy S II Original Android Development] Hacre:
Errrr?

By default when you lower the clock on the SGS2, the voltage lowers.

When people talk about undervolting in these threads, they're talking about taking advantage of an additional (as in provided by a third party through kernel modifications, not by Samsung) voltage drop outside of Samsung's default norms.

Clearer? The confusion has come in because it seems you created a point of contention where there wasn't one, we all know that lowering the clock and only lowering the clock lowers the voltage...if you know that and everyone else does why did this conversation start?

EDIT: This started to bug me, for two reasons, one I was sure when I replied to you I was assured my sarcasm was well placed and two, the fact you're obviously not an actual real XDA forums dwelling idiot I started to wonder if I was going to uncharacteristically make myself look stupid. So I went back and checked.

It would seem, we can blame Veyka for the whole thing. Someone said he had underclocked but hadn't sorted out his undervolting yet. Veyka appears to have stomped in with his size nines making claims of strangeness where there is none in a conversation about typical applications of the terms "underclocking" and "undervolting" within the SGS2 vacuum, since Veyka should know that underclocking means a reduction in voltage in the kernel's CPU driver. Then you came in saying "Underclocking without undervolting is nearly useless". See you were being technically correct and verbose in the broad meaning that you can change a clock speed without touching voltage at all, however in a conversation about underclocking and undervolting specifically on the SGS2 this threw up all kinds of confusion.

In conclusion, you're right, I'm right, Veyka is an idiot and needs a slap, I'll make sure he gets one later.

Apologies for my earlier brusqueness, it's quite a nice surprise when technically competent people show up.
[Galaxy S II Original Android Development] pspilot:
Sorry, when I wrote my answer your post still ended with the word 'fallacy'. Slowly I understand your point. You take the undervolting as granted standard and talk about under-undervolting. Agreed, that can be an adventurous thing to try. My answer was totally general and in general it makes no sense to reduce the clock when you don't reduce the voltage. Maybe I misunderstood 'undervolting' in this context.

Now, I think I don't want to get into the discussion about what 'underclock' exactly means ... here :). But sure enough limiting the max. clock can help saving battery, especially with 'hungry' apps. Never doubted that.

Good.
[Galaxy S II Original Android Development] pspilot:
Because you wanted to call me an idiot :D?
[Galaxy S II Original Android Development] Hacre:
Yeah I also have a habit of having another thought after I hit submit and editing. As you've probably noticed by now in my reply to you prior to this one where I blame it all on Veyka anyway. :)

And again in this post. I didn't want to call YOU an idiot. I wanted to point out perceived idiocy. I just like calling idiots idiots. Morons morons. Inept buffoons inept buffoons. All too often these crimes against society go unpunished and/or unrecognised. It's a public service. :D
[Galaxy S II Original Android Development] pspilot:
Jeez, I'm hunting your edits ... no need for an apology. Looking twice at my very first answer, I could have thought about the context too. Anyway, case cleared. For a second I thought about not to explain more ... I like you style when you're ranting :).

Not beeing a native English speaker I'm probably missing alot of the fine tuning in your language. Got it now.

Thank you Sir :).
[Galaxy S II Original Android Development] Major_Sarcasm:
For someone who's first language is not English, you put a lot of natives to shame. However, just to help you improve your already impressive skills, the past-tense of 'safe' is 'save'.
[Galaxy S II Original Android Development] Hacre:
Ahem I do believe you're confusing verbs and adjectives here good sire with temporal senses.
[Galaxy S II Original Android Development] kalpik:
WANKER! :D
[Galaxy S II Original Android Development] Hacre:
Hahahaha I sidestepped the obvious and begging opportunity for this knowing someone else would. xD
[Galaxy S II Original Android Development] B3311:
I'm going to put this in my sig - with credits, of course. Sheer class.

And a handy reminder to self too for my senior, idiotic, moronic and inept moments too..
[Galaxy S II Original Android Development] Major_Sarcasm:
Bah, he still got it wrong ;)
[Galaxy S II Original Android Development] pspilot:
Believe it or not, I know about that 'safe' / 'save' thing. It's happening still, like you say 'left' the moment you realize it should have been 'right' :). But thanks anyway, I appreciate sane criticism ... the more since you had to expect some of the comments :D.
[Galaxy S II Original Android Development] Major_Sarcasm:
Indeed. I read my comment back to myself earlier and thought "You idiot, you know the difference between an adjective and a verb." But by then I'd already been picked on :D

Bollocks.
[Galaxy S II Original Android Development] pspilot:
Did you mean me? I'm not going to correct it. It's written, it's wrong and it's marked as wrong. That's enough for a few 'f's :).
[Galaxy S II Original Android Development] AndroidGX:
Hello, as promised, I post my lastkmsg since I just got a reboot at yellow triangle.

It just appears after 2 days of normal/hard using and when I just tried to quit Gmail app with back hardware button, and then it rebooted.

Here is the last_kmsg.log zipped.

Hope this helps.

Many thanks!
[Galaxy S II Original Android Development] Testraindrop:
No offense, but

and

:rolleyes:
[Galaxy S II Original Android Development] AndroidGX:
A lot of people using 800mV max for 200Mhz, my hardware seems accepting it. 25mV more and it's shutdown after few mins hard using :)

Never had any problem with those my UV settings untill I jumped to KG6 rom, someone told me if it was reboot at yellow triangle, it's kernel problem and must post last_kmsg for Hacre.

Here it is ;)
[Galaxy S II Original Android Development] fenomeno83:
these UV settings working stable for 8 galaxy s2

1200MHz - 1175mV

1000MHz - 1075mV

800MHz - 975mV

500MHz - 875mV

200MHz - 825mV
[Galaxy S II Original Android Development] eiraku:
Unlike all the other fragile types out there, this is the main reason I'm still here.

But really, what is wrong with most of the new faces flocking to ALL the forums worldwide (not just here)? If you can't freaking read and take criticism, why on Earth are you on the net?

Then again, how are you even still alive and functioning socially in the first place?
[Galaxy S II Original Android Development] plaut:
The arguments in this thread are confusing (if still mildly entertaining). I thought the basic idea regarding underclocking/undervolting was straightforward:

The stock settings on my SGS2 are 1425mV @1600MHz and 1075mV @800MHz. Assuming a given computation takes twice as long at 800MHz than at 1600MHz, it "costs" 2150mV at 800MHz to do what 1600MHz can do for 1425mV. That is, if voltage grows sub-linearly with clock speed, it's always better to run at the fastest clock speed possible in order to get back to idle (200MHz) as soon as possible.

This is all independent of undervolting (which always helps as long as it's stable) assuming the clock speed to voltage relationship remains sub-linear.
[Galaxy S II Original Android Development] AndreiLux:
Your logic is flawed/bull****. Voltage is NOT power draw.

To sum it up nicely:

We can ignore C as it's a constant, so you basically have V² x f if you want to calculate your power draw.

1425² x 1600 = 3249M power units

1075² x 800 = 924M power units

("units" here are irrelevant to real world metrics or watts since they are both relative to each other, and we don't know the capacitance, which again is irrelevant since it's a constant)

If you to scale that by 2 like you did then we get 1848 if you scale up the low frequency at low voltage up, or 1624 if you scale the high frequency down, which is basically almost a drop of a factor of 2 in efficiency.

Power draw scales linearly with frequency, and it scales exponentially with voltage, and that's why you should undervolt.
[Galaxy S II Original Android Development] Nebucatnetzer:
Just a question. Do you don't need the time as well? When the cpu freq is higher it would need less time to calculate something which means it could go faster back to a lower level so compared with a lower frequency they would use more or less similar amounts of energy.

As I said just a thought I'm not really good in maths.
[Galaxy S II Original Android Development] AndreiLux:
Frequency is the amount of cycles a transistor switches in a second, so if you have for example a task which takes up 1 billion cycles, you can compute them at 800MHz and it would finish in 0.8s or at 1600MHz and it finishes in 0.4s. But the power cost you have to pay to compute it in 0.4s is almost twice as high, even if it takes half the time to do it. You're basically sacrificing power in order to get things done faster.

The only reason we compute things faster is because of user experience and we want things to be "smooth", and the only real need for speed *is* when we use the phone when for example scrolling/zooming a website or gaming. You don't give a rat's ass what other things in the background are running on or how long they take (to a respectable limit). That's why power efficiency when idle or screen is off is so important.
[Galaxy S II Original Android Development] pspilot:
Right on - wonderful explained.

Well, isn't that one of the biggest lack nowadays (and I don't mean people alive)?

In the first place, the formula shows that voltage is much more important than frequency, when it comes to power efficiency. The question, whether 'fast&hot' is better than 'slow&cool' can't be answered generally. It depends too much on the architecture of the system and the software structure. But with the invention of the lower voltages at slower clocks, working longer, but slower is more efficient. Having said that, there are systems that benefit from a fast completion, i.e. when additional hardware is involved. If you have to switch on an additional consumer which is on all the time the CPU is awake, the calculation looks different again.
[Galaxy S II Original Android Development] Nebucatnetzer:
Ah yeah right. My electronic teacher would slap me for this :D.
[Galaxy S II Original Android Development] pulser_g2:
Good to see some more discussion of stuff like this. I was thinking I was gonna have to look out the equations for reasons to uc and uv...

I will look at optimising my phone tonight - I need to do a full wipe and oust the crap, then get some UV settings going :)
[Galaxy S II Original Android Development] Hacre:
*clears throat*

What? Did you miss a quote or quote the wrong post? Or did you just assume I was being a grammar nazi instead of recognising actual rapport between myself and two other regular posters in this thread?
[Galaxy S II Original Android Development] veyka:
Hey, I have size 12's!

I already called myself a ****ing moron, I had just come off a long arse nightshift, so fu! :D

See, I am a twat, smack away baby ;)
[Galaxy S II Original Android Development] AndreiLux:
Are there any updates on work for GPU control?
[Galaxy S II Original Android Development] EarlZ:
Answer is on the first page, first post. I dont know how you missed it after reaching page 185.
[Galaxy S II Original Android Development] Hacre:
FAQ updated with answers to "new feature" related questions so people can ignore that and post about it anyway. :)
[Galaxy S II Original Android Development] AndreiLux:
Yes and I've also asked on the very second page the those things which is why he put that part in the first post. I was just asking on an update on how things were going along in that regard. Now stop being a smartass and go do more productive things like sodomizing yourself with a cactus.

Thanks for the update.
[Galaxy S II Original Android Development] eiraku:
Was recognising the rapport lol, hence "this is why I'm still here" part. Plus the deadpan humor is always awesome too.

Rest of the post was a general rant. A very general rant.

*hands hacre an ice cold beer*
[Galaxy S II Original Android Development] inkyadrian:
I was wondering. If I wanted to kill myself with electricity, would it be better to touch a third rail dc electric rail line @ 1200 volts or the overhead ac wires @ 25k volts?

Yours, waiting patiently to die.
[Galaxy S II Original Android Development] Hacre:
Just move out of Bolton mate.
[Galaxy S II Original Android Development] Nebucatnetzer:
I would recommend ac. Should go faster but if you like to suffer then you should use dc.

But when you touch the overhead lines make sure that your feet are touching the ground.
[Galaxy S II Original Android Development] Hacre:
Next on XDA Suicides we hear from a guy with an old resistive screen and he's lost his stylus.
[Galaxy S II Original Android Development] inkyadrian:
What a load of crap! I thought you lot knew about voltages, ampheres and suchlike? Ah, millivolts! Well, if those who say " put a florencent bulb under the overhead, electric wires, and it lights up, can we use the overhead wires to power our PDA's? Such great power and such miniscule voltages on our phones. I am going to use this Home Plug thing to connect, not to use my internal ac supply in the house but to plug into: BT phone, Network Rail and my vibrator.

OOPS , just electrecuted my self.
[Galaxy S II Original Android Development] Hacre:
On second thoughts, please stay in Bolton.
[Galaxy S II Original Android Development] inkyadrian:
I am all over the place. I keep wandering because these bolts through my neck keep connecting to ELECTRICITY and , well, personally, I am trying to flake out my PDA and it is taking too long. I may undervolt it to 120 usa volts and try to kill myself with some Vodka.
[Galaxy S II Original Android Development] JAG131990:
Try metho, its much cheaper
[Galaxy S II Original Android Development] CaspaTheGhost:
Man I love this thread... Useful information and a guaranteed laugh, this time around I was blessed with a good few laugh out loud moments, I thank all that participated in the last 5 pages... Helped my sanity no end after having to trawl through 10 pages of the brain dead in the Cognition thread...

And...

Thought so, to be honest it had to be in this thread!

Finally...

Seeing as I've corrected those that like to make Hacre sound like a well know Christmas carol, I feel compelled to defend the spelling of my name... It's Caspa mate, no R at the end...

Harcre herald angels sing, glory to the new born king...
[Galaxy S II Original Android Development] ebliss:
Someone made a video of flashing the kernel to use with GLAS shield. Funny comment at 2:50. lol
[Galaxy S II Original Android Development] jlevy73:
Congrats on having the patience to read through all 10 pages of that gank. I got to page 2 and passed out from the sheer stupidity. That thread needs a serious iron fist intervention.