Database Develop

HTC Droid Incredible Kernel List (10/25/11)

Because the last kernel list hasn't been updated, I decided to make one. Leave a comment if I miss one.
Format is
Kernel Name w/link *
[GB/FROYO] [2.6.x.x] Date updated:[x-x-xx]
*= Available from kernel manager
AOSP
invisiblek
[FROYO] [2.6.32.26] [3/9/11]
invisiblek*
[GB] [2.6.37.6-4] [06/11/11]
Chad's incredikernel
[GB+FROYO] [2.6.38.8] [09/17/11]
Tiamat*
[GB] [2.6.38.8] [10/12/11]
jdkoreclipse*
[GB] [2.6.38.8] [6/22/11]
Savaged Zen
[GB] [2.6.37] [3/1/11]
Audio Boost
[GB] [same as CM7 but with all audio boosted] [3/19/11]
Click to expand...
Click to collapse
Sense
HeyitsLou Custom Sense Kernels
[FROYO] [2.6.32.17] [1/23/11]
Chad's incredikernel
[FROYO] [2.6.32] [12/23/10]
Ziggy471
[FROYO] [3/19/11]
Gingertiny
[GB] [2.6.35.10] [10/23/11]
Loadable Gingersense Modules
[GB] [09/18/11]
Click to expand...
Click to collapse
Extras
Viper Mod
[Undervolting]
Incredicontrol
[App made by Chad to change kernel settings on the phone.]
Click to expand...
Click to collapse
ROM Thread
Lots of information about kernel acronyms and android in general.
Also, mods please sticky this.

thank you for doing this. much easier to watch one thread.
just a suggestion. you might want to put when they kernels were updated and if its for gb or froyo. i can see some say it but i would put a note under each hyperlink.

synisterwolf said:
thank you for doing this. much easier to watch one thread.
just a suggestion. you might want to put when they kernels were updated and if its for gb or froyo. i can see some say it but i would put a note under each hyperlink.
Click to expand...
Click to collapse
Definitely agree. I think a good format would be something like
Kernel Name w/link
[GB/FROYO] [2.6.x.x] [Updated x-x-xx]
And keep them separated by AOSP and Sense like you are already doing.

TheWhiteBandito said:
Definitely agree. I think a good format would be something like
Kernel Name w/link
[GB/FROYO] [2.6.x.x] [Updated x-x-xx]
And keep them separated by AOSP and Sense like you are already doing.
Click to expand...
Click to collapse
Good idea, I'll do that.

ithrewitontheground said:
Good idea, I'll do that.
Click to expand...
Click to collapse
Excellent job, exactly what we need! Thank you for the updated list

Anyone know why haven't sense kernels been updated?
Sent from my ADR6300 using XDA App

Pkmn760 said:
Anyone know why haven't sense kernels been updated?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Most Sense developments have been on Gingerbread sense lately, but since we don't have the official OTA, the kernel source hasn't been dropped from HTC yet so no one is making kernels for GingerSense.

TheWhiteBandito said:
Most Sense developments have been on Gingerbread sense lately, but since we don't have the official OTA, the kernel source hasn't been dropped from HTC yet so no one is making kernels for GingerSense.
Click to expand...
Click to collapse
i was just about to say this. :/

Duplicate post
Every link for Incredible kernel is here
http://forum.xda-developers.com/showthread.php?t=969371
Then under this post http://forum.xda-developers.com/showthread.php?t=969371
had original links to all ROM's, kernels,bootanimation, and splashscreens.

No it's not
rlacrossjr said:
Every link for Incredible kernel is here
http://forum.xda-developers.com/showthread.php?t=969371
Then under this post http://forum.xda-developers.com/showthread.php?t=969371
had original links to all ROM's, kernels,bootanimation, and splashscreens.
Click to expand...
Click to collapse
Actually that kernel list is outdated, a few of those aren't being developed anymore.

What is the fastest best kernel?
for AOSP gingerbread..
I have never tried inviseablek or tiamat...
I use Chad's Incredikernel....

Imo it's chads latest incredikernel, that's what I run, but it wouldn't hurt to test a few out.
Sent from my ADR6300 using XDA App

Thanks for the list, I hope you keep this updated.
I'm changing the link on my "list of roms" thread to this one.

I'll try and keep it updated, as long as kernels keep getting updated . Really think this should be a sticky though.

Is there any kernels for GB+Sense? I've got a stock rom and want better battery life lol

dmeadows013 said:
Is there any kernels for GB+Sense? I've got a stock rom and want better battery life lol
Click to expand...
Click to collapse
Nope no kernels yet for gb-sense

We finally have a custom Gingerbread sense kernel thanks to tiny4579!

ithrewitontheground said:
We finally have a custom Gingerbread sense kernel thanks to tiny4579!
Click to expand...
Click to collapse
You should update the Updated tag to the correct date in the title of this post so people know you added it in!

That was dumb of me. Updated now.

3.0 Kernel for AOSP JB?

I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least

TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....

There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app

I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app

TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?

Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app

CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.

ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?

The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s

CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.

ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?

markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.

Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?

The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.

The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.

TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:

zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!

markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed

[INS-KER] Insecure Kernel (Rooted) for GT-I9300 [Latest: I9300XXELLB (2013-01-15)]

Hello everyone,
I'm are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROMs by Samsung.
Why should i use this kernel?
My kernels are uber-minimal modification of stock kernel used only for rooting (no custom recovery is installed). So the kernel it's like stock just rooted, and there is small chance (or any chance) that it will be detected as modified by service center at the first look
Please find latest of kernels listed below:
*NEW* ROOTED! I9300XXELLB - Jelly Bean (4.1.2) - CL: 748978 - B.Date: 26.12.2012 - Download HERE!
[[size=-2]uname: Linux version 3.0.31-748978 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Dec 26 15:40:05 KST 2012[/size]]
Instructions:
1. Flash tar file of choosen kernel using Odin
2. Profit!
What's included in this kernel
- Base image of kernel is 100% pure stock by samsung
- adbd in insecure mode (so adb shell will be automatically connected with root priviliges)
Nothing more, nothing less - Enjoy!
If you like my modifications, support me with even a little donation for a beer -> Click to donate!
WARNING: Flashing this kernel will pop-up your custom binary counter! (as when rooting )
Enjoy!

wanna ask, this kernel have sds fix or not?

SDS fix is not in kernel but bootloader and yes, this version (if you will flash full rom) have new bootloader with fixes.
Adam

http://forum.xda-developers.com/showthread.php?t=2091045
from above link, i think the fixes is from kernel.. iinm, the ella firmware has the fix.. not sure from bootloader or kernel..
that's why i ask about this, to know whether ellb = ella in terms of sds fix..

AdamLange said:
SDS fix is not in kernel but bootloader and yes, this version (if you will flash full rom) have new bootloader with fixes.
Adam
Click to expand...
Click to collapse
No it's not.
Also LLB is not latest kernel.
Also this is in the wrong forum.

AndreiLux said:
No it's not.
Also LLB is not latest kernel.
Also this is in the wrong forum.
Click to expand...
Click to collapse
Why then?
Not A not C... LLB??? Strange, bardzo.

AndreiLux said:
No it's not.
Also LLB is not latest kernel.
Also this is in the wrong forum.
Click to expand...
Click to collapse
1. post some more info instead of trolling.
2. its latest in this thread not overall, i never told that this is latest from Samsung
3. REally? its I9300, its ORIGINAL (kernel is not compiled its just stock modded, so its original.)
Something else?
Adam

sebarkh said:
Why then?
Not A not C... LLB??? Strange, bardzo.
Click to expand...
Click to collapse
i will add more soon (pozniej ;>)
Adam

Personally I always thought original means ORIGINALly YOURs (you are the author, not copied), not original Samsung....
But. .. maybe mistaken. ..
Variety makes this forum better anyway. ..

Kernel base is 100% oryginal, its not recompiled or compiled from sources, so in that meaning its 100% STOCK KERNEL.
Insecure kernels have modded adbd and other settings needed to run is as root in INITRAMFS of kernel.
This make it ROOTED STOCK KERNEL 100%

AdamLange said:
SDS fix is not in kernel but bootloader and yes, this version (if you will flash full rom) have new bootloader with fixes.
Adam
Click to expand...
Click to collapse
After reading page after page on this form every one is saying the sd fix is in the kernel. How come your saying it's in the bootloader? Also what do you mean (if you flash full rom) What rom? Its a kernel in your op.
Sent from my GT-I9300 using xda premium

Noone confirmed it isnt. I can't also confirm it is or not. This is not thread about it. Move along
Adam

AdamLange said:
Noone confirmed it isnt. I can't also confirm it is or not. This is not thread about it. Move along
Adam
Click to expand...
Click to collapse
You boldly said that the bootloader had the fix. Now you don't know if it has or not. And your a developer of an original kernel. Move along
Sent from my GT-I9300 using xda premium

AdamLange said:
1. post some more info instead of trolling.
Click to expand...
Click to collapse
There's two massive threads in the general section with enough information, I'm not here to educate you myself, I just pointed it out. We don't need developers coming in and doing false statements as there's enough misinformation on the topic, you already confused some users here.
AdamLange said:
2. its latest in this thread not overall, i never told that this is latest from Samsung
Click to expand...
Click to collapse
Uhm..
I'm are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROMs by Samsung.
Click to expand...
Click to collapse
Actually that is exactly what you've told... Rephrase your English otherwhise.
AdamLange said:
3. REally? its I9300, its ORIGINAL (kernel is not compiled its just stock modded, so its original.)
Click to expand...
Click to collapse
You're mixing up the meaning of original, this section if for original works in the meaning they are made by users (Compiled kernel/ROM/program), not original in the sense as the manufacturer delivers them. It's written in the sticky in the development forum or in the portal post. Repacking kernels isn't original development. Read.
AdamLange said:
Noone confirmed it isnt. I can't also confirm it is or not. This is not thread about it. Move along
Click to expand...
Click to collapse
Actually yes it is confirmed it's in the kernel because we have the kernel code and patch regarding the issue.
Something else?

Sorry for misleading, i didnt noticed the topic with patch, i cant track everyhing.
this thread is about insecure kernel mod not a patch for death of SGS, so please no more offtopic here.
Insecure kernels are stock base (zImage is not modified) kernel with modded initramfs, where STOCK means no "tweaks" in kernel code was made. All insecure kernels works like this so i dont see a point of bashing me for saying its STOCK cause base of kernel is.
I asked mod to clean the thread.
A

And I've said it's not an original work as how you wrote in big capital letters claiming it is. Why are you replying to me about what a (insecure) stock kernel is?
AdamLange said:
I asked mod to clean the thread.
Click to expand...
Click to collapse
Why? It's a development discussion. You can't just go ask a moderator to delete things every time because somebody else is correcting you. That's bothering and abusing moderators.

it is original work. its modded initram by me , base is stock. if you dont like it, dont use it. if you dont like my reference to stock, then dont like it, i dont care.
I asked to clean the thread because you are not discussing, just attacking my work.

I have moved the thread to the Development Forum.
Can the arguments stop now please?
Keep it on topic or leave the thread alone.
Mark.

[ Guide / Script ] Auto-Porter

WINDOWS
Note: Tested on Windows 8
1) 7-Zip
2) Winmerge
3) Notepad++
4) Java SE Development Kit
5) Place on your Desktop in a folder.
This script comes with instructions for each step, It is the MIUI auto-porter modified for general use with CM10 based roms.
It will say a bunch of stuff about MIUI on the splash-screen at the start, Ignore it.
Any Rom that uses CM10 as a base can be ported to this device using this script.
Download: Auto-porter

I know It's not a new rom update but I figured you folks would like it better, to test it out go to AvatarRoms site or some other CM10 based rom and try your hand at porting!
Some roms will have TW framework or other things like this and that must be taken care of manually, so for more complex ports you will need a good understanding of how to port and diff and xml editing and so on; but for very basic things or to create a quick port to assess what kind of potential work would need to be done, how compatible your device is with a base; this is a good place to start.

Hello
We can port any rom based on CM10 with this ? Like Paranoid Rom ??

Fekajo said:
Hello
We can port any rom based on CM10 with this ? Like Paranoid Rom ??
Click to expand...
Click to collapse
Try to and it wll prob work

I have already tried this with CM10 epinter for base and Paranoid for AT&T One X because they are the same architecture and screen size ( 1280*720 )
But they don't start, i see the log but i don't understand anything ^^'
I retry and i give you feedback
Thanks for your work

im trying that right now the cm10 and pana will tell you if it works its 2.70 so dont think it has pie but hey whatever

Fekajo said:
I have already tried this with CM10 epinter for base and Paranoid for AT&T One X because they are the same architecture and screen size ( 1280*720 )
But they don't start, i see the log but i don't understand anything ^^'
I retry and i give you feedback
Thanks for your work
Click to expand...
Click to collapse
Sometimes the foreign rom is just not compatible as a base, you will see results as you experiment and find which phones are most 'similar' to yours

If anyone has successfully ported a rom with auto-porter that boots and is somewhat functional or functional, then please post and share the details here. I personally do not know how to port a rom, or make a rom etc., But I am willing to learn how to use the auto-porter in this thread if someone is willing to point me in the right direction. Like which base to use, and what modifications need to be done and so on...

the tmobile s3 is based from the same chipset, should try there to see

Will this work with CM10.1 ROMs? Looking into porting AOKP 4.2 the easy way

Ban-Hammer said:
Will this work with CM10.1 ROMs? Looking into porting AOKP 4.2 the easy way
Click to expand...
Click to collapse
Hmmm, Perhaps but most likely not, I haven't tried any CM10.1 roms in this fashion

Tquetski said:
Hmmm, Perhaps but most likely not, I haven't tried any CM10.1 roms in this fashion
Click to expand...
Click to collapse
Alright. I can wait patiently for Hashcode
Sent from my XT926 using Tapatalk 2

Can you do a CM9 version ?

radnou974 said:
Can you do a CM9 version ?
Click to expand...
Click to collapse
Uh....

radnou974 said:
Can you do a CM9 version ?
Click to expand...
Click to collapse
It might work with CM9, worth a try.
May I ask why CM9? CM7 is much more stable on these phones.
Sent from my XT926 using Tapatalk 2

Dam i can't get miui up and running. I know it's kernal related but I'm not even getting a home screen. Smh.
Sent from my Razr HD using Tapatalk 2

Sense 5 rom?

Is there going to be Sense 5.0 Rom for HTC incredible s? Could it be ported?

deni1996 said:
Is there going to be Sense 5.0 Rom for HTC incredible s? Could it be ported?
Click to expand...
Click to collapse
Not to sound rude but to open a new thread in the development section to ask such a question is just not right. Please post such questions in the general section.
We do not have that many devs working on incredible s as it is a relatively old device. If someone manges to develop an ion kernel and port sense 5 you will see it in the dev section.
Quite fortunate to get a few working jellybean aosp ROMs and quite a few sense 4.1 ROMs for a device that has no more support from htc so enjoy those and be happy.
@ moderator can this thread please be closed or moved to the general section?
Sent from my HTC Incredible S using xda app-developers app

deni1996 said:
Is there going to be Sense 5.0 Rom for HTC incredible s? Could it be ported?
Click to expand...
Click to collapse
No. Because kernel.

spazzy1912 said:
No. Because kernel.
Click to expand...
Click to collapse
-_- what do u mean kernel...... The kernel is still a jellybean kernel, just modified to be compatible with Sense. Although I dont know how to do it, Im sure it might be possible for someone like Szeszo to develop such a kernel. The only problem is that it requires a ton of work and I dont think Szeszo has that much time..... Not to mention resizing of the actual ROM.....

072665995 said:
-_- what do u mean kernel...... The kernel is still a jellybean kernel, just modified to be compatible with Sense. Although I dont know how to do it, Im sure it might be possible for someone like Szeszo to develop such a kernel. The only problem is that it requires a ton of work and I dont think Szeszo has that much time..... Not to mention resizing of the actual ROM.....
Click to expand...
Click to collapse
its got something to do with a thing called ION within the kernel.
apparently our phone doesnt have it by default.
it was mentioned somewhere in cyanvivo thread i believe.

spazzy1912 said:
its got something to do with a thing called ION within the kernel.
apparently our phone doesnt have it by default.
it was mentioned somewhere in cyanvivo thread i believe.
Click to expand...
Click to collapse
Yes it was and Im well aware of that. Our phone doesnt natively support Ion and as a result you have to change some camera libs, i think they were, and maybe a few other things here and there. But it is possible and the proof to that is the fact that we have Jellybean ROMs for our device.