[Galaxy S II Original Android Development] Hacre:
HALLO THAR me again. Ninphetamine 1.0 didn't go so well did it? I thought I'd lost my mojo. Some even had me wondering if my prior good works had been the freaky sort of flukes that would have been better spent on guessing lottery numbers than giving you lot new toys. I was down. Broken. Beaten. So much so even my sarcasm had left me, opting to close the thread after the billionth stupid question rather than scythe down the scum that floats atop our gene pool with my usual aplomb.

Down but not out the Ninphetamine team went back to basics and discovered this mysterious random reboot was still present. Many WTFs were uttered. So we seriously downgraded our building tools. Still random reboots. Many WTFs were screamed from the rooftops. Then someone "helpfully" mentioned that older Samsung ROMs were also plagued with a random reboot issue that disappeared some time a few ROM releases later. The same person "helpfully" mentioned that the Samsung kernel source was released around those early releases. I say "helpfully" instead of helpfully because it would have been HELPFUL if it'd been mentioned before hours had been spent reversing patches and performing voodoo ritual chants to try and get to the bottom of the problem. I looked back on Samsung's source website and discovered a recent KERNEL UPDATE and patched it into my source. BOOM, random reboots gone.

WELL THANKS A ****ING BUNCH SAMSUNG. I am so pleased it didn't occur to you to update your available sources after you'd discovered it was a kernel problem causing the reboots. Full marks for it completely slipping your collective mind that, while being fully aware people would be producing their own works for this phone (I know you're aware because of how you didn't lock the bootloader), it wouldn't be a GOOD ****ING IDEA to perhaps at least release a patch for the problem if not the updated source. MONTHS it's taken you, literally MONTHS.

I hate you. However, I also love you. At least you -did- release an update (albeit being later than the pope to a contraception conference) and your cockup only served to reignite the fire that is my rage.

So, Ninphetamine 2.0. It's true that war drives innovation and the war on the random reboot certainly had us trying many different things and making various discoveries. Many of those have been applied to the now working base so everything I promised for Ninphetamine 1.0 is there and then some.

EVEN FASTAR!!!11. Yep. Get a good tail wind at your back, throw a dice on a double six three times in a row and you can even break 4000 on Quadrant at stock speeds WITHOUT ANY CHEATING. I know Quadrant is largely a meaningless test, results rendered utterly useless by all the retards that mount everything to a ramdisk before running so they can masturbate furiously at HIGHER NUMBERS firmly and unironically of the belief that it increases their self worth and reputation. Performance is smoother however and responsiveness improved as well over Ninphetamine 1.0. Remember if you're the sort that does care about Quadrant scores, given that Android has the attention span of an eight year old child after consuming enough sugar to kill a diabetic in seconds, Quadrant needs 2-3 runs before the OS realises it might be a good idea to make sure the app has the CPU and memory resources it actually wants. Or you can flip the governor to the Performance.

FASTURER THAN EVAN FASTAR!!!!!111oneeleven. Speaking of people that like to furiously masturbate over high yet meaningless numbers, the overclocking feature is back with a few bug fixes for good measure. As before it's capped at 1600MHz. We haven't added the GPU clocking yet as it's important to ensure that the current feature set is stable before adding even more. The voltage control interface is also included. Remember, if you're the type of idiot that understands nothing of overclocking or undervolting or how CPUs work in general, don't come crying to me when you try and run 1.6GHz at 800mV and find you have problems. The issue isn't mine, it's yours. Take it up with your parents who are also your aunt and uncle, remember if you can to thank them for providing further evidence that inbreeding is bad and produces morons that aren't capable of functioning in society. Thanks.

Base still at 2.6.35.11. After patching in Samsung's fixes to their own incompetence I'm pleased to note that we're able to stay at least at 2.6.35.11 base, thus keeping many important fixes, improvements and performance boosts from the main kernel team headed up by God himself Mr Linus Torvalds. You thought I was God? While flattered no, I am merely a disciple ready and willing to deputise for when he's too busy.

So download it, run it, break it. Remember, asking me things covered in my initial posts will anger the Android Gods and at best will result in your public ridicule at worst will result in a few plagues upon your dark dingy basement where you no doubt reside.

If you're going to report problems I want more than "HLAP MAI PHONE BROKED". Try and recreate the issue while running logging (instructions on how will follow in a FAQ post). If you're overclocking/undervolting or any combination of the two, stop it and see if your problem persists.

Don't report every single issue you have to me either. It's possibly a kernel issue if overall stability is affected, if you get a full reboot from the boot logo (NOT the boot animation, dropping to boot animation means Android crashed, not the kernel) or if you get a full lockup. If you find that in life in general people tend to stop talking when you're around, or they don't quite seem sincere when laughing at your jokes, it's probably you, not me, that's at fault because you're a bit of an idiot.

Now, there's been a couple of testers that have suffered a rare random reboot. I have a theory on this but to prove it, I need a wider audience. There will be a downloadable kernel that is SOLELY for anyone that suffers a random reboot under NORMAL (normal clock, normal voltage, no tegrak, using OnDemand governor) circumstances.

Download links will be in the download post. If you ask where download links are, I'll give you a very custom one of your own and who KNOWS what that kernel might do. You've been warned.

TO REITERATE - READ THIS

All new downloads should download the release version. Only people who get an unexplainable reboot while running under stock 1.2GHz (or less) conditions at normal voltage with no OC software installed should download and install the workaround version.

Thanks

Unlimited thanks to my wife for her boundless patience with my Android obsessions.

Many thanks to my genius partner netarchy.

Many thanks to my harem of testers, pulser, designgears, Ante0, mattgirv, Obihoernchen, Kullt, Veyka, Lenny, yoda and Rawat.