Well.. pretty much every good sense dev has left the og dinc.
Tribulattifather I'm assuming is going to try and get this running with a fair amount of help and kernel support. If it does run sometime soon, it would be amazing but don't hold your breath.

We only have a few good devs supporting the dinc still, either way this is a godsend and I'm hoping it runs smooth considering the specs in One V. It's actually kinda amazing, ics+sense combo and its running off 512ram. I think we will just have a problem with things working.

Either way huge thanks to Tribulatti for bringing this, here's hoping for the best!

I'm helping him with the project and I think Tiny is going to take a look at the kernel (?)

I''ll have to try to look at this this afternoon.

While not an expert on roms, I think we may be best off starting with a GB ramdisk and hacking at it to get it work. Still keep the AOSP ICS zImage (kernel) thouh. I would think a Ramdisk from a Sense 3.5 ROM may be a good starting point and the zImage should be from a stock AOSP ICS kernel such as the one included in cm9 or abduction 2.0. If we get stuck maybe we could nicely ask nilsp or newtoroot or joelz for help.

While not an expert on roms, I think we may be best off starting with a GB ramdisk and hacking at it to get it work. Still keep the AOSP ICS zImage (kernel) thouh. I would think a Ramdisk from a Sense 3.5 ROM may be a good starting point and the zImage should be from a stock AOSP ICS kernel such as the one included in cm9 or abduction 2.0. If we get stuck maybe we could nicely ask nilsp or newtoroot or joelz for help.

Not a bad idea at all, mate. I will start doing this immediately. And hopefully some of the og chefs/devs will take a look at this too.

While not an expert on roms, I think we may be best off starting with a GB ramdisk and hacking at it to get it work. Still keep the AOSP ICS zImage (kernel) thouh. I would think a Ramdisk from a Sense 3.5 ROM may be a good starting point and the zImage should be from a stock AOSP ICS kernel such as the one included in cm9 or abduction 2.0. If we get stuck maybe we could nicely ask nilsp or newtoroot or joelz for help.

the method used on the msm7x30 devices (wont work as easily for older ones) is this:

any zimage from an ics aosp rom is fine (actually any zimage from gb cuz theyre all .35 anyway is fine but the ics ones have edits in them for some changes)

in the one v ramdisk you need to rename any of the files with "primo" or whatever to "inc" ie init.promo.rc

from there the rom boots for us on msm7x30 (inc s, inc2, dhd, ds, et all)...obviously a lot more changes are made to the ramdisk afterwards but step 1 is to get it booting first

i had originally planned to work on it, but my android time has been cut significantly lately, and the inc2 is my priority

That is exactly what I did. But I did notice a flaw in my design, so i'll be uploading a new port with fixed files soon. I hope it doesn't take hours like last night being as no one should be online atm compared to last night (DSL _-_ ).

That is exactly what I did. But I did notice a flaw in my design, so i'll be uploading a new port with fixed files soon. I hope it doesn't take hours like last night being as no one should be online atm compared to last night (DSL _-_ ).

whats the log saying when it doesnt boot? does it at least make it to boot ani?

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?