Related
NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
Hiya everyone,
I've ported Dumfuq's overclocking patches from 2.6.29 to 2.6.32.21! This applies to those of us using the stock HTC OTA and allows the use of programs like SetCPU. This kernel was built from the source code from http://developer.htc.com and the kernel config is an identical copy of the one included in the latest Froyo OTA (my leak).
My current method of providing this is as an update.zip... just put this on your SDcard, boot into Clockwork, and flash it. If it kills your kittens, do not blame me.
Also, reminder: flashing this zip alone is not enough to overclock your device. Afterward, use a program (from the Market) such as SetCPU to overclock your device.
Download: http://www.multiupload.com/2XEWYRL62U
Change Log:
- Revision 2
Fix Wifi issues (as well as any other kernel module loading issues).
Add support for CPUfreq governers 'interactive' and 'smartass'.
Change the default governer from 'ondemand' to 'interactive' - this dramatically improves redraw performance and other user-interface responsiveness.
To change to the Smartass governer use something like SetCPU.
Include the MSM KGSL TLB performance tweak changes that are present in CM's kernel repository. You may or may not notice any video performance improvement, but it provides a possibility of improvement.
Fixed the kernel version string to properly read '2.6.32.21' not '2.6.32.17' - the first version wasn't .17, it was .21.
Please remember to disable the HTC Perflock in SetCPU by pressing the Menu key (while in SetCPU) and selecting 'Perflock Disabler'.
Happy? Donate.
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
What is the max frequency of this kernel? And does it include smartass governer?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
agentg1001 said:
What is the max frequency of this kernel? And does it include smartass governer?
Click to expand...
Click to collapse
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
nbetcher said:
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
Click to expand...
Click to collapse
I have made the changes, however I decided to NOT disable HTC Perflock through the kernel config, so please make sure to disable it (via SetCPU) first before trying to overclock or change your governer. New version uploaded, see OP.
Could you also include some higher frequencies? (Preferibly up to 960)? That would be great because my phone is stable up to 921. Also compcache enabled (like drowning child's kernel) would be awesome.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I'm not sure why but my slide didn't like this kernel
http://pastebin.com/hVgG467j
Thank the devs for nandroid!
My slide not working with this kernel too (
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly. Besides, according to that logcat your problems aren't related to the kernel... Android is unable to mount any of the MTD partitions (/system, /cache, /data, etc).
Please let me know more about what you're running.
Also, I'll be working on making a separate version of this that has OC enabled up to 960MHz, but 960MHz is very dangerous... 800MHz+ is even asking for trouble despite our processor's normal clockrate being 800MHz (T-Mobile downclocked it to 600MHz out-of-the-box).
I'll look into Compcache as well.
im IN.
good job, will try after work. gj
how long does it take to boot the first time?
been stuck at the white MT3GS boot screen for a few minutes now.
running CM7 RC4
EDIT: oops, did not know this is only for the leaked froyo update
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Sefy said:
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Click to expand...
Click to collapse
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
pettigrew95 said:
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
Click to expand...
Click to collapse
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Sefy said:
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Click to expand...
Click to collapse
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
nbetcher said:
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
Click to expand...
Click to collapse
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Sefy said:
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Click to expand...
Click to collapse
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
EDIT: in hind-sight this all seems to not really answer your question and only further supports the need for a better answer to you, but hopefully you'll find some clarity.
nbetcher said:
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
Click to expand...
Click to collapse
Everyday you learn something new! thanks for being the teacher!
nbetcher said:
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly.
Click to expand...
Click to collapse
Well now I feel a bit sheepish, I guess that's what I get for not reading closely enough, I'm running CM7 RC4, sorry about that.
Does anyone happen to have a copy of this kernel laying around somewhere? Megaupload is long gone unfortunately
So after a couple of days of reading guides on the internets, I've been able to compile a mostly stock kernel that incorporates some of the changes made by joe85 in his NOLIGHTS Kernel. This kernel is stock other than the changes outlined below. The anykernel scripts keep your existing RAMDISK intact. If you had init.d support/other RAMDISK mod(s), it will still be present after flashing this kernel.
mKernel_v1.3
-Added TUN module for VPNC support
-Changed Display Maximum PWM from 232 -> 255
-Changed Display Minimum PWM from 8 -> 6
-Dimmed LEDs (from 20 mA -> 2 mA) or turned off completely
-Remove LED notification timer (does not shut off until dismissed)
------NotifyTimerOn versions use default timer to shut off notification LED
Click to expand...
Click to collapse
Adding overclocking has proven to be too much for me to do (more info on challenges of asynchronous dual core OC here. There isn't really much of an update going from 1.2 -> 1.3. I just re-did the changes from stock and tracked them using github. I did leave out the setting that joe85 made that allowed users to set a LED brightness via cmd line. There are 2 versions - mKernel_dim_1.3 for dim capacitive LEDs and mKernel_LEDoff_1.3 for capacitive LEDs which are always off.
You need a 2.3.4 based ROM for it to work and it can be flashed from recovery.
You can also flash it via joeykrim's Flash Image GUI with runs on your phone and is compatible with HBOOT 1.50. LINK!
Thanks to koush for the anykernel scripts and joe85 for all of his work (I just copied it into the new 2.3.4 kernel).
Everything works fine on my phone, but please post if you have any problems (not responsible, blah, blah, blah ).
github source with commits showing changes from stock kernel. There's not many and none should affect battery, performance, etc. compared to stock.
Nice will be checking this out for ya in a bit. Will report back
Currently on Myn's rom and about to give this a go Thank you.
Sent from my PG86100 using xda premium
Cool, gonna run it. Thanks.
Nandroids are for sissies.
Bang.
jayharper08 said:
Currently on Myn's rom and about to give this a go Thank you.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Dude, where can I find Myn's rom?! Been sporting him on Evo4g but miss him on my 3D.
Ok I wanna try too, but how come nobody reported back lol....
>.>
<.<
EDIT: running this now, lovin it dim lights + other mods, stock kernel, but with my ROMs ramdisk
lloydcabraham said:
Dude, where can I find Myn's rom?! Been sporting him on Evo4g but miss him on my 3D.
Click to expand...
Click to collapse
Rootzwiki.com
lloydcabraham said:
Dude, where can I find Myn's rom?! Been sporting him on Evo4g but miss him on my 3D.
Click to expand...
Click to collapse
Yup. Like il said, it's on rootzwiki, but there is a link in this thread for it. Last Page.
http://forum.xda-developers.com/showthread.php?t=1254341
Sent from my PG86100 using xda premium
mwalt2 said:
So after a couple of days of reading guides on the internets, I've been able to compile a mostly stock kernel that incorporates some of the changes made by joe85 in his NOLIGHTS Kernel. This kernel is stock other than the changes outlined below.
You need a 2.3.4 based ROM for it to work and it can be flashed from recovery.
Thanks to whomever made all of the scripts in the .zip and joe85 for all of his work (I just copied it into the new 2.3.4 kernel).
Everything works fine on my phone, but please post if you have any problems (not responsible, blah, blah, blah ).
Click to expand...
Click to collapse
You are now my hero! I have been dreaming of low lights since 2.3.4 came out! What about CIQ removal and the such?
I would thank the post but I ran out I'll hit you up tomorrow!
Also, I wont be able to provide feedback for a couple days. I am doing some load testing on my latest ROM.
scrosler said:
You are now my hero! I have been dreaming of low lights since 2.3.4 came out! What about CIQ removal and the such?
I would thank the post but I ran out I'll hit you up tomorrow!
Also, I wont be able to provide feedback for a couple days. I am doing some load testing on my latest ROM.
Click to expand...
Click to collapse
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
Correct. CIQ crap is in the ramdisk. I'm trying this asap!! Muchas Gracias!!!
About to give this a try, Thanks
nice to see your handy work mwalt! you'll be a android pro in no time
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
sweet I think you just answered my question, your updater script uses the ROMs ramdisk then and ONLY replaces the kernel/zimage ???
O.M.J said:
nice to see your handy work mwalt! you'll be a android pro in no time
Click to expand...
Click to collapse
you in mpls ?!?!
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
removing carrier IQ is big task and goes beyond the kernel, as you stated.
there was a guy over on SDX dev's that did it by removing the scripts from the framework.res apk. so basically the programs were still on the phone, but when you fired the phone up they didn't start.
that is the only way that i am aware of that it can be done. it's a lot deeper than the kernel and deleting apk files from the system.
EDIT** and when i say that is the only way i know of, that doesn't mean it is the only way.
Will this kernel work on Synergy 475 with EXT4 Opt.?
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
Ok, I didint look at the zip until now and didint realize it wasnt the entire boot.img. Thanks for letting me know.
cobraboy85 said:
removing carrier IQ is big task and goes beyond the kernel, as you stated.
there was a guy over on SDX dev's that did it by removing the scripts from the framework.res apk. so basically the programs were still on the phone, but when you fired the phone up they didn't start.
Click to expand...
Click to collapse
They are also very deep in the framework.jar and service.jar not to mentions some APK. TrevE did a great write up here: http://forum.xda-developers.com/showthread.php?t=1247108
It shows alot of dirty stuff HTC did.
Running clean. It's so perfect I'm not sure but I have to try. LOL. Will report back.
Sent from my PG86100 using xda premium
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
DedS Kernel
I'm not responsible if your phone explodes or causes any damage. You are willing to try this kernel.
Click to expand...
Click to collapse
DedS is a 4.3 JB kernel for rooted phones running custom roms,which will increase your performance
Features:
*Added experimental Underclocking and Overclocking
*Additional CPU I/O Schedulers:Sio,Row,V(R),Zen,FIOPS,Fifo
*Additional CPU Governors:Hybrid,Intellidemand,Intelliactive
*Init.d support
*O3 Optimizations
*Added KSM(Kernel Samepage Merging)
*GPU Overclocked at 533MHz
*Frandom driver
*Sweep2wake/doubletap2wake functionality(experimental)
*Kernel compressed with LZMA
*VFP Optimizations
Click to expand...
Click to collapse
INSTRUCTIONS:
*Download the kernel zip file from link given below.
*Place the zip file in external SD card.
*Reboot to recovery.
*Wipe cache, wipe dalvik cache.
*Install the zip file.
*Reboot.
*Phone will reboot. Enjoy the kernel
Downloads:
Available here:
http://www.androidfilehost.com/?w=files&flid=16352
Click to expand...
Click to collapse
Sources:
https://github.com/Ateekujjawal/android_stock_kernel_ms013g
Changelogs on post#2.
Enjoy the kernel.
If any dev wants to include this kernel in their rom,please provide a link to this thread and the source code.:fingers-crossed::good:
CREDITS:
[MENTION]rutvikrvr[/MENTION]:For providing kernel sources.
[MENTION]shabbypenguin[/MENTION]:For helping me repack the boot.img
XDA:DevDB Information
DedS stock kernel, Kernel for the Samsung Galaxy Grand 2
Contributors
##W4TCH0UT##, rutvikrvr, shabbypenguin
Kernel Special Features: fast and many experimental features and tweaks added
Version Information
Status: Stable
Current Stable Version: 003
Stable Release Date: 2014-07-14
Created 2014-07-06
Last Updated 2014-07-15
Reserved
CHANGELOGS:
|===========|
VERSION 003:
*GPU Overclocked @533mhz.
*Reverted CPU OC and UC.
*Added sweep2wake and doubletap2wake functionality(experimental)
*Add frandom driver.
*Added governors intellidemand and intelliactive.
*Add init.d support.
*Included sweep2wake enabler/disabler.
*Included Performance Control app.
*Some more performance tweaks added.
=================
VERSION 002:
*Added Sio,Row,V(R),Zen,FIOPS,Fifo I/O Schedulers
*Added Hybrid Governor
*Hopefully fixed UC and OC.
*Some minor fixes
=================
VERSION 001:
*Initial release.
|===========|
Great job bro.Finally OC kernel on blocks.Hope someone tests it.
-HellRaiser- said:
Great job bro.Finally OC kernel on blocks.Hope someone tests it.
Click to expand...
Click to collapse
Goooood JOBBBB.... i hope the kernel is soon is Stable keep the good workkk... you already try the OC?
if it work and not have bootloop i will try..
I try...
I try but odin immediately shows:
" ...
MD5 hash value is invalid
<OSM> 4.2-DedS_kernel.tar.md5 is invalid.
..."
I'm wrong?
Flashed kernel using terminal but stuck in download mode just after reboot
Sent from my SM-G7102 using Tapatalk 2
Flash using odin but stuck at bootscreen
Sent from my SM-G7102
Wait... Let me check...
Sent from my GT-I9082 using Tapatalk
Can anyone provide me the meta-inf folder from balli's ROM... I can't download it right now... I don't think it repacked properly..
Sent from my GT-I9082 using Tapatalk
Wait
Sent from my SM-G7102
---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------
https://www.dropbox.com/s/h991gw10jub455z/META-INF.zip
Sent from my SM-G7102
what would the meta-inf folder have to do with your kernel? i could understand if you think your updater script was wrong, as that would have possibly led to bricks. but you have an odin tar, which is just the kernel and odin tells it where to go.
shabbypenguin said:
what would the meta-inf folder have to do with your kernel? i could understand if you think your updater script was wrong, as that would have possibly led to bricks. but you have an odin tar, which is just the kernel and odin tells it where to go.
Click to expand...
Click to collapse
Again...this is odin flashable...not recovery flash able..... So there is nothing to do with updater script.... And. I think metainf for the inside of boot.img .... Or.. He want try make Recovery Flashable.
white7561 said:
Again...this is odin flashable...not recovery flash able..... So there is nothing to do with updater script.... And. I think metainf for the inside of boot.img .... Or.. He want try make Recovery Flashable.
Click to expand...
Click to collapse
I literally said it was an odin flashable tar in my post that you quoted. there is no meta-inf folder inside a a boot.img or odin tar hence my confusion on why he said it wasn't packed right and needed that to try and fix it.
@ shabbypenguin can u create kernel for us.. as u did for recovery??
Sent from my SM-G7102
shabbypenguin said:
I literally said it was an odin flashable tar in my post that you quoted. there is no meta-inf folder inside a a boot.img or odin tar hence my confusion on why he said it wasn't packed right and needed that to try and fix it.
Click to expand...
Click to collapse
Right.. Idk what he doing with Meta-inf folder...
Sorry for delay... But I'm busy and will start continuing tomorrow or today.
Sent from my GT-I9082 using Tapatalk
shabbypenguin said:
I literally said it was an odin flashable tar in my post that you quoted. there is no meta-inf folder inside a a boot.img or odin tar hence my confusion on why he said it wasn't packed right and needed that to try and fix it.
Click to expand...
Click to collapse
You had said that most of the problems were because the packing was not right, in your recovery thread. Can you tell me how can I repack it properly? I think it's problem of packing only. And I need meta-inf for future purposes. You said that there was no boot loader problem.
Sent from my GT-I9082 using Tapatalk
##W4TCH0UT## said:
You had said that most of the problems were because the packing was not right, in your recovery thread. Can you tell me how can I repack it properly? I think it's problem of packing only. And I need meta-inf for future purposes. You said that there was no boot loader problem.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
i havent downloaded your kernel but im willing to bet you arent using your dts files in the packing? what are you using as your mkbootimg command?
Does this kenel work??
Sent from my SM-G7102
manan001 said:
Does this kenel work??
Sent from my SM-G7102
Click to expand...
Click to collapse
Nope ... Bootloop
Sent from my GT-I9082 using XDA Free mobile app