[KERNEL] Ninphetamine-2.1.3 - Now with 100% less Samsungyness

Hacre schrieb:

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 FUCKING 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 FUCKING 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.

Zum Vergrößern anklicken....

Hacre schrieb:

Ninphetamine version 2.1.3 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.1.2 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.1.1 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.1.0 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.5 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.4 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.2 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.2 Workaround Edition
As stated earlier, only download this version if you have issues with the release version.
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.1 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.1 Workaround Edition
As stated earlier, only download this version if you have issues with the release version.
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.0 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Ninphetamine version 2.0.0 Workaround Edition
As stated earlier, only download this version if you have issues with the release version.
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Zum Vergrößern anklicken....

Hacre schrieb:

2.1.3 Release Edition

• Re-enabled kallsyms (thanks supercurio for the heads up).
• Fixed initramfs to provide support to custom ROMs that use startup scripts in /system/etc/init.d (thanks designgears).

2.1.2 Release Edition

• Added a workaround for some ROMs bootlooping after a wipe of /data due to incorrect permissions on the new subdirectories created. Appears to be a ROM bug, perhaps KH3 related, would be handy if ROM developers could look for a fix.

2.1.1 Release Edition

• Added FUSE and CUSE support.

2.1.0 Release Edition

• Update to Samsung XXKG5 source (Update2)
• Added GPU clock control interface (currently has no GUI)
• Minimum CPU voltage now properly clamped at 800mV
• Misc tweaks and fixes, see github commit log to cfs-exp for full details

2.0.5 Release Edition

• Improvements to BLN battery usage.
• Changes made to touchpanel sensitivity when the phone is charging to resolve issues for people using certain screen protectors that stop registering user input when on charge.

2.0.4 Release Edition

• BLN support added.
• RAM console (/proc/last_kmsg) added.
• Workaround edition deprecated.

2.0.2 Release/Workaround Edition

• More VPN features added.
• JHash updated to version 3.

2.0.1 Release/Workaround Edition

• CIFS support added.

2.0.0 Release Edition

• Samsung's latest source update applied to base.
• Kernel base updated to 2.6.35.11.
• Overclock up to 1.6GHz.
• Voltage control via SetCPU or Voltage Control from 800mV up to 1500mV.
• BFQv2-r1 IO scheduler added and set as default.
• Optimised EXT4 mount options.
• Various other performance related tweaks.

2.0.0 Workaround Edition
As above, but with some patches applied to workaround errata inherent to some Cortex A8/A9 processors.

Zum Vergrößern anklicken....

Hacre schrieb:

• How do I change my GPU clock speed?

Either wait for GUI support to appear in the form of an addition to SetCPU or a standalone GUI, or if you're confident with a terminal:

Code:

adb shell
cat /sys/devices/virtual/misc/gpu_clock_control/gpu_control # To view current settings
echo 267 300 > /sys/devices/virtual/misc/gpu_clock_control/gpu_control # Sets GPU clock from 160/267 to 267/300

We currently have a 450MHz maximum clock and 10MHz minimum clock. The presence of these values does not necessarily mean your GPU can run at these speeds, like all overclocking your results can and most likely will vary. Do not come crying in this thread because you broke your phone or set fire to your desk or gave yourself third degree burns. Actually, do, I enjoy a good laugh.
​

• Hey any update on you guys getting FEATURE done or CHANGE I'd like?

Given that I'm away on honeymoon in two weeks and we're expecting Samsung to release sources actually used with 2.3.4 Any Day Now (tm) any new features are unlikely to appear until September, unless you're part of my IRC Testing Crew and we start testing new features ready for the release of the next major version. So stop asking.​

• Uncle Hacre, I had a nasty crash and my phone rebooted, I want to help you debug this, what can I do?

Code:

adb shell cat /proc/last_kmsg > lastkmsg.log

Then zip up the lastkmsg.log file and attach it to your post informing me of the issue.
​

• I simply must have every possible second of battery life available, other kernel devs are disabling adb and logcat to make this happen can you do this please battery life is very important to me as I often spend days in Outer Mongolia with no access to power and that extra thirty minutes of battery life could be the difference between me tweeting I've lost my toes to frostbite or not!

Debugging features in the kernel are already disabled. Have I disabled adb/logcat? No. Will I? No. I'm at 50 hours uptime on my phone with just under 40% battery remaining. I see no battery issue. Whether the life can be slightly improved or not, removing a key debugging function from the land of custom ROMs is an incredibly stupid idea. What if you flash a custom ROM and there's an issue and the ROM developer needs debugging information to fix it? What if you install an app that has a problem and you cannot give any feedback to the app developer? Are you prepared to flash a kernel that has adb enabled any time you have an issue? For the minor gains in battery life it isn't worth it.
​

• There's a ClockworkMod Recovery with a higher version number than the one you're providing surely bigger numbers means better why aren't you providing it?!?!

I'll update CWM Recovery as and when a version appears that provides a feature or fixes a bug that we're afflicted with.
​

• WAAAAHHHHHHH QQ I have to wait ONE ENTIRE SECOND for my phone to wake up from standby!!!111oneeleven. This is totally unacceptable and it is ruining my life!!!

Of course it takes a second to wake up from deep sleep. Everything has been shut off, the CPU placed in low power mode and the entire OS placed into suspend. I don't know about you but it takes me far longer than one second to be fully coherent and responsive when I wake up in the morning and I've only got one brain to worry about, the SGS2 has two of them! Shut the whining up about this complete and utter non issue.
​

• What ROMs will this work with?

The kernel has been tested with VillainROM 2.0 and 2.1. It should in theory work with any ROM based on a stock SGS2 ROM. However if your ROM developer requires a custom initramfs for features you may encounter problems.
​

• How do I overclock my CPU?

Use SetCPU, ensure you have the latest version.
​

• How do I change the voltage of my CPU?

Use SetCPU, ensure you have the latest version.
​

• I cannot use adb install anymore.

We're aware of this and are working on a solution for the next release. In the meantime adb push the apk to the phone and install using a file browser.
​

• My phone was running fine for hours but I just now had a random reboot. What should I do?

Learn to read. Download and install the Workaround Edition.
​

• I have Tegrak installed while using your kernel, does that make me an idiot?

Yes.
​

Zum Vergrößern anklicken....

• Funktioniert dieser Kernel mit CM?

1. SetCPU installieren: SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011 - xda-developers
2. StabilityTest installieren: https://market.android.com/details?id=com.into.stability
3. Governor auf Performance stellen.
4. Im Voltage Tab von SetCPU die Voltage von 1200MHz runter setzen.
5. Apply klicken.
6. Die Max Frequenz kurz ändern und dann wieder zurücksetzen auf 1200MHz. Also einfach kurz den Max Schieberegler bewegen, damit die Voltage übernommen wird!
7. Nun StabilityTest starten und den Classic Test für mindestens 15min ausführen.
8. Bleibt alles soweit stabil kann man versuchen die Spannung weiter runter zu setzen. Dann wieder Schritt 4-7 wiederholen.
9. Rebootet oder freezed das SGS2 einfach die Voltage wieder etwas hoch setzen. Dann wieder Schritt 4-7 wiederholen.
10. Hat man einen stabilen Wert gefunden setzt man nun die Max Frequenz 1 Schritt runter und arbeitet alle Schritte ab 4. wieder ab nur, dass man diesmal natürlich die Voltage für die veränderte Frequenz einstellt.
11. Am Schluss sollte man jede einzelne Frequenz nochmals länger durchtesten.
12. Wenn ihr ausgiebig getestet habt macht den Haken bei Set on Boot rein.

• 1100mV reboot
• 1125mV reboot
• 1150mV stable - 15 min - 3 Tage stable

• 1000mV reboot
• 1025mV reboot
• 1050mV stable - 15 min - 3 Tage stable

• 925 mV freeze
• 950 mV stable - 15min - 3 Tage stable

• 800 mV freeze
• 825 mV stable - 15min - 3 Tage stable

• 800 mV stable - 15min - 3 Tage stable

2.0.0 Workaround Edition
As above, but with some patches applied to workaround errata inherent to some Cortex A8/A9 processors.

Zum Vergrößern anklicken....

netguru schrieb:

Hi, ist logo root und inkl. schnellem deep standby?
Über cwm flash a kernel machbar?
Gesendet mit der Android-Hilfe.de-App

Zum Vergrößern anklicken....

netguru schrieb:

Hi, ist logo root und inkl. schnellem deep standby?
Über cwm flash a kernel machbar?
Gesendet mit der Android-Hilfe.de-App

Zum Vergrößern anklicken....

zyfloid schrieb:

Hallo,

wenn ich diesen Kernel wie CWM installiere würd ich folgendes machen:


"Danach gehen wir auf install zip from sdcard , choose zip from sdcard und navigieren zu [da wo ichs auf die interne abgelegt habe]. Bestätigen und auf Yes - Install Navigieren , nun Flasht den Kernel. "

Erst mal: so wirds gemacht oder? Ich hab bisher immer nur den Kernel über Odin geflasht...

Das bringt mich auch gleich zur zweiten Frage:

Wenn ich über Odin z.B. nen CF-Root flashe, dann bringt der mir CWM, ROOT und BB aufs handy.

Steckt im Ninphetamine-2.0.0-Das auch drin? oder ist das nur ne Teilmenge ohne CWM etc und geht davon aus, das das schon existiert? Denn wenn da CWM drin wäre und ich das mittels CWM flashen würde, dann würde das doch nicht gehen... Ich will's nur verstehen!

Ich bitte um Nachsicht.

Zum Vergrößern anklicken....

Ninphetamine version 2.0.0 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.

Zum Vergrößern anklicken....

eybee1970 schrieb:

Du hast grundsätzlich 3 Möglichkeiten den Kernel zu flashen:

1. über ODIN (od. Heimdal), dann wird auch CWM mit installiert ==> s. 1. DL-Link unten
2. über CWM als update.zip (entweder aus der App heraus oder im Recovery-Menü) ==> s. 2. DL-Link unten
3. als zImage über die Funktion 'Flash a Kernel' in der CWM-App --> dadür musst du aber das zImage aus der update.zip oder der TAR-File extracten (mit WinRAR o.ä. Prog)

Zum Vergrößern anklicken....