yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] dirobeshploppy:
You're quite right - there is no place for humour in this thread. Or in life. Those people who post humerous comments are quite clearly affiliated with terrorists who want to steal our babies and force feed us gravel. Many thanks for bringing this to our attention.
[Galaxy S II Original Android Development] Major_Sarcasm:
Welcome, to the ray of sunshine.
[Galaxy S II Original Android Development] Major_Sarcasm:
Click^^

Legend.
[Galaxy S II Original Android Development] Hacre:
Can the moderator who decided to delete post 5 and butcher my OP PM me please so we can go over the finer points of how to edit posts without making the original poster look like an illiterate mouthbreathing dyslexic who suffered horrific hand injuries? Thanks so much.
[Galaxy S II Original Android Development] runedrune:
Everything still looks the same to me :o
[Galaxy S II Original Android Development] inkyadrian:
Hello Caspamate :D
[Galaxy S II Original Android Development] Hacre:
I fixed the OP and another mod put post 5 back.
[Galaxy S II Original Android Development] CamoGeko:
Yeah, same here. :)

Edit: nvm...
[Galaxy S II Original Android Development] CaspaTheGhost:
:mad: There's a damn space! Grrrrr....

:p ;)
[Galaxy S II Original Android Development] CaspaTheGhost:
Dont let them mess with your mind, changing stuff around is where it all starts... Sure you've seen that Pepsi advert...
[Galaxy S II Original Android Development] tolis626:
Lemme get this straight.Someone dared to mess with the legendary,unforgettable and unique post 5?****in' ****.That's pure blasphemy.

Oh Hacre,seeing as you won't be available for the next weeks(I wish you and your wife have a...good time during Honeymoon by the way ;) ),couldn't Netarchy take over responsibility for this thread during that time?Taking care of new features and all?

Unless he only takes donations. :p (Not reffering to whether he contributes to development and all,he sure does)
[Galaxy S II Original Android Development] Hacre:
If he does choose to release anything before I come back I'm sure he'll make it available.
[Galaxy S II Original Android Development] alishankiti:
Thanx for ur work. The latest kernel breaks my wifi. I am using madmack 1.6.
[Galaxy S II Original Android Development] goldbergx:
You added an extra 'r' to Hacre's good name just because someone added one to yours? :eek:

PS: love the kernel, love the humor.
[Galaxy S II Original Android Development] Hacre:
I'll get right on that.
[Galaxy S II Original Android Development] CaspaTheGhost:
Whoops! My bad, that's what happens when I post at 3:45am...

Should have been people referring to Hacre as Harce... The Christmas carol bit still stands, actually it works much better this way...

Harce the herald angels sing, glory to the new born king...

Now thats what I call support, get that man a beer!
[Galaxy S II Original Android Development] tolis626:
Nice,I can sleep happily now. :p
[Galaxy S II Original Android Development] tolis626:
At last,the long-awaited reboot came! :D

So,I flashed KH3 modem through CWM(don't feel exactly comfortable with Odin anymore),I rebooted,checked if it flashed correctly,turned on wifi,connected to the internet to check if it works(Out of habit,nothing more),closed wifi and turned the screen off.Next moment I looked at the phone,I was looking at that horrible yellow triangle below the Samsung logo.

My lastkmsg shows,from what I was able to understand,that the kernel panicked when something tried to alter brightness,or something to do with the backlights.Better see for yourself Hacre.

Hope this helps. :)
[Galaxy S II Original Android Development] fenomeno83:
your UV settings are very similar to mine.. but only the 200mhz I prefer 825mv, because sometimes has difficult to wakeup from sleep mode at 800mv..

but this depends from chip..

Me and 11 my friend use

1200MHz - 1175mV

1000MHz - 1075mV

800MHz - 975mV

500MHz - 875mV

200MHz - 825mV

and works well in every situation!
[Galaxy S II Original Android Development] AndroidGX:
I did some interesting tests with 2.0.5, with NO UV and UV with a stress test app.

Here are the results :

I am a bit surprised to "only" gain 40 seconds, is that normal ?
[Galaxy S II Original Android Development] avetny:
hi! when is gonna be something AGGRESSIVE ! BEST benchmarks scores ! (1.2-1.6 Ghz)

can u bake for some people like me...;)
[Galaxy S II Original Android Development] Hacre:
Qap'la!

...

What?
[Galaxy S II Original Android Development] avetny:
Hе пoнял!

...

Im asking about some new kernel, which will demonstrate to us "increased the amplitude" without overclock.

Which is bringing performance to your phone...

With the expectation that the battery does not matter to us.
[Galaxy S II Original Android Development] JAG131990:
You are a sad strange little man..
[Galaxy S II Original Android Development] avetny:
... it just your opinion son

Trinity

http://androidcommunity.com/nexus-s...nce-benchmarks-with-trinity-and-cm7-20110530/
[Galaxy S II Original Android Development] JAG131990:
Please don't try to marry my mother
[Galaxy S II Original Android Development] avetny:
nobody cares about your mom.

everything about: http://androidcommunity.com/nexus-s...nce-benchmarks-with-trinity-and-cm7-20110530/
[Galaxy S II Original Android Development] Hacre:
Yeah....not a ****in clue what you're on about mate.
[Galaxy S II Original Android Development] avetny:
:)you probably do not get enough sleep?
[Galaxy S II Original Android Development] tolis626:
Basically he's asking about something that I'd also like to see at some point in the future,but not THAT desperately to come asking.A kernel that will push the phone to its absolute limits so that it would kill every single benchmark we throw at it.A good start would be "lifting" the framerate cap(Which is V-Sync,but I don't know why it's called a cap in phones by everyone).The S2 already limits the counters of every graphics benchmark with the GPU @267MHz.Imagine OCing the GPU @400MHz and disabling V-Sync.The result will be something like:

Sensation User:"Holy shiznit!That thing is too fast! :eek: "

G2x User:(Looking with remorse at the G2x in his palm) "Go away you piece of ****"

So yes,for the pleasure of kicking every other phone's user in the balls(so to speak),I'd like to see a kernel lifting all limitations.

A note to you Avetny.These numbers you saw are results of a rom using a Quadrant cheat.5500ish results with 15000ish in I/O is pure bull****.That way my Desire HD does 5500ish and my Desire about 4000.The GS2 results in a nice 5000 ONLY with a 1.6GHz overclock,nothing more.Users using Quadrant Cheat could get 6000-6500.
[Galaxy S II Original Android Development] Hacre:
Oh, pointless Quadrant ****. Ok, carry on.

(No, neither myself nor netarchy are going to waste free time to purely **** about with benchmarks. Not unless we get really, really, REALLY bored. GPU clock control is coming. It's likely that the vsync "cap" is part of Android and not the kernel.)
[Galaxy S II Original Android Development] avetny:
Thank you my friend for "decoding" to him :D

I know about hacks., but I know MORFIC and Netarchy also.

I like Netarch's kernels, but they never boasted in benchmark's

if you saw the link.

Try do not look at to I/O

check the CPU results (before and after).

oh and "that" guy realized what I said....it just hurt him (but I still like "NETARCH's and hacre" kernels ;))
[Galaxy S II Original Android Development] inkyadrian:
Mine wakes up at 200mhz@751 mv. You can not lower it lower. OOPS Its crashed.
[Galaxy S II Original Android Development] tolis626:
Well,frankly,I don't give a **** about Quadrant.I even removed it from my phone recently.But there are a ton of more efficient benchmarks.I would love to see Nenamark,both 1 and 2,run without the framerate cap.Quadrant is just the most widely known and,for some god-forsaken reason,the most referred to benchmark.Killing Quadrant would just be about shutting some mouths that tend to be very insulting and arrogant.So get really,really,REALLY bored soon.A friend has a G2x and I'd love to see his face when we dust all over his new precious toy(Nothing more than a toy it is ;) ). :)

Now,if V-Sync is part of Android...Well,**** it.No one can reach the limit if they don't own a GS2.We can.A kind middle finger is all they'll get.BUT,the G2x(Dunno about other Tegra 2 devices) doesn't have it,so I don't think it's THIS general.Remember,the Evo 4G was "capped" at 30FPS.Not that it can reach much higher in most situations with the Adreno 200,but just sayin'.

As for GPU control...**** YEAH!!!!!!!! :D
[Galaxy S II Original Android Development] tolis626:
****.You serious?

THE KERNEL DOESN'T ALLOW VOLTAGES TO GO LOWER THAN 800MV FOR CHRIST'S SAKE!
[Galaxy S II Original Android Development] inkyadrian:
Oops. just woke up. Eh?
[Galaxy S II Original Android Development] tolis626:
Such increases are only natural with overclocking and some proper optimizations,make no mistake about that.The only reason the Desire HD gets lower scores while using the Quadrant cheat or similar stuff is because of bad(compared to the Nexus S) 3D performance.I think it performs slightly better in all other aspects.Using CM7 of course,Sense doesn't cut it if benchmarks are your main goal(My daily rom was Sense since the first day I got my Desire HD until its last day as my main phone,so everyone should avoid claiming I'm a benchmark junkie).

Now,NETARCHY is one hell of a developer,no one can doubt that.But Hacre is as good as Netarchy(won't even bother comparing,both of them kick ass),so I'd show some respect when writing in the thread of a developer this good,even if they didn't think the same bull**** as I do(and I tend to think of much bull**** on a daily basis).Netarchy and Hacre is more like it. :)
[Galaxy S II Original Android Development] tolis626:
No.

And,if I were you,I wouldn't post ironically about someone else.Check your bull**** and then come back to criticise me or anyone around here.Thank you. :)
[Galaxy S II Original Android Development] inkyadrian:
Well, for your Chist's sake, I have.
[Galaxy S II Original Android Development] tolis626:
You have what?You have gone below 800mV?Surely?Jesus...

I give up on you dude.Be happy with your 751mV phone,pretend I don't exist and that I'm not part of this forum.Goodnight.
[Galaxy S II Original Android Development] inkyadrian:
Well, it maybe a false reading, but; I don't know.
[Galaxy S II Original Android Development] tolis626:
It is a false reading dude.The kernel decides what voltages you are allowed to use.The option for 750mV is there in SetCPU,this doesn't mean you can use it.
[Galaxy S II Original Android Development] inkyadrian:
I have. So mote it be
[Galaxy S II Original Android Development] inkyadrian:
I have used it.
[Galaxy S II Original Android Development] CaspaTheGhost:
We've had some varied dialects in this thread, but you've just taken it intergalactic!

One thing though... "romuluSngan Hol yIjatlh. He'So' QIchlIj."

Speak Romulan! Your accent stinks.

So your not prepared to '****' about in order to produce a kernel that will allow some of the great users of XDA to play about with their 'dicks'?!

Shame on you sir...
[Galaxy S II Original Android Development] avetny:
-----------------

+1
[Galaxy S II Original Android Development] tolis626:
Lemme guess...Star Wars fan? :D

As for the "****" part,there is an expression in Greek which would translate as "You are for the ****",meaning you suck baaaadly.Sorry,but that's what this particular post deserved. :p
[Galaxy S II Original Android Development] CaspaTheGhost:
Wrong 'Star' mate, it's actually 'Trek'... Not a massive fan but Hacre's use of Klingon warranted it!

Didn't like it no? Oh well, I actually thought it was a nice little play on words... ;)

That translation sounds like something you'd expect those at her majesty's pleasure to hear whilst showering! :eek:
[Galaxy S II Original Android Development] jlevy73:
The screen of the Galaxy S II has a refresh rate of 60 Hertz, so the screen physically cannot display any material higher than 60 frames per second. If you uncap the software frame rate, then the CPU and GPU of the phone will work harder to render as much material as possible - let's say in this case, we have something that has 80 frames to display in a single second. Yet since the screen cannot display 80 frames per second, 20 of those frames will never be shown, and the resulting movement might even suffer from tearing because of the mismatched refresh rate and frame rate. In order to fix tearing, vertical sync is employed, which would cut frame rates to 60fps in order to eliminate the extra frames which cause tearing.

So, if we remove the frame rate cap on the SGS2, then what do we accomplish? We increase the workload on the phone's processors, increasing heat output and decreasing battery life. Rendering above 60fps will generate frames which are never shown, and will introduce visual glitches if vertical sync is not used
[Galaxy S II Original Android Development] veyka:
But it's not doing anything, there is a hard cap at 800mV, that's the minimum the kernel will give the chip, you could set it to 0mV and it would still be giving it 800mV.

This has been gone over many times.

Accept it!
[Galaxy S II Original Android Development] tomdot:
Using 2.0.5 and BLN giving errors

EDIT: Found the answer and fixed. However it's fair to say the liblights fix file should be posted to POST 1.

Or atleast a link to post 1113
[Galaxy S II Original Android Development] Nebucatnetzer:
And why do we achieve a remarkable performance boost when we disable v-sync in a computer game?
[Galaxy S II Original Android Development] pulser_g2:
Welcome to post 5, most likely... Did you remember to use a proper ROM, or to add the BLN driver to your current ROM?
[Galaxy S II Original Android Development] tomdot:
Found the answer and fixed. However it's fair to say the liblights fix file should be posted to POST 1.

Or atleast a link to post 1113

Thanks for the sarcasm nevertheless... It's only about 800 posts back... :)
[Galaxy S II Original Android Development] Nivekius:
I have had more than three times now that it crashes in I assume deep sleep, because it actually happens when I am sleeping :p and so far only when not charging (which I think lets it stay in 200MHz?). Crashing would not entirely be a big problem, but it also starts heating up and draining the battery entirely. So how can I fix this?

Using 2.0.5 and its underclocked to 1GHz and also undervolted, frequencies are individually tested with Stabilitytest for more then 30 minutes.
[Galaxy S II Original Android Development] k1000716:
Before the flaming starts, remove the undervolting and underclocking. See if the problem persists. It's not likely to be a kernel problem.
[Galaxy S II Original Android Development] pspilot:
All these pleads "Please Hacre, let us fry and melt our phones for a funny benchmark chart" reminds me of another question: the kernel is boosting the charge current, as I read in earlier posts. Are there any more details? Is it just the USB setting or also the AC? How much is it boosted?

Background: obviously the SGS2 can consume more than the AC input can deliver. Several people report for example, while using navigation (probably with bright screen), the battery is discharged despite the connection to a (proper working) AC source. So increasing the AC 'intake' wouldn't only speed up charging (possibly), but also supply the unit properly. AFAIK there were rumours about Samsung even increasing these values. On the other hand, 650mA are already drawn while in AC mode. The million times supplied original wall brick from Samsung delivers only 700mA. Car adapters could do more, but there's no 3. mode, AC is for everything but USB. I doubt that Samsung is setting it higher than their own wall plug can deliver.
[Galaxy S II Original Android Development] tolis626:
****,Star Trek and Star Wars always confused me.Dah... :p

Anyway,I didn't like this one in particular.Don't take me wrong.
[Galaxy S II Original Android Development] AvRS:
You deserve a slap not a phone! Go play with yourself or maybe you and your friends can compare other things other than benchmarks, I'd say IQ but then that's probably beyond your ability.

I'd say the answer to your question why is because of respect for each other's work and ability, something you seem to be missing. Oh and couldn't care less whether this is poor/dry/crap humour or the like as think you're downright disrespectful and don't deserve the time or benefits this forum gives the users. "Iron Fist" anyone? We can hope I guess.

Where's Hacre for some entertaining abuse when you need him ;)
[Galaxy S II Original Android Development] carlos67:
Unfortunately for us he's off on honeymoon with his missus (fortunate for him of course :D)

He'll be back with all guns blazing I suspect in a week or two ;)
[Galaxy S II Original Android Development] avetny:
Troll .... re-read comments...and only then do the findings
[Galaxy S II Original Android Development] inkyadrian:
Absolute rubbish. I set it to 750mv, the phone crashes.
[Galaxy S II Original Android Development] eatonjb:
Please don't hate on this question.

What has been the best and most stable UV settings .. I am not OCing it.. 1200 is good for me.. but i knocked the V's down a bit, but I would like to start with a reference plane, and work up and down from there.

thx.

otherwise.. so far so good.
[Galaxy S II Original Android Development] CamoGeko:
http://xdaforums.com/showpost.php?p=16702869&postcount=2016
[Galaxy S II Original Android Development] jlevy73:
Because the same hardware limitations are not in place. For the SGS2, the limiting factor is the screen.
[Galaxy S II Original Android Development] jlevy73:
In SetCPU, go into the info tab and look for 'time in state'. Does 750mV appear as a line item?
[Galaxy S II Original Android Development] carlos67:
Good question

Me thinks that the answer to this question will surely put this issue to bed once and for all. And tfft :rolleyes:
[Galaxy S II Original Android Development] carlos67:
Now, before everyone jumps on my bones:eek: I know all about Atinm asking Ninpo not to develop his kernel for cm7 yet.

However, I was just wondering if anyone has tried Ninpo 2.0.5 with cm7 (and if so which nightly version?). Did it work?

I mean, if no one has even tried it how do we know it won't work?

Only asking cos thinking of dumping litening ROM v5.0 for cm7 but want to carry on using ninpo kernel (because of oc/uv and cifs and BLN;))

Edit: just love the lockscreen options on cm7
[Galaxy S II Original Android Development] AvRS:
I'm no troll....I've been reading and I'm sorry but your post just came across as disrespectful that's all, I've had many a laugh at the majority of the banter that goes on in this thread but it's clear where people have been taking the piss, you just weren't so clear so just ignore me then but would say to brush up a little on your presentation then there'd be no confusion :o :p
[Galaxy S II Original Android Development] jlevy73:
AFAIK, no one has tried 2.05 with cm7. So I guess there's only way to find out :)

My guess, and this is just a guess, is that it won't boot. You could try replacing the boot.img from the CM7 rom with the one Hacre is using.

BLN is not currently supported by CM7 and from a recent post by Codeworx, doesn't look they will be because of battery drain issues. He mentioned trying a more elegant solution (inclusion into the framework) but it's low on their to-do list.
[Galaxy S II Original Android Development] mynamesteve:
CM7 and Samsung roms work very differently, it wont work as is properly or even boot at all.

Widget locker is your lock screen Savior. well worth the money.
[Galaxy S II Original Android Development] krulgrizzla:
does this works with the new XXKH3 rom?
[Galaxy S II Original Android Development] mynamesteve:
Some feedback for your adventurous self,

Your post would have been better constructed like thus:

This kernel works/doesn't work (pick one) on KH3.

FEEDBACK is or far more use than questions.

You wanna know, experiment yourself or search takes half hour tops.
[Galaxy S II Original Android Development] krulgrizzla:
ok try it..it works in XXKH3
[Galaxy S II Original Android Development] pulser_g2:
Won't boot on CM7.

CM7 devs (antinm and codeworkx) requested not to make this for CM7 until stable, as the regular idiots in that thread would have YET another variable they aren't dealing with properly...

They have enough trouble with idiots to begin with. If there were custom CM7 kernels, it would be a nightmare to bug track. So we respect their wishes :)

If you are clever and wanted to do it for personal use, you should be able to compile this kernel with a suitable initramfs, but don't share it :)
[Galaxy S II Original Android Development] goldbergx:
From what I understand, the kernel only accepts values in steps of 25mV whatever SetCPU sets. Tried 775?

Time in State only shows you frequencies, not voltages if I remember correctly?
[Galaxy S II Original Android Development] tolis626:
Hacre,a little,tiny,teeny question.

While waiting patiently for you and Netarchy to give us GPU control stuff,I realised you never answered when I asked about how will we control GPU frequencies and voltages.So,how?Will you guys write a standalone app or something?
[Galaxy S II Original Android Development] tolis626:
Completely out of curiosity and wanting to prove you an idiot,I just checked 200MHz running at 750mV.As much as I hate to admit it,you are right,my phone crashed immediately.So I am sorry if I insulted you. :)

However,it might not be because of 750mV,but something else that crashes when you select below 800mV.I can't know,will check with lastkmsg.
[Galaxy S II Original Android Development] Nebucatnetzer:
Sry I still don't get it. Even a normal pc screen has a a refresh rate of 60 Hertz maybe 75 but that's rare. 120 if you have a 3D screen. So even there is a limitation not? Forgive me if I miss a obvious point but I would like to understand the things properly.
[Galaxy S II Original Android Development] tolis626:
There are many things to take into account here.First and foremost,you are comparing a cheap,low energy,small display to a big,energy consuming display that can cost up to more that our phones.
[Galaxy S II Original Android Development] Nebucatnetzer:
But if it has a hardware limited refresh rate of 60 Hertz then even the price wouldn't change this fact.

I would say the price comes from the size, reaction time, colour authenticity, thickness, 3D stuff, etc.
[Galaxy S II Original Android Development] bclark:
Yup, tested quite a while ago with insanity and I couldn't even get a boot screen although some did. If it really is as simple as recompiling with different intramifs then I think its time to learn how to compile a kernel.

On the topic of releasing the 60fps cap: isn't it not even worth it due to the size of the screen and a persons inability to distinguish the difference, along with the intense strain to the hardware components?
[Galaxy S II Original Android Development] tolis626:
What I told you was only one thing to take into account.It ain't the most important,but it's the easiest to explain and understand.I don't exactly know the techy stuff this involves,but my uncle,an expert-it's his job,explained to me once some 2 or 3 years ago.I am sorry but I don't remember now. :)
[Galaxy S II Original Android Development] tolis626:
Well,seriously speaking it ain't worth by a long shot.I never meant that such a kernel(with the "cap" lifted) should be made for everyday use.That would be plain stupid and I hope no one asking for it meant it to be for daily use.It's a try-once kind of thing.The only thing it'd be worth would be giving us the opportunity to shut every other phone's user's mouths,especially Tegra 2 users.But anyway,I'd prefer a quality kernel like Ninphetamine anyday. :)
[Galaxy S II Original Android Development] JAG131990:
What a selfish prick
[Galaxy S II Original Android Development] inkyadrian:
It crashed at the same mvolts on my other SGS2. I asked a question about the setCPU mv settings on another thread; what is the Incremential scale of setCPU mvolts? I did not get a response yet.