Database Develop

[UNOFFICIAL] CyanogenMod 9 for Incredible S

Saw a lot of people posting about CM9 the past month, some were hoping it is official released or supported. It won't happen until awhile more for an official update. here's an unofficial build:
I just sync and built with the vivo device tree, only changes from stock CM9:
- kernel (kaijura) - without it: no panorama, updated kernel drivers, etc
- added usb
What may be fixed later or can be done:
- merge twistedumbrella's camera code to enable camera
- add rotating keys (st.matt)
Gapps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
July 02 build: http://d-h.st/ywY
cm-9-20120703.zip MD5: c0a64b1b7c2f297cb13f3ca4b501319d
Disclaimer:
I don't support or manage or fix bugs.
Only compiled for people who wanted to try where CM9 is or were sad IncS doesn't have CM9.
old posts for archive purposes
Code:
This is a kang'ed version of CM9 off the repo. It is totally experimental. This lets you get an initial taste of CM9 without having to wait for however long it takes for an official release. My initial impression after running this kang: CM9 has a long way to go before it becomes daily material.
[B]Current version compiled on Feb'23 2012.[/B]
[SIZE=5][COLOR=Lime]UPDATES this version:
Minor & small bugfixes. [/COLOR][/SIZE]
[quote][U][B][SIZE=4]Currently known NOT working major stuff[/SIZE][/B][/U]
-[COLOR=red] USB / SDCARD mounting is not working[/COLOR]
-[COLOR=red] Camera / Video not working [/COLOR]
-[COLOR=red] Other random bugs?[/color]
[/quote]
[quote][U][B][SIZE=4]Downloads BELOW[/SIZE][/B][/U][/quote]
cm-9.0.0-IncS-KANG-2012-02-23.zip
[url]http://www.mediafire.com/?v7dun59slnj5p7b[/url]
Google Apps: Get first one for CM 9.0.x Android 4.0.3-4
[URL]http://goo-inside.me/gapps#table[/URL]
[quote][U][B][SIZE=4]OLDER versions BELOW[/SIZE][/B][/U][/quote]
cm-9.0.0-IncS-KANG-2012-02-18.zip (106.35MB)
[URL]http://www.mediafire.com/?iktar6672q6ya73[/URL]
cm-9.0.0-IncS-KANG-2012-02-16.zip (109.61MB)
[URL]http://www.mediafire.com/?np79fdoncacxr1x[/URL]
cm-9.0.0-IncS-KANG-2012-02-10.zip (109.62MB)
http://www.mediafire.com/?rd3lrdebhgh7bbk[/URL]

Very nice downloading now.
Sent from my anus using xda crap

kaijura said:
cout << "kaijura has no responsibility over your bricked device - DISCLAIMER";
This is a kang'ed version of CM9 off the repo. It is totally experimental. Current version compiled on Feb'10 2012.
This lets you get an initial taste of CM9 without having to wait for however long it takes for an official release. My initial impression after running this kang: CM9 has a long way to go before it becomes DD material.
Click to expand...
Click to collapse
Thanks a lot
Swyped from my incredible s using tapatalk

nice...touch of cm9 is good.

Do the new gapps for ICS which popped out in Goo-inside.me works with this ?
http://goo-inside.me/gapps#table

Ok bro. I take back what i said in the general sect
I would love to point out the bugs but im sure u already know what they are = )
Good work kajiura bro
Sent from my HTC Incredible S using Tapatalk

jpkbeddu said:
Do the new gapps for ICS which popped out in Goo-inside.me works with this ?
http://goo-inside.me/gapps#table
Click to expand...
Click to collapse
Just tried the gapps 02 07 2012 version. Yep works fine so far for gmail, market and YouTube HD.

Following CyanogenMod 9 Blog from Cyanogen himself, he said a few words on the directions of the project:
http://www.cyanogenmod.com/blog/progress-on-cm9
So it seems like from what I understand what he says, we might not get official support for camera and video until the IncS HTC ICS release, which is supposed to be wayy later this year.

kaijura said:
Following CyanogenMod 9 Blog from Cyanogen himself, he said a few words on the directions of the project:
http://www.cyanogenmod.com/blog/progress-on-cm9
So it seems like from what I understand what he says, we might not get official support for camera and video until the IncS HTC ICS release, which is supposed to be wayy later this year.
Click to expand...
Click to collapse
That sucks major donkey butt.....

tethering work

Please, can you update the first post so the download link isn't unclickable from the xda app?
Links inside quotes are not links in the xda app... or if someone could just post the link for me
Sent from my HTC Incredible S using XDA App
*edit*
http://www.mediafire.com/?rd3lrdebhgh7bbk
So I can download it directly from my phone

who download's this stuff.. not to be rude, but it's half broken by the looks of it. there's other ICS ROMS out there with less problems.

Jess95 said:
who download's this stuff.. not to be rude, but it's half broken by the looks of it. there's other ICS ROMS out there with less problems.
Click to expand...
Click to collapse
This is cyanogenmod team, so you get an idea of how far the cm9 team has progressed with ICS. Some people have been with CM since the old G1 days you know?

Yeah its definitely not a daily but it is pretty cool to check out. Once our phone has an official ICS ROM from htc you can bet cm9 will be official for vivo. It's more of a peek at what's to come. I swear by cm so if we don't get official support I would be amazed and disappointed.
Sent from anus using xda crap

People thought about an e-petition to opensource the camera drivers?

updated for today's build

kaijura said:
updated for today's build
Click to expand...
Click to collapse
VERY COOL! Thanks kaijura, I'll have to try this one out! Can't wait for a fully working CM9

sabret00the said:
People thought about an e-petition to opensource the camera drivers?
Click to expand...
Click to collapse
I email them everyday for this they even called me back to say sorry and they would try their best to release it asap
Sent from my HTC Incredible S using XDA App

TheJimFish said:
I email them everyday for this they even called me back to say sorry and they would try their best to release it asap
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
People believe the target may be Qualcomm instead of HTC. There has been a long discussion on this at the DesireZ forums and lots of people emailed, you can read its progress here:
http://forum.xda-developers.com/showthread.php?p=20970354

I updated the CM9 KANG build to Feb'18 2012. Lots of commits and fixes, too much to list. Some minor changes but getting more and more stable now.
In other works, I have also ported a very popular DHD ICS ROM Ice Cold Sandwich from the Desire HD section with permission from LorD ClockaN and some help from vampire36 who ported it to the Desire S.
So far, it works fine on release 2.0, it uses some sources from CM9 and community fixes.
But I need to tweak it a little to get it working smoothly, there are some minor things wrong with it and camera is not working right at the moment. If people are crazy about it I'll try to get a fully functional rom up sometime.

HTC release ICS kernel source codes.

Finally they're here. Although only for Sensation's and One V at the moment. Hopefully this will help our awesome devs in their future releases. Here is a link for those interested:
http://www.htcdev.com/devcenter/downloads

Hopefully we don't have to wait much longer for a stable ics rom
Is our situation the same as the desire s? http://forum.xda-developers.com/showthread.php?t=1605341

incrediblealex said:
Hopefully we don't have to wait much longer for a stable ics rom
Is our situation the same as the desire s? http://forum.xda-developers.com/showthread.php?t=1605341
Click to expand...
Click to collapse
Just have to wait and see I guess. I have been quite impressed with the latest ics releases though and the talk in the thread you linked seems positive.

xda recognized developer nexx is working hard to make fully functional kernel for desire s and other same models. We will get stable ICS before release

sagarda7 said:
xda recognized developer nexx is working hard to make fully functional kernel for desire s and other same models. We will get stable ICS before release
Click to expand...
Click to collapse
Yeah I've seen their cm9 rom by nexx and it looks like he is working really hard to make it stable with one v source code. Hopefully we get some of that rom too.
Sent from my Incredible S using XDA

No CM9/10 for IncS?

I haven´t found any info around the web about CM team making a vivo release? Does anybody have information about that?

weaselEST said:
I haven´t found any info around the web about CM team making a vivo release? Does anybody have information about that?
Click to expand...
Click to collapse
The CM team tend to not discuss a lot of what they will release untill it is due soon. Guess it's to stop people nagging about deadlines.

They are probably waiting for the source code and kernel.

acme anvil said:
They are probably waiting for the source code and kernel.
Click to expand...
Click to collapse
Source code for HTC ROM? Or what?

weaselEST said:
Source code for HTC ROM? Or what?
Click to expand...
Click to collapse
They are waiting for the source code for kernel 3.0.16. Currently, it only works for Sense ROM's and not AOSP ROM's. AOSP for our device uses 2.6.x GB kernel hacked to work with ICS which is why our ROM's aren't fully stable yet unless your using the stock 3.0 kernel.
I emailed HTC regarding kernel sources and was told they will release it 90-120 days after the release of the WWE ICS RUU. The RUU was released a few weeks ago, so a few months to go unfortunately.

ZaySk said:
They are waiting for the source code for kernel 3.0.16. Currently, it only works for Sense ROM's and not AOSP ROM's. AOSP for our device uses 2.6.x GB kernel hacked to work with ICS which is why our ROM's aren't fully stable yet unless your using the stock 3.0 kernel.
I emailed HTC regarding kernel sources and was told they will release it 90-120 days after the release of the WWE ICS RUU. The RUU was released a few weeks ago, so a few months to go unfortunately.
Click to expand...
Click to collapse
exacly
s*ck but we must waiting
check ice cold sandwich
4 me best ics rom
5!

Just curious, what is the difference between AOSP kernel and Sense kernel in general? If I got the source for the Sense kernel, what do I need to do to make it work for AOSP?

itandy said:
Just curious, what is the difference between AOSP kernel and Sense kernel in general? If I got the source for the Sense kernel, what do I need to do to make it work for AOSP?
Click to expand...
Click to collapse
do you have the source ;o !
and you would need to build a aosp kernal based on the sense source

naathaanb96 said:
do you have the source ;o !
and you would need to build a aosp kernal based on the sense source
Click to expand...
Click to collapse
Just don't get so excited. It's just a big IF. ,-)
What do you meaning building an AOSP kernel based on the Sense kernel? I previously compiled some AOSP kernels from source but dunno about porting Sense kernel to AOSP.
Sent from my Incredible S using Tapatalk 2

itandy said:
Just don't get so excited. It's just a big IF. ,-)
What do you meaning building an AOSP kernel based on the Sense kernel? I previously compiled some AOSP kernels from source but dunno about porting Sense kernel to AOSP.
Sent from my Incredible S using Tapatalk 2
Click to expand...
Click to collapse
i think you need to compile a AOSP kernal from the sense kernal source. id private message kaijura or lord clokan or nik, being developers they would be able to tell you more do you know someone who is a htc dev or something ?

naathaanb96 said:
i think you need to compile a AOSP kernal from the sense kernal source. id private message kaijura or lord clokan or nik, being developers they would be able to tell you more do you know someone who is a htc dev or something ?
Click to expand...
Click to collapse
I wish I do but I don't
Sent from my Incredible S using Tapatalk 2

Now as the source code is available, we can hope for stable ICS rom.

Well ICS is already kind of stable just some minor bugs if you mean that. However JB would very likely be possible imo.

Our devs are working on it and I'm sure CM10 will be on our device Nik just got a port from DHD ROM booting and will release it tomorrow Also Floatshow and djpbx are building a JB ROM from source and I guess they're making awesome progress, too. So it's just about time, mate

Nice to see that my old thread has been awaken
Waiting from CM10 now.

Just a matter of time. Gonna be a fun few weeks
Sent from my HTC Incredible S

Nik got it booting!
Sent from my HTC Incredible S using xda premium

Nik released his JB rom stating he uses CM10 kernel. I understand that kernel is phone specific and does that mean we well see a CM10 alpha build really soon?

weaselEST said:
Nik released his JB rom stating he uses CM10 kernel. I understand that kernel is phone specific and does that mean we well see a CM10 alpha build really soon?
Click to expand...
Click to collapse
It doesn't surely mean that but it's possible

What about CM9. will we get it?
Sent from my Incredible S using Tapatalk 2

CM10 or CM9?

Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?

It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2

vizzy said:
It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
I'm torn between the two! On the one hand, I want a stable ROM which would be CM9, but I also love that JellyBean goodness. I've also seen some people here that simply want a stable CM9 that's up to date, and other's that want the latest CM10 despite bugs. That's the point of this thread

I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?

My vote goes towards CM9! been using codename for the past couple months and although i'm enjoying all the new features, i still find myself yearning for a rock solid & stable ASOP based build.
Sent from my Incredible S using Tapatalk 2

linezero said:
I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?
Click to expand...
Click to collapse
I could give it a try, but if nik and others couldn't get a 3.0 kernel up and running for AOSP, then I'll have a damn hard time. I'd prefer to have someone else make the new kernel, I don't know much about compiling them. Till then, I would just use X-ICS4.0 for the kernel.

Make a CM9, CM10 would have in the end too much bugs and they would just chance again. I'm waiting for a stable cm9 anyway
Sent from my HTC Incredible S using xda app-developers app

Kernel 3, Cm10 got my vote
sent from my jellybean device

ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
cm9 bro! because ics kernel source is out and bugs can be fixed!

Yeah. CM9 would be OK for me too. I can help with testing if needed.
But what would be those great JB features we would be missing out? Sry I haven't been following the differences between 4.0 and 4.1.

IncS community is desperate for at least one fully functional, bugless AOSP ROM, so my vote goes for CM9

CM9 bro..wishing for bugless one.. gud luck..
Sent from my HTC Incredible S using xda app-developers app

My 2 cents.
CM9. Kernel sources for ICS has been release by HTC and ANY AOSP rom that is stable would be very welcome in our community.
(I know there is gingerbread roms.. But.. Its ginger bread..)
Jelly Bean is nice and all,
But the odds of getting a stable AOSP rom are much higher with cm9.

CM9 I would say. I hope you can fix data problems for Vodafone NL users. We always have problems with data connection on AOSP ROMs.

CM9 would be great....!!
Its great to see devs are enthusiasticaly working on Roms..!!
You are the one dude...
Jst for info u might already aware of
This thread
http://forum.xda-developers.com/showthread.php?t=1914015
CM10 test build
Sent from my HTC Incredible S using xda app-developers app

my vote a CM9 ASOP rom and bugless
Sent from my Incredible S using xda premium

naathaanb96 said:
cm9 bro! because ics kernel source is out and bugs can be fixed!
Click to expand...
Click to collapse
Totally agree. I don't like much sense ROMs, CM9 with working camera and camcorder would be perfect!
Thanks ZaySk

CM9!!!!

ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
My request would be neither CM9 nor CM 10.... it will be great if you can work on Kernel Version 3.... Becz that is the only roadblock for us for Jelly Bean and would open doors for may developers to come up with fresh and exciting jelly bean ROMs.....Why stay behind the world guys... lets target Jelly bean step by step.....who knows if you start working on kernel it may really turn out to be good.....Try for kernel bro......all the best.. try to compile it from source....

A rock solid cm9 would be great!
Sent from my Incredible S using xda app-developers app

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