yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] tiny4579:
I screwed it up so it would boot and then go to recovery. As a result I ended up fixing the updater-script (I hope). And Pure, check your updater-script on Anthem, it tries to extract /data before mounting it. This is the reason people have issues and the VR superwipe ends up mounting /data which is why it works. Back on topic.

I'm not eliminating the kernel, I just don't think the ROM is built properly yet.

Uploaded link to dev-host:

Test ROM 303.78 MB
[Droid Incredible Android Development] Tribulattifather:
As will I.

Thanks for the upload. But I think I agree with you; i've downloaded other one v ports from dhd and a few others and it seems that you are correct. They're not building it up the same way I did. I'm going to study the architecture from these ports and try to apply what I learn.

EDIT: Okay, I got the port to bootloop.. Do you guys think that is good or bad lol. I am not really sure. Before, it was booting the animation twice, then going back to the recovery. Now it's just continuously looping over and over again. I just wish I knew if that was a good sign or not, lol.
[Droid Incredible Android Development] tiny4579:
That's the way mine's been for a while. Below is my logcat in case someone can figure it out. I tried several things and searched online regarding that android/graphics/paint error to no avail. I'm kind of done for now unless I can think of something or there's a new lead.

http://d-h.st/Ren

Also, I copied AdieHWCodecSetting.csv and TPA2018.csv from /system/etc in evervolv-ics to this ROM. It clears a few errors but doesn't get rid of the one causing the looping. Every change other than that I reverted so there's no point copying a new rom.zip up plus I don't have anything new zipped up either. I tested on the fly with adb push.
[Droid Incredible Android Development] renzo.olivares:
wait u guys r symlinking right? im pretty sure the system folder for the primo rom is to big for our system partition.....also those logcat errors are similar to the one i got when trying to port evita to htc rezound...i had to switch out the framework for the one s framework for it to boot
[Droid Incredible Android Development] tiny4579:
Yeah, I did that on my build precisely for that reason as system is only 250MB. My build is 220MB. I deleted some music files (probably don't need to) and symlinked usr and fonts and apps was already symlinked when I got it from tributallifather (sp?)

Also, where did you get the framework for One S? (I'm not familiar with the new HTC series)
[Droid Incredible Android Development] Hero:
Tiny, here's the RUU for the One S:

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

You can get the framework from here. Let me know if you have any luck with it. I'm going to be sticking with the One V just so that we have some variety and knowledge in what works and what doesn't
[Droid Incredible Android Development] tiny4579:
I wasted too much time trying to extract the darn thing. I can't figure out how to extract the system.img. If you find a usable file let me know.

I was hoping to test tonight but no time and the RUU was a waste of time as I tried unyaffs2 that failed. I don't know what format this blasted img is in.
[Droid Incredible Android Development] kinghunki:
I can help you extract. .

What files do you need? I extracted, upload it here
[Droid Incredible Android Development] tiny4579:
It's the RUU for One S. I just need the framework. Joelz in an earlier post said he had better luck with the framework for the One S than One V on his devicee (Rezound). Do you know what's causing the error in the logcat:

android/graphics/paint that leads to the device bootlooping or not booting up. Logcat is a page or two back if you're curious.
[Droid Incredible Android Development] kinghunki:
OK, I extract the framework files to you.

ONE S -RUU:1.53.401.2 CL47230 release-keys

framework:framework

If you need something, you can tell me.
[Droid Incredible Android Development] tiny4579:
It didn't seem to resolve the issue. Also the normal apks were missing such as framework-res.apk so I stuck with the ones for One V.

Is below a kernel issue or lib issue or framework issue:

W/dalvikvm( 242): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V
E/JNIHelp ( 242): RegisterNatives failed for 'android/graphics/Paint', aborting
F/libc ( 242): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
[Droid Incredible Android Development] kinghunki:
Yes. We now have the same problem.
[Droid Incredible Android Development] tiny4579:
It's the same issue on the One V framework and One S framework. Any ideas?
[Droid Incredible Android Development] renzo.olivares:
framework issue in framework.jar
[Droid Incredible Android Development] kinghunki:
Do you know how to change this?
[Droid Incredible Android Development] tiny4579:
Do you know how to fix or how it was fixed on the Incredible S? I think that port had the same problem or at least a similar error message.
[Droid Incredible Android Development] Tribulattifather:
Tried the One X's framework and got the same errors in my logcat. Well, at least we know it's a universal issue.
[Droid Incredible Android Development] tiny4579:
I think I'm making headway. I had the wrong bootclasspath in my initial init.rc. I copied it from init.primou.rc instead of init.rc. Now that that's corrected I'm checking it out again.

It looks like this:

D/dalvikvm( 89): DEX prep '/system/framework/usbnet.jar': unzip in 7ms, rewrite 353ms
W/dalvikvm( 89): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V
E/JNIHelp ( 89): RegisterNatives failed for 'android/graphics/Paint', aborting
F/libc ( 89): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

I thought it was the sim and wimax.jar stuff that wouldn't work on our phone so I removed the jar files from /system/framework and from bootclasspath. From the error above it looks to be choking on usbnet.jar now. It may not be the JAR file but I know the framework was not loading properly before but I'm not sure about now. I'll try it when I get back in about an hour (remove .jar, wipe dalvik and disable from bootclasspath).

Update on the usbnet.jar: No go.

Here is my latest boot.img (without the removal of usbnet and with the changes to bootclasspath):

http://d-h.st/Whe
[Droid Incredible Android Development] Hero:
Have you guys experienced this problem yet?

I/Netd ( 1027): Netd 1.0 starting
E/Netd ( 1027): Unable to create netlink socket: Protocol not supported
E/Netd ( 1027): Unable to open quota2 logging socket
E/Netd ( 1027): Unable to start DnsProxyListener (Protocol not supported)
E/SocketListener( 1027): Obtaining file descriptor socket 'dnsproxyd' failed: Protocol not supported

I thought it had to do with init.inc.rc so I made changes to the ramdisk and it still didn't work. This is the only error I'm getting right now
[Droid Incredible Android Development] Tribulattifather:
So wait, you're not getting the same error as tiny and myself? We're getting

D/dalvikvm( 89): DEX prep '/system/framework/usbnet.jar': unzip in 7ms, rewrite 353ms
W/dalvikvm( 89): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V
E/JNIHelp ( 89): RegisterNatives failed for 'android/graphics/Paint', aborting
F/libc ( 89): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
[Droid Incredible Android Development] Hero:
I was actually working on a separate version that I was building myself so that I would know exactly what I did and didn't do :p I'll download the latest that you guys have come up with and will have a look at the logs
[Droid Incredible Android Development] Hero:
I tried our latest release with Tiny's updated boot.img and got the same errors as before

D/dalvikvm( 89): DEX prep '/system/framework/usbnet.jar': unzip in 7ms, rewrite 353ms
W/dalvikvm( 89): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V
E/JNIHelp ( 89): RegisterNatives failed for 'android/graphics/Paint', aborting
F/libc ( 89): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

in addition to the ones I received on my build:

I/Netd ( 1027): Netd 1.0 starting
E/Netd ( 1027): Unable to create netlink socket: Protocol not supported
E/Netd ( 1027): Unable to open quota2 logging socket
E/Netd ( 1027): Unable to start DnsProxyListener (Protocol not supported)
E/SocketListener( 1027): Obtaining file descriptor socket 'dnsproxyd' failed: Protocol not supported

I only know really minimal things that have to do with framework.jar (nothing ICS related) so any help in editing it would be awesome.
[Droid Incredible Android Development] kinghunki:
I/Netd ( 1027): Netd 1.0 starting
E/Netd ( 1027): Unable to create netlink socket: Protocol not supported
E/Netd ( 1027): Unable to open quota2 logging socket
E/Netd ( 1027): Unable to start DnsProxyListener (Protocol not supported)
E/SocketListener( 1027): Obtaining file descriptor socket 'dnsproxyd' failed: Protocol not supported

These errors, you replace the "system/bin/netd" ...
[Droid Incredible Android Development] Hero:
I tried that on both builds. It didn't work...

_____________________________________

Check out my logcat. I seem to have solved our libc problem among others. The way it looks to me is that we primarily have issues with dalvikvm and Zygote which I believe to be a boot issue. Zygote failing results in this:

D/AndroidRuntime( 265): Shutting down VM

I'm going to check the ramdisk again to see if I missed anything. Hopefully once Zygote is figured out we'll at least see a boot...

P.S. My build does get to the bootanimation
[Droid Incredible Android Development] tiny4579:
Based on this post I think something was still wrong in my boot.img which is why when you switched you got my errors along with yours but you said you got further now.
[Droid Incredible Android Development] Tribulattifather:
Well done guys. Looks like Pure's going to have the first Rom port here on XDA, lol.
[Droid Incredible Android Development] Hero:
Lol I don't know about that. Either way, its still been a team effort :)

I'll upload my build or PM it to you guys if you want. I get off after 4 PST so it won't be for a while.
[Droid Incredible Android Development] SlimSnoopOS:
To be honest, I've been following your guys' comments and it's refreshing to see a collaborative effort on this just like with the Bliss port awhile back. I honestly don't know what y'all are doing but just reading and seeing the posts back and forth is about as fun as helping find bugs and helping others enjoy a rom.

I for one appreciate where this thread has gone since the OP.
[Droid Incredible Android Development] tiny4579:
I don't think I'll get to it tonight. Try uploading your boot.img that was not getting the signal 11 error regarding android/graphics/paint.
[Droid Incredible Android Development] Hero:
I didn't make changes to the boot.img yet. I was just messing around with the libs, bin, and framework. I'll upload both the ROM and the boot.img when I get back
[Droid Incredible Android Development] orfius christ:
So will this finally be flash-able?:confused:
[Droid Incredible Android Development] 5thAgent:
Probably not. Even if it does boot, it's likely next to nothing will work. Though, I'm just speculating.
[Droid Incredible Android Development] Hero:
I have the same thought as you. Once we get it to boot we can release it if trib and tiny are cool with it, but yeah no guarantees of lots of things working
[Droid Incredible Android Development] orfius christ:
Yeah, I didn't really think about functionality at the time. I honestly just want to see how the little trouble causer runs, because it would just be pure amazing to have such a new OS and UI on the ol' Incredible.
[Droid Incredible Android Development] 5thAgent:
I have high hopes for this project. It's not likely to move fast, seeing as the kernel porting is something I can barely even comprehend how to do. The ROM will come along as the kernel gets updated and troubleshot.
[Droid Incredible Android Development] Hero:
@Tiny & Trib

I just got the 5 vibs of death (also s-on :confused:) on my Dinc and am trying to fix it so I won't be able to get the build up until that is finished. If you can, try moving some of the system/bin files from evervolv into our port and see if you can make any advances. also, I think the bootclasspath in init.rc is a little off so you may want to check that again.

EDIT:

I fixed the phone! Going to resume One V development
[Droid Incredible Android Development] kinghunki:
Hope to have new progress. .
[Droid Incredible Android Development] Tribulattifather:
I'm really glad that you fixed it, man. Would you upload your port for us. I'd like to try something in the bootclasspatch. I've been researching a lot about it and I have a few ideas.
[Droid Incredible Android Development] Hero:
Yeah for sure. I'll upload it when I get home today
[Droid Incredible Android Development] orfius christ:
Wait so is this port actually running or is it still all stuck at boot loop and such?

Throwing in my thoughts from the incredible
[Droid Incredible Android Development] Ruggerxpunk:
Pretty sure nothing boots yet past boot animation.
[Droid Incredible Android Development] Hero:
This build contains a modded framework.jar, swapped files in system/bin and system/etc, and a boot.img (ramdisk) with a revised bootclasspath in init.rc. It gets to the boot animation, but does not get any further than that. The Zygote issue is becoming so problematic, I don't really know how to fix it ATM.

One V hTC Incredible port

I attached the logcat for this build.
[Droid Incredible Android Development] Tribulattifather:
Thank you again, Pure.

Just to keep everyone updated, I added the new RomUpdateUtility (uploaded not even a day ago) to the first post.

Edit: I downloaded your project port, Pure, and I got errors when extracting. I got the boot.img which is what I was really wanting anyhow, but, thought I'd just let ya know..

See attachment pic:
[Droid Incredible Android Development] Hero:
hmm thats weird... i think im going to use the newest ruu you uploaded and try to get the port going. ill upload it once i finish, which shouldnt take too long. going to try some new stuff. if you mod the boot.img do you think you could upload it so i can try it?
[Droid Incredible Android Development] Tribulattifather:
Hm, I think we have the best possible boot.img tbh. But if I do anything I will def upload.
[Droid Incredible Android Development] withbloodskies:
Chance out of 100%, what do you think the chance of this running is? It sounds like its slightly possible?
[Droid Incredible Android Development] Tribulattifather:
49%

10-Char
[Droid Incredible Android Development] withbloodskies:
Well.. better then I thought, I hope it can work. Either way, great job guys. Outstanding teamwork.
[Droid Incredible Android Development] Tribulattifather:
Well, I'm trying my last idea tonight. Been working on this all day getting no where, lol. *Crossing my fingers*

I'll report back in a sec after I boot my latest port up.

Edit: Literally installing right now. and got a status 0 error. Yaay :rolleyes:

2nd: Okay. Trying something else. Let's do this again, lol.

3rd: Had another error durring installation. I have a good idea in my latest port, just not sure what is wrong inside the ROM that is causing the error. I'll pick where I last left off tonight later on tomorrow. Good night all, See ya in six to eight, lol.
[Droid Incredible Android Development] Hero:
Sounds good lol. I'm downloading the RUU right now and will work on it when it finishes. Hopefully we can eventually get this out :p
[Droid Incredible Android Development] Hero:
Something I just came across...

After extracting the files from the RUU, I tried to deodex them and was given lots of errors. I don't know why this is, but the fact that I get errors while deodex-ing could be attributed to the errors we've been receiving in our logcats while trying to boot the ROM. I'm going to try and make an odexed version of the ROM and see if anything changes. And tbh, I have a good feeling about this. I don't know why, but I do lol
[Droid Incredible Android Development] Tribulattifather:
How'd your idea go?

Mine >.> hasn't worked yet, lol.

I've got a few more idea's up my sleeve though ^>^.
[Droid Incredible Android Development] Hero:
I haven't gotten a chance to test it yet, but I will soon. Check your PM!
[Droid Incredible Android Development] tiny4579:
How's it going guys? If we do get stuck we can check with joelz or try his suggestion but do a separate port on like the 3rd, 4th, or 5th page, I don't remember which. If you dump a logcat, I'd be glad to look at it and provide some input. I may not have any solutions but I'd like to try.
[Droid Incredible Android Development] Tribulattifather:
I tried your idea you gave me in my P.M. I just can't get it to install.

I'm going to upload it and maybe you guys can help me try to figure out what is wrong in the updater-script.

I get a status 7 error in the recovery saying it's expecting 4 args and getting 3..

I'm uploading it now.

Edit: Here's the updater-script (the Rom will be up in about an hour or so, I get the problem at mounting).
[Droid Incredible Android Development] tiny4579:
What are your format and mount system lines like? That is likely the problem. Try these below:

format("yaffs2", "MTD", "system", "0");

mount("yaffs2", "MTD", "system", "/system");

I found them in the evervolv updater-script.

Also, just push it as a .txt file to your post as I can't download it.
[Droid Incredible Android Development] Tribulattifather:
Sorry about that.

I'm trying to install now too.

P.S. Grats on the 2k post count.
[Droid Incredible Android Development] nitsuj17:
sense ics needs to be deodexed with api 15....if you use dxidia's kitchen its an option under deodexing...or if you do it manually you need to do -a 15 in command line

some apps wont properly deodex (phone.apk comes to mind) with smali/baksmali 1.3.2 (latest official)...however i built 1.3.3 and it works to deodex the rest of the missing apps...that should work for ya

althoug deodexing on the priority scale is way down if you the rom isnt booting yet :p
[Droid Incredible Android Development] Hero:
I spoke to Joel about the issue we were having with the framework.jar and he said that we would have to do this to solve the paint issue we've been having.

Oh I've never heard of that, but good to know lol. Do you have any experience with this error?

W/dalvikvm( 242): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V
E/JNIHelp ( 242): RegisterNatives failed for 'android/graphics/Paint', aborting
F/libc ( 242): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
[Droid Incredible Android Development] tiny4579:
OK, I have an idea I wanna try. Can someone post a zip of the system folder extracted from the latest RUU? The mirror to download the full RUU is not accepting free downloads.

Here's what I wanna do:

1. Take odexed ROM and my current boot.img and double check my updater-script.

2. Rearrange folders to match the updater-script and to make it fit on the 250MB system partition.

3. Follow this thread for porting (confused though about it) - credit to puremotive for finding:

http://emexci.com/2012/04/12/how-to-port-sense-4-0a/
[Droid Incredible Android Development] Hero:
I can upload it when I get home today. It'll be around 3PM PST
[Droid Incredible Android Development] Hero:
Something to be aware of is that the Evervolv ROM doesn't have all of the components listed on the website that are used for porting, but what I did was just take all the files I could find and move them over into the port.

I didn't try taking the files from Primadonna yet though, because I'm guessing it wouldn't work. But it would be something to try since we pretty much have nothing to lose
[Droid Incredible Android Development] Hero:
Here is the system folder from the latest RUU: One V /system
[Droid Incredible Android Development] Tribulattifather:
I also have mirrors on the first post of the original leaks framework and apps that aren't deo'd.
[Droid Incredible Android Development] Hero:
So I fixed the fatal error that had to do with libc, but have encountered another... If anyone can help determine what file needs to be edited then that would be greatly appreciated.

W/dalvikvm( 90): Exception Ljava/lang/NoSuchMethodError; thrown while initializing Landroid/database/sqlite/SQLiteDatabase;
E/SqliteDatabaseCpp( 90): Can't find SQLiteDatabase.mNativeHandle
E/AndroidRuntime( 90): Unable to register all android natives

I really just don't know where SqliteDatabaseCpp is located
[Droid Incredible Android Development] tiny4579:
I did a bit of searching. I think sqlitedatabasecpp is actually part of core.jar in /system/framework. I have doubts about trying to replace it.

Try replacing the libsqlite_jni.so first and then libsqlite.so if the first doesn't work (from evervolv).

It's also possible that what was done to fix the libc error or at least get rid of the error caused the new error.

Just checking but you didn't try deodexing the ROM did you?
[Droid Incredible Android Development] Hero:
I did deodex it. I'm starting over on a new build a completely new build. So far I've rewritten the framework.jar (to remove the libc.so error) and the ramdisk. I'll check out core.jar and see if there is anything I can fix. And I agree with you, I think fixing the libc caused these new errors and it's going to keep on going like that (domino effect), but it seems as though we are going to have to rewrite as much of the framework as possible to get this to work :/

...just gotta find out where the files are lol. I'll look into the core.jar now
[Droid Incredible Android Development] tiny4579:
Deodex should be fine as long as it's using the new api level 15 as that one dev mentioned (I knew nothing about that beforehand).

What do you mean by re-writing the files?

Also the files I mentioned in my previous post are /system/lib.
[Droid Incredible Android Development] Hero:
I mean just editing the code in the .smali files in the .jar files. I'm changing it up so that it works with the port and produces the least number of errors.
[Droid Incredible Android Development] Hero:
I was unable to find sqlitedatabasecpp in core.jar so I think I'm just going to look through more of the .jar files. the sqlitedatabasecpp error still remains as the only error despite swapping the lib files
[Droid Incredible Android Development] tiny4579:
It wouldn't be in core.jar as that file name. Core.jar just has Java stuff. Unless you meant the smali file.
[Droid Incredible Android Development] Hero:
Yeah, the .smali file
[Droid Incredible Android Development] Tribulattifather:
Guys, I am going on spring vacation with the family for a week. I'll be able to keep updated on what you all are doing just will only have my phone with me so I won't be able to help til i'm back.

Thanks again,

Brad.
[Droid Incredible Android Development] mushat3k:
Be safe on vacation dude

Looks like HTC has released the kernel source code for the one v, hopefully this will be helpful

http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
[Droid Incredible Android Development] TokedUp:
http://www.xda-developers.com/android/htc-one-v-ruu-and-kernel-source-released/
[Droid Incredible Android Development] nitsuj17:
its a common misconception that one v kernel source will make a difference...it really wont for the vast majority of rom porters....i suppose its possible (though unlikely) that some kernel dev can pull and backport some stuff

but its not gonna magically fix things

the phones that will eventually have the most functional (or already have them) sense 4 ports are ones that have or will get official ics from htc/carriers and get source for 3.xx kernels

the best that non official ics htc phones can do is probably the current state of say the dhd/msm7x30 ports using the .35 kernels
[Droid Incredible Android Development] Newt:
If I get time this week ill take a look at this... But I'm almost 90% sure it'll never boot on the older hw.... If it does boot what it will take to boot it will make it so unstable that it won't be usable at all, but ill check it out for you guys