Related
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.
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
Why was I getting that error? It's gone now I just want to make sure it's answered for everyone else. I was flashing a rom and it was doing that. Do a reboot. Your system wont be there so reboot into botoloader and go back into recovery.
I'm getting the same error when trying to flash and when I reboot I can't get past the htc screen. I'm using the twrp recovery and I have tried resetting a few times.
EDIT**
I tried resetting my phone a couple more times and it finally just worked. I have no clue what causes this.
Original poster is correct, this method works for whatever reason. I tried it twice now.........
Same thing
Trying to flash a kernal. I tried several reboots of bootloader and recovery and no luck. I am going to flash clockwork since I am using team wins recovery and see if that works.
Same exact thing......OP's solution worked......Thank you
Yeah had this error too. I think it happens when you try to flash a different kernel on the stock ROM. After I switched to a different ROM the error went away.
Sent from my PG86100 using Tapatalk
I'm having the same issues, but rebooting isn't helping. TWRP needs to be updated to address this issue. Until then, no ROMs for me.
That error will usually occur with signature verification failures, you need to make sure that signature verification isn't turned on when installing an unsigned rom.
It would make sense if this has to do with permissions, but I have signature verification turned off in the bootloader. Is there somewhere else that signature verification needs to be turned off?
I'm getting this error trying to root the phone using the sticky guide. It happens when I try to flash the superuser file.
what the op said worked for me as well...restarted and everything worked fine
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
myn said:
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
Click to expand...
Click to collapse
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
I was receiving this error for two days after s-off and updated recovery. I was breaking my head trying to figure out a solution. I tried everything from switching recoveries to even pushing SU again. I also downloaded ROMe using my pc and my phone bc many ppl were calling the ROMs "corrupted." Nothing worked. I even received hate mail from multiple XDA members bc I was posting "too" many questions "without" searching the forum.
Solution, changing out my SDcard. LMAO, yes I know, wanted to run through a wall bc i had thought of it right off the back but did not want to believe my 32 gig card was causing the problem. I replaced with the card that came with the phone and BAM have been switching ROMs ever since.
Food for thought.
AssassinsLament said:
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
Click to expand...
Click to collapse
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
First off, who really cares about "Backup Naowz!" being an issue but you? I mean seriously, you're just trolling. So do you go tell people they can't speak improper english because you don't like it? Come on. We do this for free, for fun. If you paid us to make this recovery for you, then sure, if what you want is Backup Now!, we can do that for you. But you are using it for free. At least feel grateful of what we've done as a hobby for everyone instead of nitpicking 10+ issues on the smallest inaccuracies that go against your perfect world. Seriously, I'm sure others might like the "Backup Naowz!". Anyways, if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Here's the zip that was giving me the sideload errors.
I don't see any issues with the updater-script and the updater-binary is ver 3.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
i completely agree with polish and consistency portraying professionalism, and we're glad for and always open to suggestions. however, in this case, we purposely used that terminology. we, as teamwin, like to have fun with our projects. some of them are very serious (wimax, hdmwin, kernel manager). others are a bit more on the entertaining side (theninjatweeter, twinpic 3d). with the recovery, we wanted to do something that stood apart from the rest. we do things that reflect our personality as a team.
as for the sideload issues that many are experiencing, we've discussed many times in our threads as well as on twitter and even google+; it is an issue with an outdated updater-binary script. update the scripts, no more sideload errors.
to come out and say we're not willing to listen to suggestions seems a bit presumptuous, even dangerous, when the issues you put on our github were more along the lines of requests.
AssassinsLament said:
...
if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Click to expand...
Click to collapse
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
myn said:
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
Click to expand...
Click to collapse
Again, I don't mind real issues... That's not my point. My point is a lot of your so called bugs or issues are the way we cosmetically chose to do it. Your issues are more so opinions, and wish lists. There is a place for opinions, and a place for real bugs. That's all I am saying.
It would be on the same level as me using your bug/issue space to say "hey i don't like that color.", "hey, can you take off myn from everywhere in your rom, I like it without?" <--- these are NOT issues. These are just what I would like/want. Do you understand?
Anyhow, I am looking into your script. Sadly we do not have any documentation of the differences between api's but, I will try to figure it out. It looks simple enough, so it should work. I'll let you know.
We are starting a new thread as we enter a new phase of development.
We are beyond confident @ this point that we are where we need to be. We are now working on new init.rc and init.mapphone_cdma.rc that will be able to boot a cm7 atrix nightly.
As of now we only have aceoyame working on these and wish to solicit ideas from those who may be more experienced or who have a keen eye for the obvious.
We will be test flashing this first run shortly. Lets keep this thread clean. We are expecting only comments relating to the new .rc's or pointing out obvious shortcomings of our method.
Expect a test flash to be posted here shortly so others can try along.
So without further ado... here are the initial versions of the inits as modified by aceoyame..
init.mapphone_cdma.rc http://pastebin.com/N3CFNrBX
init.rc http://pastebin.com/KdpL6eKC
Help and comments are welcome...
If you apprecieate our work please hit THANKS on the appropriate post to let us know you guys care and to keep the thread un-cluttered. So far with the other threads it seems we only have about 20 or so users who are looking forward to this.
There is an excellent thread here.. http://forum.xda-developers.com/showthread.php?t=1372293 started by ashclepdia that can be used for speculation, thanks, etc...
Thanks again to the many users here for helping during the sbf flashing phase.. we may need your help again soon.
And last but not least thanks again to dragonzkiller for taking the time from his busy schedule to get us past the last hurtle.
So fu$king excited! Thanks guys!
Sent from my DROID X2 using XDA App
While reading init.mapphone_cdma.rc i noticed like 3 mount points referencing yaffs2. From what I understood, yaffs2 isn't supported by the X2. That was the only glaring thing I saw so far.
Keep up the great work
Edit: Everyone, Please lets keep on topic. If you have any questions or you want to say thanks please use this thread http://forum.xda-developers.com/showthread.php?t=1372293
We need to keep this topic clean for the sake of development.
Thanks
can someone explain whats this for and what it does?
Does it improve something?
Makes my phone faster?
Last longer?
Took better photo and video?
Better sound quality?
Tnx
raclimja said:
can someone explain whats this for and what it does?
Does it improve something?
Makes my phone faster?
Last longer?
Took better photo and video?
Better sound quality?
Tnx
Click to expand...
Click to collapse
Well in an EXTREMELY broad overview, all this work that these fine gentleman are doing will take the lid off the jar of the x2. And when they are finished we will finally be able to port over miui and cm7 and many other roms for the x2. I super excited for miui... love u ace
kpkacts238 said:
Well in an EXTREMELY broad overview, all this work that these fine gentleman are doing will take the lid off the jar of the x2. And when they are finished we will finally be able to port over miui and cm7 and many other roms for the x2. I super excited for miui... love u ace
Click to expand...
Click to collapse
STATUS UPDATE
Well after numerous tries with variations on those inits we still have no sucessfull boot. Gonna try again tomorrow with some new inits.
Gonna keep @ this till we get somewhere..
raclimja said:
Click to expand...
Click to collapse
Put the phone down and back away! Haha I'm extremely excited about this I'm desiring to see a cyan droid spinning on my boot screen I only wish I knew more so I could be of some help top make this happen like yesterday. Im very thankful to all that are making this happen this forum will explode once this comes out LIKE BOOM
To the ones who like to clutter the thread (over half of this thread isn't relevant) and you know who you are please just only hit the thanks button. Even the OP has a link for people who can't stay on topic. This is necessary
Sent from my DROID X2 using XDA App
This is me asking for all of the x2 devs to pitch in and help with CM now that we have 2nd init going. The thing holding us back atm is our init scripts, the one were using bombs out shortly before boot animation (before adb runs) any help would be awesome!
Do you have link to CM7 including 2nd init you are testing with?
I want to push it into my phone when I get a chance this weekend and see whether I can help.
Thanks.
Well its a new day.. and i begin my holliday break.. Gonna spend a good bit of it working on this. I have some new approaches I am going to try today. Hopfully we can get some good information from the upcoming tests.
Do you have link to CM7 including 2nd init you are testing with?
I want to push it into my phone when I get a chance this weekend and see whether I can help.
Thanks.
Click to expand...
Click to collapse
We intend to release a testing package shortly, once it is logging some sort of usefull data for us. In its current conditions it is not very informative. Rather then spending time getting people up to speed on it.. i am gonna try to get it to a point that it is more useful and self explanatory.
Ideally someone with more experience booting on second init devices will come along and give us a nudge to speed things up
In the meantime i have re-written our hijack to work along side our current X2 bootstap so that will save us some sbf time.
Hang in there.. We are getting close. Thanks for everyones support.
Probably should've posted this earlier, but I have a fairly powerful system. I could compile for you guys.
(I'd need to know what to install, since I haven't compiled a ROM before)
Sent from my DROID X2 using XDA App
mastafunk said:
Well its a new day.. and i begin my holliday break.. Gonna spend a good bit of it working on this. I have some new approaches I am going to try today. Hopfully we can get some good information from the upcoming tests.
We intend to release a testing package shortly, once it is logging some sort of usefull data for us. In its current conditions it is not very informative. Rather then spending time getting people up to speed on it.. i am gonna try to get it to a point that it is more useful and self explanatory.
Ideally someone with more experience booting on second init devices will come along and give us a nudge to speed things up
In the meantime i have re-written our hijack to work along side our current X2 bootstap so that will save us some sbf time.
Hang in there.. We are getting close. Thanks for everyones support.
Click to expand...
Click to collapse
So I take it the script I sent you over helped a lot? It's good to see that! If you're guys' init script works I can patch them into an actual CM7 build for the X2 (So that we can have a device config, and eventually nightlies for it).
fortune82 said:
Probably should've posted this earlier, but I have a fairly powerful system. I could compile for you guys.
(I'd need to know what to install, since I haven't compiled a ROM before)
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Don't worry about trying to compile anything yet. For a few reasons:
They're only patching an ATRIX build, not compiling yet
We don't have a full device setup for the X2 (i'm working on that now)
My computer is more than powerful enough to start releasing office DX2-Dev-Team betas from the repo, so don't worry about compiling yet
I will be on irc @ #X2-AOSP all night for the specific discussion of this thread.
So after a late night in IRC we managed to past 1 of the 2 hurdles we were trying to solve. Thanks to all that helped.
We were able to get some logcat action going!!
One more hurdle to pass and we are going to be VERY CLOSE.
Thanks again for those that were up late night working on this..
Which hurdle?
Tapped from my tweaked out DX2
Which hurdle?
Click to expand...
Click to collapse
answered in the post above yours..
mastafunk said:
We were able to get some logcat action going!!
Click to expand...
Click to collapse
Duh moment lol,
Tapped from my tweaked out DX2
is this the lockboot loader you guys are trying to crack?
If so, would this allow people to install or port ics? or copy the fix for blue tint on camera on droid 3?
Tnx
First off I would like to extend a hardy thanks to LilChris for assembling this most excellent ROM. It was able to breath new life into my SGS2 (AT&T version I777)
I will be sure to donate.
I am left with one question that I've spent the last 2 hours trying to find a definitive answer too. I would like to have the ability to control my processor clock speed and with Entropy's current Kernel it seems it caps at a stock 1200MHzm, is there a different Kernel that allows overclocking(undervolting) to be installed?
I come from DroidX/DroidX2/HTC Thunderbolt and have a firm understanding of the whole rooting/romming process.
My current device is rooted, running Phone Bricker.
If this has been answered elsewhere, please forgive me, I did look for quite some some.
Thanks
Wink
Donate to Entropy not me.
He is working on the kinks for overclocking, just give him time he is busting his ass to get us another amazing kernel.
I can do that.
I installed a different kernel, and while I could certainly overclock, I could not make telephone calls.... kind of a bad tradeoff. I went back to Phone Bricker as it came out of the box. I've got to say I am absolutely in love with this ROM.
Having dealth with Motoblur and its depressing color scheme, and overall.....yuckiness, I am just thrilled with this ROM.
Thank you for answering my question.
It does lead me to one other one, is there a central repository where I would be able to see this (as of yet unreleased) kernel?
Thanks again and have a great weekend!