yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] orfius christ:
Jesus amazing! Seeing those words from newt just made my hope rise :D
[Droid Incredible Android Development] Alton (Halo 2):
Wats up incubus !!
[Droid Incredible Android Development] Hero:
Newt that'd be great. I'm going to try to get it to boot on my own as well. Thanks for taking the time to help us out. Also, Shaky requested that I not release my (technically your) ICS Sense ROM (if it's based on his) for the next week. So I guess that gives us time to work the kinks out.
[Droid Incredible Android Development] LunaticSerenade:
Good lord. Everywhere I look, there you are! Super pumped!
[Droid Incredible Android Development] withbloodskies:
Okay I'll admit it, I screamed in the inside lol.

Its like at fingers reach taunting us
[Droid Incredible Android Development] Newt:
Thought you fell off the earth bro
[Droid Incredible Android Development] ca1ne:
A minor note, platypus over in the evo section has a booting sense 4.0... I know our phones port back and forth for the most part.. Might want to hit him up as well..
[Droid Incredible Android Development] tiny4579:
Which was probably ported from desire. We can port straight from desire once we have permission which I plan to help pure with except I can't test phone/data/SMS.
[Droid Incredible Android Development] jioleight:
http://www.technobuffalo.com/compan...-budget-android-smartphone-packing-beats-ics/ cheap phone w/ Sense 4, beats audio
[Droid Incredible Android Development] withbloodskies:
Lol.. that phone.

Anyway it said 5mp, is this some type of ics issue?

Galaxy Nexus has a 5mp aswell, not sure about the one series but I'm just curious.
[Droid Incredible Android Development] jioleight:
that, i can't answer. :-D
[Droid Incredible Android Development] LunaticSerenade:
To my knowledge, the ICS that is working on the Rezound is still 8MP. I think manufactuers are just lazy.

Idea Guy: "so, should we put in an awesome camera?"

Engineer: "man, that sounds like work. Do I have to?"

Idea Guy: "guess not...no one will notice anyway."

:D
[Droid Incredible Android Development] enomele:
Incubus is so bad ass that he gets thanks for saying hello. :D
[Droid Incredible Android Development] amit.shah:
Shaky has updated his ROM to ALPHA v0.2 and mentioned about Multidevice script supporting our beloved Dinc in changelog http://xdaforums.com/showpost.php?p=26396650&postcount=258
[Droid Incredible Android Development] withbloodskies:
Kinda curious how development has been going then.
[Droid Incredible Android Development] Hero:
For Shaky? Development has been going great hence the popularity of his thread not to mention he is one hell of a dev. Me, Tiny, and Trib are still working on our own Sense 4.0 port for the DInc since I refuse to kang/semi-kang Shaky's work despite him giving me permission to use his ROM as a base :P Regardless, his work is top-notch and Amarullz's Aroma Installer is pretty beast :D

Development for us is a little slow I'm afraid. I've contacted the dev of the Evo ROM for some help on a question. Once/If he responds, I hope to get Sense 4.0 up and running (and optimized (as much as possible)) for our phone.
[Droid Incredible Android Development] tiny4579:
Can you contact me on gtalk?
[Droid Incredible Android Development] Hero:
Started a chat, but I'm gonna go to bed soon since it's 3AM.

***PM me dude. I can't manage stay awake any longer lol
[Droid Incredible Android Development] withbloodskies:
Well it sounds like it's going good. Excited to hear the word boot pop up lol.
[Droid Incredible Android Development] Hero:
Booted! :D

I'll get you guys a better picture later. I'm too excited to concentrate :p
[Droid Incredible Android Development] SlimSnoopOS:
(starts singing) toot it and boot it!
[Droid Incredible Android Development] Alton (Halo 2):
Let's go pure ! Ur a pro !
[Droid Incredible Android Development] Tribulattifather:
Grats guys. I'm proud to be among developers/chefs like you all.

But, the reason why this sounds like a 'Goodbye,' is because it is. I just got a new phone and sold my good ol' INC. I'll be available for anyone who ever needs me. Don't be afraid to 'drop me a line.'

Thank you Pure and Tiny for making probably the best team i've ever worked on. And thank you to everyone else too.

Bye guys. I will always drop by this thread to keep updated on all of your progress, but now I go to the 3VO 3D fora and figure out how to root ^>^

:o
[Droid Incredible Android Development] tiny4579:
Alright best of luck on your new phone. I couldn't part with my Inc when I got my Nexus. I guess I'm still too attached to the Droid Incredible community and there's so many devving on the Nexus I don't feel I have anything new to bring to the table. Plus it's more fun to work on a phone that I can risk bricking as there's no active line.
[Droid Incredible Android Development] Hero:
Some news to keep you guys updated:

Good

SMS works

3G works

270 Rotation works

It's pretty damn fast :D

Bad

still testing...
[Droid Incredible Android Development] LunaticSerenade:
I am so excited...and my Inc is only for music and alarm clock!
[Droid Incredible Android Development] withbloodskies:
That one word.. speed. That's what I've been waiting to hear, thank you!

Can't wait to try yours and shakys version.
[Droid Incredible Android Development] Hero:
Feels like Sense 2.1 lol
[Droid Incredible Android Development] :
Imo its 10x better than 2.1 :p

Sent from my HTC Desire HD
[Droid Incredible Android Development] rayado:
I've read that Sense 4.0 is "lighter" than previous Sense Versions. Would the size of the zip file be smaller as well?
[Droid Incredible Android Development] Hero:
Yep, it's about 270mb
[Droid Incredible Android Development] withbloodskies:
Wow.. if that's the case then this thing will be a beaut when everything or almost everything works huh?

Estatic to hear its as fast even faster then 2.1, currently what I'm running.
[Droid Incredible Android Development] tiny4579:
Keep in mind this is also a port of the slower One V so it won't have all the fancy animation effects. But it is smooth. I like the transitions and it may be quicker than AOSP ICS.
[Droid Incredible Android Development] jioleight:
so, any updates pure? :)
[Droid Incredible Android Development] Hero:
I'm going to put up the thread in a bit (just waiting for Tiny so he can reserve a post (if he wants)). I made the ROM smoother than it already was, but right now not much works unfortunately, we're working on getting WiFi and data fixed as fast as I can.
[Droid Incredible Android Development] withbloodskies:
Yeah I would figure Data/wifi would be first.

Hoping music/storage will be fixed afterwards. I've been dying to try out the new music player and audio.

Just curious, will we have to used hacked libs or audio hardware to get it to work properly?

I was going to reflash shakys again and mess around with libs and some other files, but if it runs deeper than that I won't be able to do anything lol.
[Droid Incredible Android Development] tiny4579:
We have our own thread now for the ROM but we're still trying to fix data/wifi.
[Droid Incredible Android Development] jioleight:
so any devs working on a build based on this?
[Droid Incredible Android Development] withbloodskies:
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!
[Droid Incredible Android Development] Hero:
I'm helping him with the project and I think Tiny is going to take a look at the kernel (?)
[Droid Incredible Android Development] tiny4579:
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.
[Droid Incredible Android Development] Tribulattifather:
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.
[Droid Incredible Android Development] nitsuj17:
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 :p

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

hope you guys get it worked out
[Droid Incredible Android Development] Tribulattifather:
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 _-_ ).
[Droid Incredible Android Development] nitsuj17:
whats the log saying when it doesnt boot? does it at least make it to boot ani?
[Droid Incredible Android Development] Tribulattifather:
HERE is the newer port.

I have used a different AOSP ICS CM9 zImage,

Changed a few things in the updater-script,

and deodexed a few more apps that I quite couldn't get to work before.

I don't exactly get to a bootanimation, but it does change the screen right after initially booting.

However,

adb logcat -v long > C:\users\mine\desktop\logcat.txt

doesn't let me see any info.

What is the best way to get a log?
[Droid Incredible Android Development] nitsuj17:
check in the terminal first to see if logcat is even running ie

adb logcat

if its spitting stuff out then stop it and output

adb logcat > whateveryouwanttocallit.txt
[Droid Incredible Android Development] Tribulattifather:
Nope. Doesn't connect. It looks for device and never connects.
[Droid Incredible Android Development] tiny4579:
I won't have time on this project tonight as I decided to try and get beats audio working on my newer sense kernels for roms that support it. No success so far.
[Droid Incredible Android Development] WildZontar:
I've never heard of anything like this before. Are you trying to port a newer phone ROM back to the Inc? Is this possible or feasible?
[Droid Incredible Android Development] Tribulattifather:
Yes. If we figure out the kernel issue. I have the rom already ported, just doesn't boot yet.
[Droid Incredible Android Development] nitsuj17:
ummm, every sense 3/3.5 (and before that sense 2.0/2.1) rom you have on the inc was "ported" to it...so yeah its possible
[Droid Incredible Android Development] renzo.olivares:
Most of my ports were from the desire hd...use libs from evervolv and cayniarbs hw acceleration kernel...and u also need the bootclasspath to match the one v's
[Droid Incredible Android Development] renzo.olivares:
I'd be willing to help but no longer own an inc but can still help contact me joelz9614@gmail.com
[Droid Incredible Android Development] Tribulattifather:
I have to be honest here. I mainly make apps and older rom ports for devices like the HD2, DInc and the Herald/Wing. I've never really worked with kernels, so when you say:

I understand how to do two out of the three you mentioned above (-I don't know how to match the One_V's bootclasspatch).

If you'd be willing to help us, I know we'd all be greatful. Do you need any files? I have a lot on the first post.
[Droid Incredible Android Development] tiny4579:
I think I know what Joel is talking about. As far as which libs are needed from the ics evervolv I wouldn't be too sure. I've messed with bootclasspath in the ramdisk before. Can check this evening. Is the port on one of the previous pages your latest attempt?
[Droid Incredible Android Development] Tribulattifather:
I actually just edited the first post with my latest.
[Droid Incredible Android Development] tiny4579:
I think I'll have something up in a bit. I copied the lib folder from evervolv, used the ramdisk from evervolv with the bootclasspath entry from OneV and had to make changes to the updater-script to allow adb shell and I'm trying something right now to see if it will boot. If unsuccessful I'll try to get a logcat at the very least. I got it to the bootanimation (stock android) and then decided to try something else.
[Droid Incredible Android Development] Tribulattifather:
This is very exciting news indeed. I messed up something on mine. I got a boot ani and then i tried to do something else and it doesn't go now lol. I want to kick myself for not making a backup of it. I usually copy it into my Android ROM Folder right before I make an adjustment. I'll post my port if I get it back to the animation.
[Droid Incredible Android Development] tiny4579:
I think I did the same thing. I'll post a logcat if I get something up.

Second day in a row I try to do something awesome and fail.
[Droid Incredible Android Development] Tribulattifather:
Na. You only can learn by failure.

Edit: Well, I can't figure out how I got it to the ani.. I'm gonna get some sleep and I'll see you all tomorrow to retry some more.
[Droid Incredible Android Development] :
This is a qsd soc device too O__o

patience :P

Thanks to the desire commuity, I'll be getting my hands on a desire, I'll then be able to do some more deving on this soc
[Droid Incredible Android Development] renzo.olivares:
bootclasspath is in the bootimgramdisk inside the init.rc..im not sure what primo's bootclasspath is...basically what u need is the egl folder from evervolv.....the hw folder from them.....might need the libui.so libsurfaceflinger.so and libsurfaceflinger_client.so...libEGL.so..libgsl.so ......libOpenVG.so libsc-a2xx.so....libC2D2.so...play with those.....libui and the surfaceflinger i do last.....also some other libs to note are liboverlay.so libgenlock.so libtilerender.so libqcom.so...
[Droid Incredible Android Development] Hero:
The bootclasspath for the Primo is this:

/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/VirtuousExtension.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/filterfw.jar:/system/framework/com.htc.android.bluetooth.jar:/system/framework/wimax.jar:/system/framework/usbnet.jar:/system/framework/com.orange.authentication.simcard.jar

Will work on it more tomorrow...
[Droid Incredible Android Development] tiny4579:
Well, I figured out what I did wrong last night after I fixed it and broke it. I was using my initial boot.img which was from primo which when it was working I was using evervolv's boot.img with the bootclasspath from primo. Now time to dissect this logcat and update libs.

EDIT: Ok, so it seemed simplest and what worked the best was copying the entire libs folder from evervolv. I've gotten my flashable zip to the point where at least it will display the bootanimation.

adb shell and logcat work too.

Here is my logcat, maybe someone can figure it out. I'm taking a break for now:

http://dl.dropbox.com/u/31805083/logcat.txt

My current ROM is below.

http://dl.dropbox.com/u/31805083/sense-ics-inc.zip

Update (10:42 EST): All files uploaded.
[Droid Incredible Android Development] Tribulattifather:
Thank you.

Do mind if I post your work on the O.P. (and mind if I use your work)?
[Droid Incredible Android Development] tiny4579:
Go for it. This is not really for me as much it is you all.

Joelz's method may be best for getting it to boot but at least the graphics are loading if I have the stock animation.

I just don't want the dropbox to be a primary mirror for dev's to download to work on it (might flag something with dropbox due to bandwidth but may not if it's just a few people), so if you're going to link the dropbox make sure you note to only download if they're going to work on it.

I actually think there are jar files in the ROM and bootclasspath that don't necessarily need to be there (mainly the ones about SIM but better leave in there to be safe).
[Droid Incredible Android Development] Hero:
I believe we are still having an issue with the kernel. From the logcat, there's this line:

F/libc ( 219): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

which indicates that this lib file (libc) is experiencing an error in the kernel. Not too positive though :/
[Droid Incredible Android Development] tiny4579:
I just checked the logcat. The problem and I just verified is that /data/system.app, /data/system.usr, and /data/system.fonts didn't extract. I'm going to try and push them manually and see if that helps.

This may not still get the ROM booting but it will correct a definite problem.
[Droid Incredible Android Development] kinghunki:
You merge JAR and ODEX do not have?

---------- Post added at 12:45 AM ---------- Previous post was at 12:41 AM ----------

Yes, we are now experiencing the same problem. . .
[Droid Incredible Android Development] Tribulattifather:
Ill do the same.

Not sure what you mean when you say "You merge JAR and ODEX do not have?"
[Droid Incredible Android Development] kinghunki:
Now the jar+odex, or only the jar? This can be understood not? Sorry, English is hard for me to express. .
[Droid Incredible Android Development] tiny4579:
I never messed with JAR or odex but there's a problem with the JAR files in /system/framework. None have classes.dex in them.

I have updated my logcat.txt so the link will download the latest.

Both JAR and odex files are in framework but the JAR files just have META-INF folder. That doesn't seem right. Also, the apks in /system/framework have no classes.dex in them.

Tribulattifather, can you upload the original framework folder from the leak so I don't have to download the whole leak. Something seems wrong in the framework copy of the port attempt you posted.
[Droid Incredible Android Development] Tribulattifather:
Oh. Sorry. I deodexed the whole rom. Should be only jar.

I'll update the O.P.
[Droid Incredible Android Development] kinghunki:
I think you can try to replace the “system\bin\dalvikvm” look at will change. .

I downloaded your ROM to see if there is nothing that can help each other. .

Edit:I am sorry, and now time is 1:00, I go to bed. Tomorrow I will continue to pay attention to this post
[Droid Incredible Android Development] tiny4579:
This message from the logcat indicates to me that the framework is jacked up:

I/dalvikvm( 261): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory

There are .odex files in /system/framework but it doesn't like them. Do you have a copy where you didn't try to deodex /system/framework? I just need the framework folder.
[Droid Incredible Android Development] Tribulattifather:
Hmm, so either when i deodexed something happened or when i ported something happend.

Edit: I just deodexed the original leaks apks and jars. When I do this with the new smali and the older versions the same things happen. We may have to find another way of deodexing or just leave the odex files as is.

I'm going to upload the original framework folder from the leak.
[Droid Incredible Android Development] tiny4579:
The /system/app .apks which are symlinked to /data/system.app look normal though.

I hope this works, at least to have it boot.

FYI, my public dropbox is suspended. Do you know how much traffic is needed to cause it to be suspended? It wasn't even that high. Speeds are also good on dropbox.
[Droid Incredible Android Development] Tribulattifather:
Mine was suspended for three days once too. But that's all it takes for it to go back. And they make you read something when they're ready to let you use it normally again.

I can't believe with the few of us downloading that it would get suspended, though. I posted my servers links on the O.P. too fyi.

Also, I'm uploading the framework folder now.
[Droid Incredible Android Development] Hero:
Are all of the files odexed? If so that's why there are no classes.dex
[Droid Incredible Android Development] Tribulattifather:
Okay. Lets add the original odexed framework and app folder. Might boot if we do this.

I've never done this before, but has anyone ever left the framework odexed and the app folder deodexed in a build? I mean i've only ever either deo'd or not, lol.

Here's the Framework folder.
[Droid Incredible Android Development] Hero:
I've only done one or the other, but normally I deodex just in case I need to edit something
[Droid Incredible Android Development] Tribulattifather:
Yeah. That's exactly what I do too.

I'm uploading the original app folder as well.
[Droid Incredible Android Development] tiny4579:
I don't think we need the odexed app folder as it looked normal but it doesn't hurt.

I can't hit the host. It doesn't ever load after waiting like a minute.
[Droid Incredible Android Development] Hero:
If you guys are still having hosting issues with dropbox I can host our project on the server where my roms are.

Ill have to do it later though because I'm at work
[Droid Incredible Android Development] Tribulattifather:
That'd be cool. As my net bandwith is so slow and tiny's DB is disabled atm, lol. Sorry about that, Tiny. Took one for the team there, heh.
[Droid Incredible Android Development] Hero:
Alright I'll do it in like 4 hours @_@
[Droid Incredible Android Development] mushat3k:
Thanks for the time and attention on this guys, can't wait to see what comes out of this!

sent from my incredible
[Droid Incredible Android Development] Tribulattifather:
Okay. The original Framework and App folder are on the O.P.
[Droid Incredible Android Development] tiny4579:
I just downloaded the ROM here to get my framework files:

http://xdaforums.com/showthread.php?t=1545595

Now I'm getting this error below which I think is the reason it's not booting now:

W/dalvikvm( 347): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V

E/JNIHelp ( 347): RegisterNatives failed for 'android/graphics/Paint', aborting

F/libc ( 347): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

From a bit of googling and based on the error name that is probably a lib issue somewhere. (Maybe that's why Joelz mentioned copy only a few libs at a time from evervolv).
[Droid Incredible Android Development] Hero:
I saw that port as well and I was using portions of it for my test build. I googled the error that has to do with libc and it appears to be connected to a problem with the kernel. I'm not too sure about it, but if all else fails then we should look more into the kernel
[Droid Incredible Android Development] Tribulattifather:
I think we can fix the libc issue. Not sure about the other two.

But, can one of you upload your port at a later time when you're not busy; I am getting a lot of errors in my logcat now that I tried a few things to your port, Tiny.

Forgot to backup again :o
[Droid Incredible Android Development] tiny4579:
It is in fact a memory issue and the cause is I think something's not right in the libs.
[Droid Incredible Android Development] Hero:
Alrighty I'll look into the libs more then