WARNING THIS COULD AND VERY WELL MIGHT HARM YOUR PHONE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING THIS COULD AND VERY WELL MIGHT HARM YOUR PHONE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING THIS COULD AND VERY WELL MIGHT HARM YOUR PHONE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
You voted I have decided that what I will post here on XDA is a zip that contains the files needed to compile this on your own. This a development forum after all. I will also give you some simple instructions explaining how you can accomplish compiling this kernel.
I am including pershoots files for the 8mb ram hack along with the audio hack. I have modified the boardmahimahi.c and the acpuclock-scorpion.c to achieve a very minor overclocking. That being said, this can still harm your phone.
I have over-volted the processor to 1.325v. I have overclocked to 1.117ghz. If you were to over-volt the processor to 1.35v. That would be a 4% increase over max stock voltage. That 4% increase would result in roughly 8% more heat to your chip. I have halved the voltage but the heat increase is not linear so that doesn't mean it is half the heat. It sure isn't any more than 8% though. Anyway I take no responsibility for you harming your phone and that is why you must compile the kernel. I am only supplying knowledge.
Follow these instructions to set up your build enviroment: Cyanogen Wiki
What you need to do here is follow the instructions for compiling the kernel up until you get to step 5 of installing repo. Instead use this: repo init -u git://github.com/cyanogen/android.git -b eclair.
Now follow the steps for preparing the kernel but before you do steps 6-8 here you need to cd to the directory you initialized the repo in, cd to /kernel/arch/arm/mach-msm and copy all but the q6audio.c file into here. Then open the q6 folder and copy the q6audio.c file into here. Then complete steps 6 7 8. You can play with some kernel settings but if you don't know don't do it.
If you want to enable some compiler optimizations you can do this before compiling:
export KCFLAGS="-O2"
then when you give the make command:
make KCFLAGS=-O2 ARCH=arm CROSS_COMPILE=$CCOMPILER
Once it finishes (30min-2hr) find your zImage. Then you can go and look in
kernel/drivers/net/wireless/bcm4329 and in there you will find your .ko file to get your wifi working.
Download Source Files Here!
I will answer no other questions about this. If you need more help you should not do this. But there is always Google and a wealth of info awaits you if you use it!
CREDITS: Pershoot, Cyanogen, Kmobs (even though you hate it, you still inspired it with mention of the "Jesus Kernel"), intersectRaven, PsyQ, and many many others, I am sure!
Nice posting this, but you should post some disclaimers in BIG red writing.
Harry454 said:
Nice posting this, but you should post some disclaimers in BIG red writing.
Click to expand...
Click to collapse
Done and done! I forgot about that.
Hopefully we still have bootloader unlocked phones in the future...
+1. This is stupid, you SHOULD NOT SHARE STUFF LIKE THIS WITH XDA. 90% of the users here WILL NOT READ YOUR BIG RED WARNING LETTERS.
What so wrong about this info kmobs ?,
Your kernel also overclocked from beginning and we still have unlocked bootloader.
I posted source files and compiling how to. All of this information is available on this site already. All I did was put it in one place for the people willing to take the time to set up and compile it for themselves. I did not post a zImage or an update.zip for the masses to flash. What I posted is what anyone with 1/2 a brain and a Google search bar can figure out on their own.
This pushes the phone far beyond its safe limits, not to mention the max voltage is actually set to 1.4v which is extremely reckless.
rheza02 said:
What so wrong about this info kmobs ?,
Your kernel also overclocked from beginning and we still have unlocked bootloader.
Click to expand...
Click to collapse
I completely agree plus very few will figure out how to do this. My only concern is that someone will post a zip file of this but oh well, I think XDA should benefit from stuff like this. This is development at it's finest.
jlevy73 said:
I completely agree plus very few will figure out how to do this. My only concern is that someone will post a zip file of this but oh well, I think XDA should benefit from stuff like this. This is development at it's finest.
Click to expand...
Click to collapse
If the information was already out there, why is this thread needed? All this does is simplify the processes of basically running too much electricity through your phone. My mod didn't affect voltages at all, which is why it wouldn't cause any long lasting damage.
If someone posts a zip file, thats probably going to be the end of bootloader unlocked phones.
Yeah, there is nothing like a bunch of people cooking their phones to really advance the development around here.
Google is going to love dealing with those support calls.
1.The max voltage is set to 1.4v however no frequency on the table uses that voltage.
2. Anyone who takes the time to compile the kernel could do this themselves anyway.
3. There was already a post on the forum explaining over-clocking. Almost to the letter I think, and after that was posted, the OC-UV-kernel was released.
Tell you what, I will fix the boardmahimahi down to 1.325 since the freq table doesn't go higher anyway.
Knowledge should be shared not horded.
Gr8gorilla said:
1.The max voltage is set to 1.4v however no frequency on the table uses that voltage.
2. Anyone who takes the time to compile the kernel could do this themselves anyway.
3. There was already a post on the forum explaining over-clocking. Almost to the letter I think, and after that was posted, the OC-UV-kernel was released.
Tell you what, I will fix the boardmahimahi down to 1.325 since the freq table doesn't go higher anyway.
Knowledge should be shared not horded.
Click to expand...
Click to collapse
There is a REASON that the phone is locked to 1.3v instead of 1.4, 1.325, or even 1.301. The processor is rated for 1.3v. Thats it. No higher. I know the OC-UV thread was posted you know.. since I'm the one that made it.
Like you said, there is already a thread explaining the overclocking, so someone that wants to do it already has the resources. All this does it make it easier for someone without knowledge of the dangers to take it and release it. Do you really want that?
So only your kernel acceptable and the other not ?
persiansown said:
There is a REASON that the phone is locked to 1.3v instead of 1.4, 1.325, or even 1.301. The processor is rated for 1.3v. Thats it. No higher. I know the OC-UV thread was posted you know.. since I'm the one that made it.
Like you said, there is already a thread explaining the overclocking, so someone that wants to do it already has the resources. All this does it make it easier for someone without knowledge of the dangers to take it and release it. Do you really want that?
Click to expand...
Click to collapse
Persian I have a ton of respect for all that you have done here at XDA and helping others out. But honestly if someone is that stupid to install this without knowing something bad might happen, we got bigger problems than this post. But sharing is caring so while I get your point, I appreciate the OP putting up the information.
And on that note, a ZIP file is already in existence. I will not say where but I just stumbled across it (it's not on XDA).
ANDROID IS OPEN SOURCE! GOOGLE WANTED THE PHONE UNLOCKED!
Do you really believe that they did not foresee this? The whole point of open source is the sharing of Knowledge. It is not up to me or anyone else to decide who should and should not have access to knowledge (Steve Jobs?) If you don't like open source go hang out on an iPhone forum!
Yes this could harm someone's phone, yes some idiot will fry his processor with this knowledge. I don't see anybody complaining about the guy who posted a radio image and instructions on how to flash it. I have seen a few bricked Nexus One's from radio flashes though. At least with this Kernel they will see some instability long before anything drastic happens. Not so with a screwed up radio flash.
Now tell me I am wrong and why!
Gr8gorilla said:
ANDROID IS OPEN SOURCE! GOOGLE WANTED THE PHONE UNLOCKED!
Do you really believe that they did not foresee this? The whole point of open source is the sharing of Knowledge. It is not up to me or anyone else to decide who should and should not have access to knowledge (Steve Jobs?) If you don't like open source go hang out on an iPhone forum!
Yes this could harm someone's phone, yes some idiot will fry his processor with this knowledge. I don't see anybody complaining about the guy who posted a radio image and instructions on how to flash it. I have seen a few bricked Nexus One's from radio flashes though. At least with this Kernel they will see some instability long before anything drastic happens. Not so with a screwed up radio flash.
Now tell me I am wrong and why!
Click to expand...
Click to collapse
Google wanted it unlocked, but in the future will HTC and other hardware manufactures comply? No. They are the ones that are going to be handling repairs from your reckless overclocking
Gr8gorilla said:
ANDROID IS OPEN SOURCE! GOOGLE WANTED THE PHONE UNLOCKED!
Do you really believe that they did not foresee this? The whole point of open source is the sharing of Knowledge. It is not up to me or anyone else to decide who should and should not have access to knowledge (Steve Jobs?) If you don't like open source go hang out on an iPhone forum!
Yes this could harm someone's phone, yes some idiot will fry his processor with this knowledge. I don't see anybody complaining about the guy who posted a radio image and instructions on how to flash it. I have seen a few bricked Nexus One's from radio flashes though. At least with this Kernel they will see some instability long before anything drastic happens. Not so with a screwed up radio flash.
Now tell me I am wrong and why!
Click to expand...
Click to collapse
Google wanted the phone unlocked yes, but why do you think the regulator was put into place?
If google didn't care about people messing with voltages, they would have never implemented the regulator. Transistors and resistors DIE with extra voltage. Once they are gone, there's no bringing them back. I'm all for the advancement of the platform, but how exactly does this do that?
I understand why everyone is up in arms about this but this wont stop future phones from having an unlocked bootloader. That's why there's a big ass warning stating that your warranty is invalid should you unlock it. Anyone who compiles this kernel and flashes it knows they are taking a huge chance of frying their phones so in my opinion, that's on them. Personally I didn't spend close to 600 bucks just to turn my n1 into a pretty paperweight, but should someone not heed people who know what they are talking abouts advice, its on them.
All this will do is let the people who have no idea what they are doing, mess with something that we shouldn't mess with, or if we must mess with it, it should be a couple of people so that the masses don't get ahold of this and fry all their phones. 90 percent of ROMS here have the same warning label and I can guarantee that people probably don't even read them they just skip down to the instructions or to the download link. This is worse because it will actually fry their phones. If you are reading this do NOT attempt to do this. It will **** UP your phone.
Related
I would like to start learning how to put roms together. I would like to start with developing a 2.2 rom compiled from galaxy s I900 source. Is there anyone here that can point me in the direction of a good tutorial on how to start? I have been using other peoples work for like a year and a half and would really like to create rather than use. I am a total noob when it comes to developing so any help would be great. thx
Go here;
http://forum.xda-developers.com/forumdisplay.php?f=613
Read a lot before you ask.
Good luck!
You can't develop a rom using only kernel source.
Sent from my SCH-I500 using XDA App
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
yutzyscott said:
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
Click to expand...
Click to collapse
All I have to say is good luck with that.
fallingup said:
All I have to say is good luck with that.
Click to expand...
Click to collapse
In all seriousness do you stay apprised in any way shape or form of android related news our just enjoy smearing the forums with your illinformed ramblings and negativity? Speak of what you know and don't be so eager to dismiss anyone with the fortitude to increase their own knowledge base on an operating system such as this when its these people who we all depend on to better our experience with said operating system. As it is these people for whom google turns to when it comes to ideas on how to better their future stock releases. Thank you for the vote of confidence.
Sent from my SCH-I500 using XDA App
You do realize fallingup has written more android code than your phone can hold?
The reason they seem testy is they(actual developers) have been spending all their free time trying to get Samsungs crappy code to compile, and every couple of hours some one asks for an easy how to guide for porting Froyo.
Spend some time reading the forums. Find out what is already being done, then learn the basics of rom development. THEN, ask intelligent questions on how help develop Froyo for our phones.
Asking for an easy way to cook roms is the equivalent of the kid in the back seat asking "are we there yet" every 30 seconds. If you really want to learn how to cook roms, try a couple easy ones with the kitchen I linked to, then learn how to work on roms without the kitchen. Then work on Froyo. There is no easy way.
I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing. As far as my last post I meant no disrespect to fallingup in fact it was my mistake to quote his post. I actually intended on quoting jt1134 so, to fallingup, I have used your stuff many times and have nothing but respect for what you do. I apologize for the misquote. I in no way think myself to be super genius to the 10th power nor do I believe that I can actually do anything worth while with this code. I'm just bored and want to learn. I'm also an Android addict.
P.S. Thank you for the link. Also you'll notice in my last post now that you know of my misquote, that I am actually 100% behind people like fallingup. I would never knowingly give a verbal bashing like that to him.(god I feel like **** now)
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
I'm tired. I'm generally a nice guy, sorry!
jt1134 said:
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
Click to expand...
Click to collapse
Now I have the right person quoted. Did you even read my post??? Let me repeat a key part so that you can understand and maybe you can stop battering the new guy.
"I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing."
I have admitted to my know nothingness. I simply want to learn. You could respond with something such as Galaxy S 2.2 is not a good place to start the learning process. Or you could have left it alone entirely and just thought that the link posted by "sgtmack" was sufficient enough. After all it did answer the exact question I asked. You might know a lot more about code and code writing than me but you have to admit, "your kind of an arrogant ass!" Now I would like to end this banter by allowing you to respond in whatever way you deem necessary. I myself will give this no further thought as I would like to move on now. That and I believe I have made myself look bad enough now.
As for fallingup and sgtmack, thanks for the hard work and helpful advice.
yutzyscott, do you not realize that jt and dirrk are the ones that got us the voodoo kernel? do you know they are the ones that got the kernel booting in the first place using samsung's ****ty source code? without jt, there would be nothing to build a rom around. wtf do you mean ill-informed when jt probably knows more than most people about developing for this phone? pay some ****ing respect for people that deserve it.
Yeah I do but, when this whole thing started I did not read who the post was by but, rather I just read the post. While I appreciate his work and am actually using it, my pride was hurt and its hard to interpret someones tone on a forum. I was under the impression in the beginning of all this that it would be known that I downloaded the 2.2 ota pushed to the original galaxy s and not the source they have been working with and making leaps and bounds with despite the road blocks. I was interested in learning how to port it (the ota I mean) rather than just sitting on my hands waiting to use anothers work. Chances are that I would never even come close to understanding what I was looking at but, I had to try. Now I'm sorry I asked. I quit...I was wrong, sorry! Leaving it to the experts. I'll go back to helping people with simple basic problems on droidforums.net and continue being an expert on using the real experts work.
This doesn't need to be turned into a flame thread. So here's my advice: join us on irc.freenode.net #samsung-fascinate and ask questions there. learn how to build a kernel, and maybe try to find out how exactly to port roms from other devices. Its a tough business, especially when we don't even get working kernel source from the manufacturer.
There are a ton of people that are working on the galaxy s phones, trying to get AOSP and the like on them. These phones are quite different than any other android phones, just with the way that the hardware / partitions are, so there is a lot to work through and document. Once one of the SGS phones is running aosp, im sure the others wont be too far behind. I wouldn't bother porting another crappy samsung rom, cause it will still have a lot of the crap that we are trying to get rid of by running aosp.
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
jt1134 said:
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
Click to expand...
Click to collapse
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats always a good excuse
this was an entertaining thread lol.. misunderstandings is one of the biggest downfalls of online conversation.
Not meant to be offensive. Just funny. http://www.geekologie.com/2010/10/a_day_in_the_life_of_internet.php
Sent from my SCH-I500 using XDA App
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Download Links
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.
Changelog
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.
FAQ
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 or Voltage Control, ensure you have the latest version.
How do I change the voltage of my CPU?
Use SetCPU or Voltage Control, 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.
Super Happy Fun Time
Should you arrive in this thread bereft of the basic intelligence required to remember to breathe in and out as needed and you ask questions/make posts that clearly demonstrate this fact, I'll be sure to give you the attention you deserve in this very post.
geistteufel said:
I don't see bfq scheduler in set cpu, is it normal?
Click to expand...
Click to collapse
Yes it's normal. Your IQ isn't. What on Earth possesses you to even open SetCPU if you're looking for schedulers in there? Do you also complain to car manufacturers when you can't find your spare tyre in the engine bay or you find that a motorbike has no ashtray?
saintxseiya said:
Hi,
do i have to set setcpu in some way or is the kernel all doing by itself?
Cheers.
Click to expand...
Click to collapse
If only I had taken the time to write a FAQ post, on the first page of this thread that would answer this question...
golf60 said:
wipe cache and dalvik cache before flashing....
Click to expand...
Click to collapse
I'd really like it if people with a shoe size rivalling IQ would refrain from giving advice to users of our kernel. Advising to wipe cache/dalvik before changing kernel is akin to advising checking tyre pressures because the gearbox just fell out.
Kollegah said:
Is this kernel compatible with cm7?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Or in other words: "Hi, I'm too lazy to read threads or use the search function." This has been addressed in several posts in this very thread.
Cygnuss said:
So what does this version do VS the 2.0.0?
Click to expand...
Click to collapse
Wow, I really wish I'd taken the time to put a changelog on the first page after the download links. If I had, then surely no one would need to ask me what's changed in new releases. Thank you so much for highlighting my failing!
Logi_Ca1 said:
Is anyone else running 200Mhz at 475mv? Works fine on my phone, passes stability test 2.11 as well. Or maybe there's a softcap for the minimum value?
Click to expand...
Click to collapse
It would seem I live in a parallel universe, one where I'm sure I write things down yet they do not appear. This can be the only explanation for you not seeing "Voltage control via SetCPU from 800mV up to 1500mV" in the THIRD POST ON THE FIRST PAGE. Well there's that explanation, or there's you being a moron. Hmmm...
varenathan said:
Dear all,
How to install Ninphetamine version 2.0.1 Release Edition using ODIN? I have downloaded it "TAR file for ODIN" here : http://forum.xda-developers.com/showthread.php?t=1179814
, n extract it and found this zImage. Please tell me how to use this zImage?
My kernel version at the moment : I9100XXKG1 but my PDA/PHONE/CSC = KG2.
Thanks n sorry if this question has been replied before but i couldn't find it anywhere.
Click to expand...
Click to collapse
varenathan said:
But i found it's not a .tar file, it's zImage. Is this the same? sorry for nob question..
Click to expand...
Click to collapse
varenathan said:
Thanks mate! Just realized it's a .tar or .zip in notification, but when i open it in windows, it shows only ninphetamine-2.0.1-release.
So, another Question. Is it possible to flash back my last Kernel version if i flash ninphetamine (just in case, something wrong with it)? How to do that?
Click to expand...
Click to collapse
varenathan said:
thanks mate! Usefull information indeed!
EDIT :
How to take out the zImage and where to find it from the last ROM which i've just flashed before i flash ninphetamine?
Click to expand...
Click to collapse
varenathan said:
I have I9100XXKG1.
Okay, thanks again. I thought i should move the zImage from my sdCard and then place on my PC and then i can flash it to a new Kernel.
So blessed today, found these people who help me
Click to expand...
Click to collapse
varenathan said:
hahaha.. be my guest. I am just trying to be a good user for my phone
Click to expand...
Click to collapse
varenathan said:
Which i have already made, but i am not sure for the kernel version, as i always get the new version from my ROM Developer it's included, n shouldn't flash it seperately
Click to expand...
Click to collapse
AND THE CURRENT THREAD RESIDENT INEPT BUNGLING RETARD AWARD GOES TO:...you. How the hell did you even manage to find this thread? In fact how did you even manage to survive long enough to use a computer? Or am I looking at this from the wrong perspective, should I be thrilled that a Chimpanzee has managed to procure a PC and an SGS2 and already managed to flash a custom ROM to it? You sir are the reason new scissors are labelled with "Warning: contains sharp objects". Answers to all of the questions you've asked are freely available throughout the SGS2 forum and in the form of guides all over the internet. So not only are you bereft of the basic intelligence required to figure out which way is up, you're also lacking the kind of effort that's required to carry out the most simple tasks like "find a useful collection of words" and "read a useful collection of words". Shame on you.
-Zork- said:
Have a question about this kerel, I got 1 % drop per hour in standby ( sleeping 8 hour and wake from 100% go down to 93%). Is it normal?
Click to expand...
Click to collapse
No it's not normal. This is outrageous. Thank you for submitting this bug report so that myself and netarchy can get to work right away on the part of the kernel that is supposed to suspend the space-time continuum when your phone goes into standby so that it uses no power whatsoever. You see we weren't sure whether to suspend time or have it invent hydrogen fuel cells and circumvent the battery during Deep Sleep so we opted for the far easier suspension of space and time. I'm awfully sorry that our experiment failed and we'll now look into kernel code that can combine matter and anti-matter for a low power sustainable reaction so that you lose no precious battery life at all while the phone is in standby. Or you could do us all a favour, including yourself and turn your phone off and never ever touch it again. That way the number of people you communicate with will be curtailed, your phone will never lose power and you'll never need to sully one of my threads again. You have all the intellectual creativity of a box of hair, a command of language worse than that of a deaf mute and an ineptitude so offensive it cannot be summed up in a single word, so I'll try three: You're a moron.
Warrimonk said:
Can't seem to get 1.6ghz stable at all, even at 1.5mV. Running lightening 4.1 and this kernel. any tips?
Click to expand...
Click to collapse
Yes. Kill yourself. Asking such a question means you're clearly beyond help, have no clue about overclocking and don't deserve such a nice phone. Free up some oxygen and resources for the rest of us please, thanks.
CrimsonAxe said:
This might sound dumb, I'm using Litening rom 4.1 with Ninphetamine 2.0.2
What app should i use to underclock my voltage? i tried Voltage Control and after i've got my settings done, i try to check the current battery voltage it's still at 4004mV? Does that mean the application is not working?
Click to expand...
Click to collapse
Might sound dumb? No no, it IS dumb. 4004mV is how much voltage is remaining in the battery you twatneck. Why are you asking what app you should be using when it is clearly stated ON THE FIRST PAGE OF THE THREAD?. How has it escaped your grasp when editing voltages that are all ~1000mV that over FOUR THOUSAND millivolts might just be something else?? In fact how did the words BATTERY VOLTAGE not clue you in after changing CPU VOLTAGE? You're a (unfortunately) breathing example of never underestimating the lowest level of stupidity. If brains were chocolate bars yours would be labelled "Fun Size".
NeoPhyTe.x360 said:
And do you think that #twiter word in my signature, is a fail? Maybe you don't understand why I put things like this
SARCASTIC MODE ON
I put twiter in a text, but in the hyperlink I'm seeing twitter, oh **** i'm clever!
Click to expand...
Click to collapse
NeoPhyTe.x360 said:
my twitter was deleted months ago, man.
Since Feb, 2011, and Google knows
Click to expand...
Click to collapse
NeoPhyTe.x360 said:
And you are a moderator?
Maybe you have to understand it first, because I don't think that people in usa are much clever.
Click to expand...
Click to collapse
This guy calls himself a developer. Yes your "#twiter" link is a fail because a: it isn't spelled properly and b: it 404s. Why keep it there if it's a dead link? Because you didn't know until it was pointed out to you, that's why. As for "I don't think that people in usa are much clever"....oh the irony. If your kernels run as well as you post I'm sure scattered around the XDA userbase is a smattering of dead or unresponsive SGS2s. Which wouldn't surprise me. Taking a look at your kernel thread it's clear that you've as much clue as a lobotomised Orang-Utan. More steps on your CPU frequencies than there are on the stairway to heaven, you think somehow that 500MHz uses less power than 200MHz, governors included that anyone doing five minutes of research would know they're unstable, you advertise standard kernel features as unique features in your kernel (CFQ, CFS, boy those sure are new features!) and to top it all off you've got the cheek to take code from Ninphetamine and then come here and ****post. I've more chance of developing film in direct sunlight than you have of developing anything close to competent and the fact that you have the audacity to consume bandwidth on the internet offends me. If braincells were matchsticks you couldn't light a candle, so kindly return to your thread full of fail and leave us big boys and those of us with IQs higher than room temperature to get on with grown up things, mkay?
NeoPhyTe.x360 said:
I have been living in Chester this spring/summer some months, and maybe I'll go in september, so I hope we could meet, because maybe my braincells can't light a candle, but I know that my fists yes. Coincidences of life...mate
Click to expand...
Click to collapse
Holy **** an actual threat of violence from the internet. Hahahahahaha. At least I think that's what it is. You "know that your fists yes"....I can only assume this is a threat...unless you're chatting me up and want to fist my bottom? I'm not that way inclined mate, sorry.
Tarek82 said:
Try running 1.6ghz under a different rom, I have no problem running 1.6ghz with Cognition S2 using set cpu
Click to expand...
Click to collapse
I'm revoking the other guy's retard award because you've single handedly come into the post and shown us in fewer than 20 words just what being a hap-hazardous retard with an IQ smaller than a bullant's testicle and the sharpness of a dull stick of butter what being a retard is all about.
No no, please, pray tell, how running a different ROM will magically make a CPU run at 1.6GHz when it wouldn't before? This, you cretinous simpleton, is akin to giving a steam roller a paint job and expecting it to pull an extra 100mph as a result. Please promise me that's the last time you ever post on the internet, because if you keep this up you'll dilute the global IQ so much we'll all start eating our shoes.
apache86 said:
I realy appreciate your work but arent you going a little too far with your language and comments? you mentioned your wife at some part of the long story at the first post (who can actually read all this? are you an author as well?). are you also talking to her like this when she doesnt understand somthing? your kids? im definitely not jealous in her
Now come down a little bit with your language and dont help us if you cant do that as a fully grown man (are you a grown man?)
This is the common nature of people, asking dumb questions somethims but on the other hand, do you realy expect them to know as much as you do on changing kernels and messing with them? the fact that you might have no life does not mean you should take it out on others isnt it?
Now come on, tell me what you think about my post, dont spare any word of it!
Click to expand...
Click to collapse
Oh yippee the language police arrived. I'm so pleased you found the opportunity to take time away from your perfect life your perfect wife your perfect children and your perfect job situated high within that glorious and shining ivory tower of yours to descend upon us normal folk to educate us about our terrible language and vulgar manner of insulting those whom we only see as morose shambling idiots who cannot even manage to search a thread, whereas you see them as gleaming examples of humanity, bereft of love, attention and experience.
Well, as you're now down here on planet Earth, you globulating and sickeningly sweet preacher of goodwill, may I first introduce you to the word hypocrisy. Often rife among your dogooding kind, it means that you sit on high quaffing down pints of innocence and regurgitating it upon us regular folk as some kind of moral education, while still sneering like a ****ing 1930s cartoon villain. If you could get the shine of your halo out of your eyes for a few seconds and deign to look upon the unwashed masses, you'd recognise that dishing out lessons in manners doesn't often mix well if you throw in a dash of "insult their lack of any life worth living" or "let's have a pop at his wife".
You sir, are a **** but not only that, you're the worst type of ****. I'd rather deal with 20 of EACH of every idiot that precedes you in this posted collection of horrors than one of you, you vile and pathetic excuse for a human being. How dare you feign to come into my thread and chastise my use of language when you can't even ****ing spell let alone string a sentence together. You're not only offensive to the morals you're offensive to the eyes, you write down pure eye cancer and I implore you to stop.
I have never and will never excuse anyone's lack of common sense. There's a difference between not knowing and not even having the wherewithall to help your sodding self. I berate the latter and assist the former, whereas you don't flap your ****in caviar chompers unless there's some moral crusade to embark upon. How about you be honest with yourself and realise that you only arm yourself for combat and mount upon your trusty forum steed to put right what mere mortals like me have wronged, to give yourself grace and relief from the sorry, putrid and langquidly depressing state your own life is in. How about you spend even half the effort you spent ejaculating that illiterate and berating post into my thread, on sorting your own miserable existence out and then maybe we'd both be a lot happier. Your insignificant blip of an existence wouldn't be quite so worthless to you and maybe, just maybe, you'd keep your hypocrisy laden lectures to yourself which would in turn make me very happy indeed.
****, LOLed so hard I woke up my kids!....thank you!
Nice one, will try soon. Btw i love your epic stories in your OP
oh jesus i'm dying after reading the whole story in op ...rotfl
edit: just to say something useful, i'm going to try it!
rocketpaul said:
Nice one, will try soon. Btw i love your epic stories in your OP
Click to expand...
Click to collapse
You should start with 7
Swyped from my Galaxy S II using Tapatalk
Artius89 said:
oh jesus i'm dying after reading the whole story in op ...rotfl
edit: just to say something useful, i'm going to try it!
Click to expand...
Click to collapse
If you die, you cannot enjoy the even better entertainment next time round... So try and survive
@ninpo, did you remind them that anyone trying to use it with Tegrak is subject to capital punishment?
Any plans for CM7?
pulser_g2 said:
@ninpo, did you remind them that anyone trying to use it with Tegrak is subject to capital punishment?
Click to expand...
Click to collapse
Yes, read the thread, don't make me make you my first example in post #5, you know I will.
Cool intro, thank you guys for all the time and effort you put into this. Downloading now and testing on villain 2.1.
Cheers!
saifbechan said:
Cool intro, thank you guys for all the time and effort you put into this. Downloading now and testing on villain 2.1.
Cheers!
Click to expand...
Click to collapse
No problem.
This kernel will make your phone turn into a blowjobs and pudding machine.
In all srsness.
Its great, use it, love it <3
Your a funny dude you must be Scottish surely?
Sent from my GT-I9100 using XDA App
Nice work, I'm looking forward to this kernel as it evolves. Will be testing it out tomorrow.
I'm especially looking forward to GPU frequency and voltage control, as I'm running my GPU at 750mV instead of the default 1000 and the phone runs noticeably cooler when playing games, and thus logically would mean superior battery life while gaming. This would be a killer-feature in future releases, for me at least.
It would also be interesting to know if we'll eventually get "internal voltage" control some day. My deduction is that that would be the voltage for most things other than the CPU and the GPU like for example the hardware decoder/encoder as being the most significant part of the SoC, if it truly is things like the decoder, then it would boost battery life for video playback by some amount.
dibdab214 said:
Your a funny dude you must be Scottish surely?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
"British by birth, English by the grace of God".
AndreiLux said:
Nice work, I'm looking forward to this kernel as it evolves. Will be testing it out tomorrow.
I'm especially looking forward to GPU frequency and voltage control, as I'm running my GPU at 750mV instead of the default 1000 and the phone runs noticeably cooler when playing games, and thus logically would mean superior battery life while gaming. This would be a killer-feature in future releases, for me at least.
It would also be interesting to know if we'll eventually get "internal voltage" control some day. My deduction is that that would be the voltage for most things other than the CPU and the GPU like for example the hardware decoder/encoder as being the most significant part of the SoC, if it truly is things like the decoder, then it would boost battery life for video playback by some amount.
Click to expand...
Click to collapse
The next logical step is to work on voltage/clock control for the GPU. We'll then look at the internal voltage and what it affects. Not all Samsung's code is easy to follow.
Hacre said:
Yes, read the thread, don't make me make you my first example in post #5, you know I will.
Click to expand...
Click to collapse
Ahhh... Wasn't there a minute ago Place bets on when you need an extension of post 5 due to 40k character limit? ;0
>>>> 22Jan2012: linboothkvc v1.0 source released in my linboothkvc thread. It works successfully on Omap3 and Omap4 based devices including NookTab. And with minimal changes/love can work with any rooted arm based linux device <<<<
>>>> 17Jan2012: Kernel module SUCCEEDS on NookTab to reboot into NIRVANA - NO NEED to BREAK the default SECURE BOOT CHAIN and NOTE THAT EVEN THIS CAN WORK ON ANY ROOTED DEVICE and not just NT, with minimal love so ENJOY <<<<
>>>> 16Jan2012: My kernel module based path (linboothkvc) to running custom kernels and roms is almost done, except for a __small part__ to get it running on NT now - IF ONLY PEOPLE HAD WAITED ...., we could have reaped the potential benefit in future, Why not !!!! why not ....WHY NOT !?!?. NOTE that it can allow one to run custom kernel/roms WITH OUT MODIFYING ANY CRITICAL PARTITIONS provided one sets it up properly/appropriately. Source for beta version available in my linboothkvc thread, for the interested developers/experimenters for now ... <<<<
>>>> I may not respond to the posts on this thread currently, because I am trying to get a alternate option called linboothkvc using kernel modules up and running (which will occupy my free time), which AVOIDS the NEED for this flaw in the first place for most of the people out there (i.e Custom ROMS with different kernels). However over the weekends, I will go thro all the posts on this thread <<<<
>>>> 14Jan2012: Initial pre-alpha version of kernel module path based source code uploaded to my linboothkvc thread for those still interested to experiment
http://forum.xda-developers.com/showthread.php?t=1427610
<<<<
Hi All,
If you have been following my posts over the last few days
NOTE: To people frustrated with UART requirement - I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then do note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all. AND THAT By holding off now, we can _potentially_(Risk is always there) reap the benifit with next years NEXT GEN Nook Tab+ or what ever they call it.
a) I have implemented 2ndihkvc, which follows the same fundamental concept as 2nd-init, but achieves it in a simpler way (Needed because some of the calls used in original 2nd-init doesn't work on NookTab, or have unnecessary dependencies (in this given context, otherwise they are good in them selves) which can be avoided with my simpler method)
b) I have provided the NOP Bypass method of running a modified Ramdisk and also 90% a modified kernel, provided UART access is there.
c) There is still the power of linux KERNEL MODULES to EXPLOIT. (Haven't had time on that yet).
If you ask me, this should cover all category of people. Be it people who want to run custom Roms, or people who want to experiment with Kernel and or other low level stuff for the fun of it.
There is a 4th method which will allow one to achieve (b) above with out requiring UART access or even uSD (potentially . If one reads between the lines from all my posts till date, the answer is hidden in there. Only that I haven't spelt it out directly or in the face. The reason is because It is a fundament flaw (rather there are potentially two at two different levels - one relatively simple and one relatively bit more involved - One I know for sure, another I have to dig bit more) in the way things are done currently in the secure boot chain on this device as well as potentially other devices with same or similar SOC (and or different SOC but with similar boot chain s/w components.
SHOULD WE BE WASTING i.e providing a solution which uses it, when there is already 2ndihkvc and NOP Bypass over UART and also the Linux KERNLE MODULE ROUTE to cater to most peoples needs.
Because if we do, then even the Device manufacturers and their partners will come to know about it and can easily fix it in their Newer/NextGen devices. While if we withhold it for now, we may be able to get access to it on their Next generation Devices with hopefully Arm A15 core or .... (NOTE: Depending on the boot sequence ROOT access may or may not be required for this).
The reason I am asking now is because, few people are asking my help on certain things and the reality is I know that the concept for which they want my inputs/guidance, can be applied at a more fundamental level here (or even at the same level), but that I have not ventured into it because of my delimma above.
NOTE: People who wanted my inputs/guidance wrt uSD, you all know who you are, I know the flaw to achieve what you want to achieve, but it is more powerful than what you all are currently thinking of doing/ ristricting yourselves to (You all have one input/... in there wrt devices . Unless let me think thro further and see if something can be done differently, with out exposing the flaw I have in mind to help you achieve what you want, otherwise i.e if there is nothing else I can come up with, and in turn if you people experiment further and are able to come up with the solution on your own, I would suggest that hold off on it for few days, think thro all the implications keeping what I have mentioned in this thread, and then take a call one way or the other.
Please provide your thoughts on this after thinking thro the options already available on NookTab (root access, kernel modules, UART UBoot access and inturn 2ndihkvc and NOP Bypass or equivalents)
Based on all the feedbacks as well as bit more thinking from my side, I will take a call on this.
Forum moderators I know this is the development portion of the forum, but I wanted feedback from Developers also that is the reason why I have posted here. But beyond that I leave it to you, whether you want this to continue here or move it out.
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
cfoesch said:
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
Click to expand...
Click to collapse
Hi
I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all.
By holding off now, we can potentially reap the benifit with next years Nook Tab+ or what ever they call it.
Im not a Developer but I've got a few questions. NOP requires to open up your device, so I think probably 95% won't open their device for ICS and I think since the device had a dual core CPU we should get ICS roms. Now my actual question how does your 2init work or how do you install it on our device? But great work so far keep on.
Sent from my SGH-T989
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
PM me about the flaw, I'll see if we should have it outed yet or not (sorry guys, but if it's a decent exploitable flaw and we have other methods, I'm pretty sure I'm with hkvc on it.)
xdahgary said:
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
Click to expand...
Click to collapse
Not worried for 2 reasons,
a) It doesn't bother if my name comes or not. I am exploring just for the fun of exploring.
AND MORE IMPORTANTLY,
b) Actually I have already revealed the flaw in my NOP Bypass thread, indirectly, if only, one reads carefully all my lines as well as between them. Only that I have just replaced one or two of the steps with a different steps thats all for now.
If someone else find the same flaw, he will realise the same, if he reads my posts once again with his new knowledge.
What an awesome idea, we can have a root for the Nook Tablet+ or whatever else in a years time!
...
So, um... what do I do now with my Nook Tablet? It's a piece of garbage now, I guess, so, I'll just return it since it's still within the Holiday return period? I suppose I'll just have to wait for the Nook Tablet+ to have a custom ROM running on my Nook... ("But you can UART hack it!" ... *sigh* I've already explain that that is not sufficient. The UART hack is a stop gap, and should only be stopped at if that is the absolute only option available.)
And I mean no disrespect to xIndirect, but why should he be the lone gatekeeper of what exploits and hacks are out there for the Nook Tablet? I would rather see this exploit before making a decision as well, but I don't think it fair that someone should have privileged access to the exploit. Either release it to everyone or DON'T SAY ANYTHING IN THE FIRST PLACE.
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Indirect said:
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Click to expand...
Click to collapse
If you buy a plot of land and the seller has accidentally left seeds there and isn't coming back for them, do you grow a garden on your current plot of land, or do you decide not to plant them and hope that the next time you buy a plot of land they might forget some seeds again?
I would rather tend the garden I own than hope for a better plot of land with seeds I may never have.
Cheers!
-M
XDA member since 2007
Sorry if my post is offtopic, I just want to help with development.
My SE Xperia x10 came worh a locked bootloader and devs figured out how to make a bootable recovery (xrecovery) based on CWM, may be with an adaptation for the NT we can get the world of custom roms, even with locked bootloader this crappy phone got cuatom kernels by bypassing the bootloader, hope this give little ligth to you guys the real Developers.
If this post is garbage mods please delate it.
Sent from my BNTV250 using xda premium
Hello, I beleive if there is a software way to get ICS + maybe overclocking it should be tried first as this IS what most people are waiting for. That's the big dream they got. If someone knows how to implement that, then please by all means do so ..
P.S. you said so much where to look for the flaw in your posts that if I was a programmer from B&N I'd know where to look like everybody else. Assuming they are not complete morons they can already figure it out too. Can they plug the hole or not? Is it oversight or permanent design flaw ? We'll see. Best way to keep a secret is to " keep it secret " , ie not talk about it at all. Especially if soft mod ICS, hw acceleration and overclocking already available.
Sent from my LG-P500 using Much Love
First of all hkvc +1 for your efforts.
I voted yes, the NT developers can read between the lines in your posts as well.
Whats life without risks once in a while
Hi All,
I understand very well that even BN devs will be looking and potentially can figure out and fix it. That is the risk, but at one level I don't mind taking the risk and see if it works out to my/our advantage (i.e the bug being still open in a new device (From BN or any other Vendor)) or disadvantage(the bug is either way fixed).
Also the flaw can affect ANY DEVICE (Not just NOOK TAB) using similar secure boot chain not just NookTab, that is also one reason why I am bit wary of releasing the info or a implementation which uses it just like that.
I will share my finding with few people on the forum/outside in few days time so that even If I loose interest in this, there will be few people with the required knowledge (i.e if they haven't already figured out on their own by then (and released something or not ...)).
Also I haven't taken a final call on this yet. I am in a delima, so getting all your opinions also before I decide.
Time permitting I will also attack/explore the KERNEL MODULE PATH in a few days time, so that people don't have to depend on this flaw in the first place, but use the wonderful world of Linux Kernel Modules to achieve what they want.
LexS007 said:
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Click to expand...
Click to collapse
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
absolutely YES, we r all xdaers, right hehehe. Thanks all devs especially hkvc for the efforts
hkvc said:
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
Click to expand...
Click to collapse
It's very good. Thanks!!!
First off, not a dev but read religiously.
2nd, release it if the people who would take advantage of it agree. The rest of us say "great,woohoo!" But I must admit, I can't take advantage of it. But I certainly don't want to make a hardware uart to boot custom roms.
That being said, if its more complicated to install with a different method, that's fine. As long as it doesn't include a soldering iron.
But if it were easier to make a custom rom, or open up more capabilities of the kernal or whathaveyou, well that would attract more developers to make roms, etc. and so on and so forth.
Btw. Yes, exploit may exist if outedin a later tablet, but you found this one.... I have faith the next flaw will be found in the next one too.
A bird in the hand is worth two in the bush.
Posted from my B&N Nook Tablet... rooted of course!
jotekman said:
A bird in the hand is worth two in the bush.
Click to expand...
Click to collapse
I would say this summarizes everything I want to say on the topic.
Hello I'm a newb!
I'm sorry, but this is the unfortunate state I find myself in.
When I first found this site, what I was expecting to find was a ICS for my phone. I could not have guessed what I would learn here. I had no idea I had a counter in my phone to worry about when installing open sourced roms? Next after much more reading I am to learn the source code Google releases is not complete, and uses binary drivers? Now I am to learn about CIQ, and my phone is spying on me? Wow!
Before I say anything else I want to express my thanks to this community. This has been such a resource I had no idea that it would be when I started. Thank you!
Now on to my question that after learning about all of that I don't seem to have a clear answer to. What I wanted when I first considered getting an Android phone, was to build from source, and run my own rom. I still want this, even more so since I learned about CIQ.
1. Due to the counter on my phone
2. I am to understand multiple images that make the phone work (boot, firmware, system)
3. The binary drivers.
Is this at all a reasonable goal?
Are there more flash images that I haven't read about yet?
Would having a direct from Google rom even be desirable?
I own a stock SGH-I777, I have done nothing to it yet.
Lastly about this site:
Is there anything you think I should read about on the forums?
Any language I should know, as in what does hellraiser imply/mean?
Any Android experience you think might benefit a could be developer?
Counter can be reset and avoided all together.
Sorry I don't know much about AOSP building, but your better off starting with compiling CM and learn from there unless you are really experienced in coding.
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source. Ty for reminding me.
NEME5I5 said:
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source.
Click to expand...
Click to collapse
AT&T Galaxy S2 SGH-I777 has never had CIQ.
LiLChris06 said:
AT&T Galaxy S2 SGH-I777 has never had CIQ.
Click to expand...
Click to collapse
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
NEME5I5 said:
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
Click to expand...
Click to collapse
No it was just some phones, I think the skyrocket had it at some point.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Ok, so I rooted my first cell phone. It would seem heimdall latest has a bug that will brick your phone. (I'm on Mac OS Lion) I used the 1.3.1 instead, and it worked fine.
I saw many more sites, and this was quite easy. The way they showed it was very complex. Since I'm new at this should I wait to try out a ICS rom till after Samsung releases their source code, and the devs have had a chance to get it stable? How complete is the open source version of ICS? There was a note on the fsf.org page that linked me over here that some of the parts were still binary. Is it still true?
I think long term I want to get away from the official releases.
Well, you came this far, might as well flash an ICS rom now. If the leaks are any indication of status, the Samsung release will be pretty stable but the included kernel is problematic because it can cause hardbricking. Besides, you want to get away from stock, and all of the big roms released thus far are pretty darn stable; I don't know anything about binary parts or any of the coding, but plenty of people have no problem running CM or AOKP. Even the Samsung-based roms all look AOSP-like nowadays because they use Apex or Nova (not many devs like Touchwiz anymore). So take your pick, they're all good roms and most look like AOSP to some extent, with a few (mainly CM and AOKP) striving for pure AOSP.
Make sure to read and follow this guide carefully for flashing stuff, and have fun!
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Prother, by no mean to offense you, but seriously, if you don't know those fundamental technical terms, I strongly suggest you to hold off what you about to do and spend more time reading.
Let me go off and do a search the post for you, where you can get used to those terms.
Hang tight, prother.
Pirateghost said:
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
So I will. To be honest I don't see the connection between the new jargon, and development I learn in school. There is definately much to learn here. I was expecting this to be like Zaurus development from back when I was active, it's very clear to me that this is a very different beast.
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
votinh said:
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
Click to expand...
Click to collapse
Thank you friend. I may not have my own rom at the end of summer, but I should be on my way to understanding what would be needed for one.
Well the terms I wanted are not present on that list, most of that I was familiar with. To be honest, some of it I have not seen before as well. What is hellraiser, and some of the other xda developed jargon? I do have a tab open to that part of the forums, I just hadn't made it over there yet. I started on the forums for my device, then Android OS, and lastly general. Is there any other place I should pay special attention to that would help me?
Phalanx7621 said:
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok? I'm not sure I understand, is there something you don't like about the aokp rom that doesn't work very well?
I want off of the carrier provided images based on personal conviction. Google's development practices smack of cathedral, as do all of the 3rd party companies. In a sense they are abusing the spirit of free software by using a signed kernel to impede (if not actually prevent) our right to modify hardware we own. Any normal user of the software provided by the community (bazaar) can only help the cause.
I plan to share what I personally learn with close friends who live in my area. The more people we liberate, the better for everyone else. I simply applaud the work done here.
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
karate104 said:
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
Click to expand...
Click to collapse
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
From a relative noob:
Follow the directions in the " [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!! " thread. Then pick a rom you want to try and follow the CWM directions ... after that , find a ROM you like. If you don't want to void your warranty, wait for your carrier to provide the closest thing to what you want ... but, I'm happy with my flashed ICS ROM.
NEME5I5 said:
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
Click to expand...
Click to collapse
Just like everyone else has said. Read read read. Search for answers for your questions before you ask on forums. U will be fine as long as u can read and follow simple directions. Good luck to u. If u haven't flashed a rom yet I would recommend aokp. Awesome rom.
Sent from my SGH-I777 using XDA
just a odd idea I thought I would share
I wonder if its possible to patch a kernel on load using safestrap
I am wondering if maby we can hex-patch the DVFS table at execute to at least gain some overclocking
I read the kexec thread but the consensus there is that development is stalled waiting for a breakthrough
thoughts :fingers-crossed:
Legitsu said:
just a odd idea I thought I would share
I wonder if its possible to patch a kernel on load using safestrap
I am wondering if maby we can hex-patch the DVFS table at execute to at least gain some overclocking
I read the kexec thread but the consensus there is that development is stalled waiting for a breakthrough
thoughts :fingers-crossed:
Click to expand...
Click to collapse
You can overclock via module sure, hex patch prob not needed.
Surge1223 said:
You can overclock via module sure, hex patch prob not needed.
Click to expand...
Click to collapse
hrmmm.... you talking about patching the dvfs kernel module or writing a custom module ...
if so I am surprised nobody has done that yet ..
is hex-patching from safestrap at all feasible ... it would grant you the 'keys' to all manner of "doors"
I used to fiddle with it on my cheap mk808 tv stick before we had kernel sources
I am surprised nobody has used kmodule's as a "attack vector" people seem to be chipping away and the Mountain that is kexec instead of just focusing on patching the issues we have with the stock kernel .. . a few years ago somebody was doing hex patches to implement kernel changes on the first generation of rockchip powered "tv sticks" the same logic should apply here
then again maby I have just been out of the game for way to long ....
*continues pondering*
Legitsu said:
hrmmm.... you talking about patching the dvfs kernel module or writing a custom module ...
if so I am surprised nobody has done that yet ..
is hex-patching from safestrap at all feasible ... it would grant you the 'keys' to all manner of door if it was
I used to fiddle with it on my cheap mk808 tv stick before we had kernel sources
I am surprised nobody has used kmodule's as a "attack vector" people seem to be chipping away and the Mountain that is kexec instead of just focusing on patching the issues we have with the stock kernel .. . a few years ago somebody was doing hex patches to implement kernel changes on the first generation of rockchip powered "tv sticks" the same logic should apply here
Click to expand...
Click to collapse
I have dabbled with this, using a custom module based on the 8660 overclock module I found source for somewhere. The reason kexec is so much more desired then fixing the current kernel is because patching the current kernel might give us more io schedulers, overclock, custom governors etc, but at the end of the day all that crap isn't worth much on the poor excuse for android ui known as touchwiz.
Idk about you but I can tell you I for sure would not want to post a thread on overclocking or modifying cpu via modules in this day and age of 'the entitled xda user'. Maybe that's why you don't see any threads.
You bring up a good point about how people don't understand the various uses kernel modules can provide including but not limited to being attack vectors (though to some degree this is being done with kexec).
Surge1223 said:
I have dabbled with this, using a custom module based on the 8660 overclock module I found source for somewhere. The reason kexec is so much more desired then fixing the current kernel is because patching the current kernel might give us more io schedulers, overclock, custom governors etc, but at the end of the day all that crap isn't worth much on the poor excuse for android ui known as touchwiz.
Idk about you but I can tell you I for sure would not want to post a thread on overclocking or modifying cpu via modules in this day and age of 'the entitled xda user'. Maybe that's why you don't see any threads.
You bring up a good point about how people don't understand the various uses kernel modules can provide including but not limited to being attack vectors (though to some degree this is being done with kexec).
Click to expand...
Click to collapse
ill be the first one to admit I haven't keept up on this stuff simply because the effort started outweighing the gain
it just seems to me that people are chasing clouds ... with kexec the possibility of getting it working is basically nill due to lack of debugging information so why not attack something you can debug such as a kernel module hell in theory it should be possible to add io schedulers and governors via a module hell with a properly 'crafted' module we may even get kexec(kgraft?) as a result if you could create a exploit you could use to the proper effect ..
I agree that touchwizz is utter poo and should be stabbed with white hot knives and buried under 12ft of cement but the phrase "if life gives you lemons ... make lemonade" rings to mind ...
I am sure somebody will give me the usual speech about "if you are so smart do it your self" but sometimes people just need to step back and look at it another way .. + I am fighting insomnia and am on my third shot of jack ...
wow did I really write all that jesus ... no more jack for me at 12 am...
Legitsu said:
wow did I really write all that jesus ... no more jack for me at 12 am...
Click to expand...
Click to collapse
Lol. At least your question is a good topic of debate. Most questions and posts in our forum are boring to me but this isn't, so there's that I guess.
Surge1223 said:
Lol. At least your question is a good topic of debate. Most questions and posts in our forum are boring to me but this isn't, so there's that I guess.
Click to expand...
Click to collapse
realistically you probably could't alter to much but adding overclocking a variety of minor tweaks could be done in hex
on a personal note I would be content with figuring out how to get some overclocking/undervolting done
Legitsu said:
realistically you probably could't alter to much but adding overclocking a variety of minor tweaks could be done in hex
on a personal note I would be content with figuring out how to get some overclocking/undervolting done
Click to expand...
Click to collapse
When you reply to me, you realize you are actually continuing your thoughts and not actually replying to me right?
Surge1223 said:
When you reply to me, you realize you are actually continuing your thoughts and not actually replying to me right?
Click to expand...
Click to collapse
Lol I am just rambling feel free to ignore me lol
board software here is a bit odd
*deleted tired*