yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Nathalex27:
Undervolting is not harmfull.

Your system crashing could be but not so much. It's overclocking and overvolting where the harm is done.

Heat is your enemy!

I'm a pro overclocker when it comes to pc's but this is only my 2nd overclocked phone. I think It pretty much are same things to keep in mind. Watch your heat closely when overclocking and don't rush stress tests. 3 minutes is not stable...
[Galaxy S II Original Android Development] Ghazkul:
I was refering to my phone reaching 1% battery level left and still not shutting down after 15 min with screen on. it had nothing to do with Hanniballs post.
[Galaxy S II Original Android Development] Hacre:
I didn't say it did have anything to do with Hanniball's post? I asked you what "danger" you were referring to. You. Not him.

The SGS2 shuts itself down when the battery no longer provides sufficient power for keeping the phone running.
[Galaxy S II Original Android Development] αкαѕнα:
OMG.... the first post was awesome... i LOVE YOU Hacre
[Galaxy S II Original Android Development] carlos67:
Deleted.......
[Galaxy S II Original Android Development] Testraindrop:
It is Kernel!

With an .... e ...:eek::rolleyes:
[Galaxy S II Original Android Development] pulser_g2:
Indeed, any "stock" device needs to cope with the removal of power at almost any time.

To be intrinsically safe, in terms of coping with (not being damaged) by realistic power failure circumstances, the device should not corrupt itself beyond non-root repair at any time.

Imagine if you are on stock and run out of power, or the battery fell out (after you lose the rear cover and use an elastic band to hold it in (true story about some non-root users I use - they move the band to access the part of the screen they can't reach :D) - without root you can't easily reflash and wipe etc...

A phone like this should cope with removal of power at any time when not doing a firmware update (ie. when it's plugged in via USB). If the device were able to "die" during regular use if power supply is lost, it wouldn't be that reliable a device...

So realistically, you can (but shouldn't try) pull out the battery and not suffer corruption - the system partition isn't written to in normal use. And likewise, if you corrupt your SD or user data partition somehow, the factory reset system exists...

But you ain't likely to do much damage from my experience in designing systems to survive end-user inability and stupidity - I have to consider things like cleaners pulling out power leads to servers to plug in their vacuums... :p Hence journaled filesystems...

It's the same with the phone - EXT4 should be fine :)
[Galaxy S II Original Android Development] Willie_Heckerslyke:
lol all the way thru this thread at his replies....gets my vote as the most comical mod on XDA.... :D

(BTW....thanks for all your work on this Hacre ;) )
[Galaxy S II Original Android Development] Major_Sarcasm:
I find storing all my overclocked devices in the fridge is a remarkably effective way of keeping them stable. On my SGS2, I've achieved eleventy million mhz using this method... at 799mv.

Condensation is an issue, so I keep them all in sealed plastic bags.
[Galaxy S II Original Android Development] xan:
Kernel is so good that there is nothing to talk about...

Why say OMG hacre you rooxx for 1024th time?

Break it and some serious reports will be posted :D

By then.. just chit chat and have fun.
[Galaxy S II Original Android Development] tltester:
I'm not sure if this is already discussed, but here is a solution to adb install / adb uninstall problem (that's a really really worse for developers, because eclipse installs apps through this):

Edit your /system/bin/pm and /system/bin/am files and put #!/system/bin/sh to first line, that's it...
[Galaxy S II Original Android Development] Hacre:
Because this should be said, at least once daily. It's like the old days when the serfs prayed to the sun gods for good weather during crop cycles. You offer worship to the kernel gods Hacre and netarchy to ensure smooth running, plentiful uptime and future prosperity (updates).

:facepalm: why on earth isn't this the case already...well done good sir.
[Galaxy S II Original Android Development] xan:
I've diffrent approach, involving LN2 and copper tubes. I've cut from my AC and led to holes in backplate. Condensation is a bi(**@, but I keep it isolated with mounting foam.

tvelvty million mhz at 798mV.

Sorry.

Let this post be my prayer and sacrifice, kernel godz.
[Galaxy S II Original Android Development] carlos67:
This kernel is sooooo good that Litepro has now added it into his Litening V4.1 ROM.

I wonder what goodies Ninpo has up his sleeve for us in the next update? Not that we need one.
[Galaxy S II Original Android Development] JAG131990:
He is referring to the damage that these batteries will take if fully depleted. we are not talking about the phone turning off that is a safety feature fo protect the battery, rather he is asking whether or not this kernal will allow the phone to switch off at a safe time before the battery level is too low and damage is done.

Note: when the phone switches itself off this is not because there isn't sufficient power to run it is because you don't want to deplete the battery completely for it's longevity sake (damage)
[Galaxy S II Original Android Development] xan:
I've heard that microwave and brain desolator, there are traces on github already.
[Galaxy S II Original Android Development] Major_Sarcasm:
No apology necessary. My way is cheaper, quicker and more convenient. Also, most homes have fridges.
[Galaxy S II Original Android Development] knightnz:
Here's another possibly useful bluetooth A2DP fix thread in relation to poor A2DP quality resulting from a fixed bitpool size;

http://xdaforums.com/showthread.php?t=708685&page=10

Looks like the issue is fixed in current Gingerbread AOSP, and hence in CM7, but the Samsung kernel still uses a fixed bitpool resulting in poorer quality A2DP audio.

Any chance of implementing in Ninphetamine for us bluetooth-audio plebs?
[Galaxy S II Original Android Development] stoney73:
I have informed the relevant authorities regarding your post.

Shame on you. Putting your sgs2 in a jiffybag. How can it breathe?
[Galaxy S II Original Android Development] pulser_g2:
What about liquid nitrogen?

Something most homes should have but don't, for some stupid reason apparently linked to health and safety...
[Galaxy S II Original Android Development] Hacre:
Unfortunately because most of the developers on these forums are ****ing useless at keeping their git repositories up to date, there's nothing in that thread that points to kernel changes that we can incorporate. A lot of the changes involved also require changes at the ROM level to use the BlueZ bluetooth libs instead of the proprietary ones, IF the Samsung ROMs are even capable of that.
[Galaxy S II Original Android Development] pulser_g2:
I have a modified lib file to increase bitpool. It needed no kernel change, but I am uncertain if anyone properly established any benefits proven to not be the placebo effect.

If you have a way to test, or some good objective ears, I will send you two files... One called "A" and one called "B". You then test with both stock file, and the two provides ones, and give feedback.

I won't say what is done to the files, other than that it won't adversely affect your phone to the best of my knowledge, and that it only touches the issue at hand.

I'll then look for open ended feedback..

If interested, make a thread in general and someone pm me a link. I'll just hijack the first post when needed. This will be for tomorrow though...

Can anyone interested organise themselves as above please and make one thread, and subscribe to it etc...
[Galaxy S II Original Android Development] JF-GINO:
I have experimented on both modded & unmodded lib on my car stereo.

It makes a BIG difference.

Without a larger bitpool, two bad things happen

1) The highs tend to sound 'fuzzy' and sometimes crystalize.

2) Higher bitrate mp3s will break up as if there is a buffer problem.

I have a 3000watt component comp system with 24 speakers and its tuned flat - as I also produce music I need it that way for reference.

I am currently using a modded liba2dp.so file from an old firmware build.

Its started to give me problems on newer builds for some reason tho.

Im thinking that the bitpool needs to be increased even more.

New thread created and PM sent.

http://xdaforums.com/showthread.php?p=16022400#post16022400
[Galaxy S II Original Android Development] xan:
Go for it -> blind tests are sexy
[Galaxy S II Original Android Development] Hacre:
Lmfao just lmfao at having such equipment then piping music to it through ****ing bluetooth.
[Galaxy S II Original Android Development] knightnz:
It does seem rather counterproductive. I would imagine with that many speakers the audio quality would become largely irrelevant due to the huge amount of bass present overpowering the other frequencies. I prefer quality to kilowatts.

If both devices support negotiation MPEG4/AAC protocols and don't enforce any filtering/compression then there's no reason the audio _shouldn't_ be really good. If the implementation isn't great then that's going to be a problem though. Regardless, a CD is going to sound better.

It can also help to tweak the /etc/bluetooth/audio.conf file as has been done with Cognition to improve profile support and prevent audio dropouts by forcing "Master" connection.
[Galaxy S II Original Android Development] CaspaTheGhost:
We get idiots around here???... Naa, dont believe it... You're having me on Hacre...

Now if there was a post, say at #5, that ridiculed all the idiotic posts... Hmmm... I wonder...
[Galaxy S II Original Android Development] Hacre:
What a fantastic idea!
[Galaxy S II Original Android Development] Vulpix:
I notice there was no mention of any governors in the first 2 posts, so I'm assume there is no smartass or interactive governors in this kernel?
[Galaxy S II Original Android Development] antiochasylum:
Correct.

Ondemand, conservative, performance is all you get.

Sent from my 114 linpack SGS2
[Galaxy S II Original Android Development] ebliss:
ninpo had said that interactive governor doesn't work well. Ondemand works best and you can tweak it further in the advance tab of setcpu.
[Galaxy S II Original Android Development] Vulpix:
Then is there a good SetCPU config where I can get the CPU to scale nicely? Like 800mhz when I'm just at the home screen and only bump up to 1.2 when I'm playing games?
[Galaxy S II Original Android Development] :
Very good battery life. Running stock odexed KG3. 86% left.
[Galaxy S II Original Android Development] Vulpix:
Why is your AOS so low? :(
[Galaxy S II Original Android Development] kenkiller:
Err...because his other things are high?
[Galaxy S II Original Android Development] jlevy73:
Because there is an inverse relationship between screen on/device in use versus AOS%.
[Galaxy S II Original Android Development] JF-GINO:
My system consists of only 2 12inch subs, the rest are all equally balanced 'Component' speakers with crossovers for 4 separate breaks in the frequency scale from 300 Hz to 30 kHz. I assure you, there is no distortion and everything is clear and balanced.

Im not sure what audio container the stream is, but processing is switchable on my receiver from pcm raw to compressed (unknown). BTW all streams are compressed and go thru a colouring filter, even at the DAC.

This is very interesting...

Might seem excessive to some, but its quite impressive & enjoyable.

You wanna know what funnier tho, Ive even seen bluetooth streaming used in clubs and live to air radio broadcasts - its not as bad as you think, just the range is not practical.
[Galaxy S II Original Android Development] Factisnet:
I´m using your kernel with the insane Cognition S2 Rom, unbelievable how fast the Galaxy S2 now is! THANK YOU

Is it possible to ad the BLN mod for backlightnotifications? Waiting hard to get this on my Phone :)

https://github.com/neldar/backlightnotification/tree/master/kernel_patches

http://xdaforums.com/showthread.php?t=813389

again THX for you work :)
[Galaxy S II Original Android Development] pulser_g2:
I'll bite... Yes I have personally used bluetooth audio streaming at events when I used to help out with A/V :)

Sure, we are talking fairly short distances, but I quite like it for monitor headphones, as it lets me move around behind the scenes much more :)
[Galaxy S II Original Android Development] isotoper:
Hello Guys,

Silly question, but very important for me :

Does a kernel influences also the phone's cellular transmitting strength or behavior ?

Thanks!!
[Galaxy S II Original Android Development] pulser_g2:
You better hope ninpo doesn't see this post or it might be off to post 5 :p

The modem does that, the kernel doesn't directly interfere with the radio transmission or reception beyond providing a driver interface.

In short, you shouldn't see any difference
[Galaxy S II Original Android Development] Testraindrop:
Just wanted to share my battery experiences with you...

Everything was going fine for more than 2days, but tonight something drained the battery from 30% to 9% in just 7 hours :(

But I think 2 days and 18 hours and 9% left isn't quite so bad;)
[Galaxy S II Original Android Development] jlevy73:
Actually, it's not a terrible question, maybe post 6 worthy :) Back in the Nexus One days Kmobs had released a series of heavily undervolted kernels. Shortly thereafter, people started complaining that their reception became terrible. So kmobs looked into it further and did a couple of blind studies to find out what's up. Anyway, long store short, the undervolting didn't affect the radio but it did have a negative impact on battery life.
[Galaxy S II Original Android Development] isotoper:
Thanks pulser_g2 :)
[Galaxy S II Original Android Development] luminoso:
I'm getting Segmentation Fault a few seconds after trying do do a cifs mount. I would like to help with more but I have no idea how to get more information.

Am I the only one having this issue?

I am running Ninphetamine version 2.0.2 Release Edition with XXKG3 TOUCH X 3.1 'PERFORMANCE' rom also with XXKG3 Modem
[Galaxy S II Original Android Development] pulser_g2:
adb shell logcat > luminoso-logcat.txt

adb shell kmsg > luminoso-kmsg.txt

Upload both once you have seen this happen.
[Galaxy S II Original Android Development] pulser_g2:
Interesting :)

I think in this case the OP is confusing kernel with modem, but that's actually quite interesting, though I guess if you were to under-volt the radio chip (do-able via kernel I imagine), then you could have issues...
[Galaxy S II Original Android Development] pulser_g2:
Could you use BetterBatteryStats and look for rogue wakelocks perhaps?
[Galaxy S II Original Android Development] luminoso:
It is always happening so it is easy to replicate.

logcat and i dont seam to have kmsg? "/sbin/sh: kmsg: not found"
[Galaxy S II Original Android Development] Testraindrop:
@pulser

Will do when I'm back at home from work, thanks.
[Galaxy S II Original Android Development] pulser_g2:
Sorry it should be

adb shell cat /proc/kmsg > luminoso-kmsg.txt
[Galaxy S II Original Android Development] pulser_g2:
I have edited the link for your logcat out the post, as it has personal details in it. I've got a copy and will take a look at the errors and pass on relevant parts to ninpo :)
[Galaxy S II Original Android Development] guru_floyd:
I have flashed this with Lightning Rom. Can someone please point me to a guide about overclocking. I have setcpu installed and i just selected ondemand 1.2ghz -200Mhz. My battery drains in about 8 hours. Can someone point me to a guide on overclocking. Been trying to search for one for about 2 days. Cant find it.
[Galaxy S II Original Android Development] Testraindrop:
http://tinyurl.com/3hlx79c

And btw... Overclocking wont help you with your battery life...
[Galaxy S II Original Android Development] fbousk:
Any chance to see your work on cm7 or miui? thank for all....;)
[Galaxy S II Original Android Development] Lennyuk:
the CM7 guys have asked that no-one make custom kernels for it until it is stable so ninpo is going to respect that wish, others have not....
[Galaxy S II Original Android Development] Hacre:
Unless you're hopping in and out of airplane mode your phone signal looks like ****, which will push cell standby really high and drain battery.

However, if the kernel ran fine for more than 2 days, it's not the kernel that caused the battery drain. What did you change between now and yesterday?

READ THE THREAD, MORON.
[Galaxy S II Original Android Development] xinfinityoO:
lol.. cracks me up :)
[Galaxy S II Original Android Development] Testraindrop:
I know that the signal is **** :) here at work I'm in a massive concrete building :(

Airplane mode was only active overnight, I don't believe it's the kernels fault either, but I also don't changed anything, but entered airplane mode manually this time and not automatic by JD, so maybe JD messed something up...

Nevermind, the Kernel itself is working great so far for me, looking forward to new features that are on the todo list :)
[Galaxy S II Original Android Development] tltester:
Random reboots

Hi there.

I'm one of those unfortunate "people who get an unexplainable reboot while running under stock 1.2GHz (or less) conditions at normal voltage with no OC" :)

I'm getting one random reboot once in a day averagely...

It's not related to heat / load conditions, as it happens in very different conditions, mostly a few seconds after waking up the phone. I've tried a stress test and heated up this *****'s ass up to 46C for half a hour, and it were stable as stone :) I'm on Lite'ning 4.1 ROM with Ninphetamine-2.0.2. A few minutes ago I flashed the workaround edition on top of previously installed release edition, we'll see how it's going on from here.

However, I'd very like to get some more info to be able to further help with testing and to better understand what's going on:

1. How can I log what's going on before the reboot? Is there some kind of persistent log I can check after rebooting? Is there some dump it's writing on kernel panic? Anything else?

2. What's exactly this workaround edition? What does it means? It's being stated as "As above, but with some patches applied to workaround errata inherent to some Cortex A8/A9 processors". Why this is relevant only for some of us? Does it mean I have some special CPU revision? Hardware fault that needs workaround? Something else?

If there is something else you want me to test, just tell me...

Here is my CPUINFO:

~ # cat /proc/cpuinfo

cat /proc/cpuinfo

Processor : ARMv7 Processor rev 1 (v7l)

processor : 0

BogoMIPS : 1592.52

Features : swp half thumb fastmult vfp edsp neon vfpv3

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x2

CPU part : 0xc09

CPU revision : 1

Hardware : SMDKC210

Revision : 000e

Serial : 304d19a48618ee6e
[Galaxy S II Original Android Development] Ghashul:
My CPU info (apart from serial, of course) are exactly the same, yet I do not experience reboots.
[Galaxy S II Original Android Development] ebliss:
Hi,

previously when I was logging for this kernel, this is what I need to type.

1) Open a command prompt window, connect your device to your computer

2) adb shell (or "C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe" shell for my case), press Enter

3) cat /proc/kmsg > /sdcard/kmsg.log & and press Enter

4) logcat > /sdcard/logcat.log & and press Enter

For 3 and 4, remember to include the "&"

2 logs will be created in your sdcard. You can unplug the cable and it will still log. once reboot, send the logs to ninpo.
[Galaxy S II Original Android Development] AndroAndo:
Thanks so much Hacre. Been using 2.0.1 for about a week with great overclocking and stability. I flashed 2.0.2 yesterday and I would like to say that my idle battery life has increased about 20 fold here and in-use battery life is nearly doubled.

I was blown away this morning that my battery went from 91% to 88% in almost 9 hours. And it took about 12 minutes to charge just now.

Also getting 7100+ Antutu scores with stock rom, this kernel and setCPU at 1600MHz max/min, performance.

I'm running it underclocked at 800MHz max, 200MHz min all day and we'll see how little juice it uses. Thanks again!
[Galaxy S II Original Android Development] tolis626:
Hey Hacre,bored today so started searching around for stuff here in the forums.

I want to ask you two things:

1)Are there any news on GPU stuff?You haven't mentioned anything in days.I know it's in the to-do list,but how near is that to-do with -done-? :p

2)Just wondering,what settings do you use?Clocks and voltages.I ain't asking about lengthy posts will all freqs,just min and max.Out of curiosity,that's all. :)

Other than that,my phone's been too stable over the past days that I have your kernel installed.How can I log its behaviour?Something's wrong.MY phone was NEVER that stable. :( :p :D
[Galaxy S II Original Android Development] zmirburger:
im having some wakelock issues after going to VillainRom2.3 & Ninpo 2.02

upon further checking its actually the dialer >

RILJ

Dialer

15m (900 s)

is it the kernel/rom or something else?
[Galaxy S II Original Android Development] tltester:
Done, thanks a lot!

BTW: What was your reason to debug? Did you have a reboots too?
[Galaxy S II Original Android Development] Nathalex27:
Man I lose 50 / 60% in 8 hours.....couple hours bt music streaming, little youtube, 20 minutes gaming, lots a texting. 24/7 msn and whatsapp. Downloading music.

So I think 2 days would be awesome.

( Switching to 3500mah battery soon )
[Galaxy S II Original Android Development] serch826:
Got this with Ninphetamine-2.0.2

After i´ve flashed this wonderful room got this with Quadrant, i can´t believe, this is amazing.
[Galaxy S II Original Android Development] kwerdenker:
So you're using your phone constantly with many battery taxing things like BT, video streaming, gaming and you probably have quite a lot of screen on time through the texting and now you wonder why you battery sinks faster than the titanic? I so hope it's just my internet sarcasm filter thats broken and you don't really mean it that way...
[Galaxy S II Original Android Development] Bl@ck:
Sorry if this was already answered but i couldn't find anything till now.

I'm not that experienced with the Galaxy S2 rooting process atm, so, till now i was using CF-Root kernel, yesterday i wanted to try this kernel and flashed it via ClockWork Recovery via .zip file (i also cleaned both cache and dalvik cache), but after flashing it i lost Root access on my phone.

So the cases are 2, or i didn't understand a thing and this kernel comes with no root access, or i should have flashed it via CWM app on my phone.

Atm i'm using VillainROM 2.3.

Thanks in advance for any help.
[Galaxy S II Original Android Development] Lennyuk:
If you like this kernel then leave a 5 star rating on this thread, it seems some idiots (I won't name them, but they know who they are, and we know who they are!) have been rating this thread 1 star all day for no reason at all.

It's not cool.
[Galaxy S II Original Android Development] Lennyuk:
if you had cf-root then you flash this kernel (and don't change rom) you should retain root.

You can just flash it via the CWM app though, maybe that made the difference but I don't see how.

Also when you flash a kernel there is no need whatsoever to wipe anything.
[Galaxy S II Original Android Development] kalpik:
Room? O.o

Post 5?
[Galaxy S II Original Android Development] azulgranas:
Hi i'm on stock rom KG3.

If i flash this Kernel, will this offer root for my phone?
[Galaxy S II Original Android Development] Lennyuk:
no this kernel does not root, you will have to flash cf-root kernel then flash this kernel if you want this kernel and root.
[Galaxy S II Original Android Development] serch826:
XXKG3