yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] mingolianbeef:
Do you have a logcat for this latest build, or r u referring to the Dec.23 build.? I'm not a good dev when it comes to sense at all but I still would love to try and contribute in any way I can
[HTC EVO 3D] Tribulattifather:
Yes. There is a libc error if you let the logcat go for a long time.

Same as dec. 23rd.
[HTC EVO 3D] beneath-a-burning-turtle:
Actually changes were made to the Dec. 23rd one because it wasn't getting past system/etc/soundimage, don't know if you picked up on that with the many things I had you switch and whatnot lol
[HTC EVO 3D] Tribulattifather:
True. I downloaded the 23rd one and still got that fatal error.

I didn't want to upload the one we have now because we mixed too many libs and got that memory error..

Hopefully, Newt will be available to help figure this one out with us soon.
[HTC EVO 3D] sellers86:
You know what, ill be bored tomorrow at some point, ill see if I can help. :)

EDIT: Im pretty sure that libc error is actually a memory error. I will look into it more tomorrow.
[HTC EVO 3D] VictoriousShooter:
Does the memory error have to do with the size of the system partition?
[HTC EVO 3D] beneath-a-burning-turtle:
The libc error is a signal 11 (segmentation fault), caused when there's a read/write/execute callback issue, usually when the system tries to access a memory location that's not assigned. I'm gonna run an addr2line (I think thats what its called) on libc.so when I decide to get out of bed lol
[HTC EVO 3D] sellers86:
Exactly, its a memory error :p
[HTC EVO 3D] beneath-a-burning-turtle:
Just thought I'd expand on it for ya lol
[HTC EVO 3D] ramjet73:
Alright! Now we're cooking.

I don' speak Chinese but Google translated the page linked from that thread and I've attached the specs for that update (3.14.709.102).

And the screenshot speaks for itself. ;)

ramjet73
[HTC EVO 3D] sellers86:
I appreciate it :)
[HTC EVO 3D] beneath-a-burning-turtle:
Just outta curiosity, what do you think is causing the error? And if you wanna bounce ideas or anything you can get me on gtalk, I have a few ideas myself.
[HTC EVO 3D] Tribulattifather:
I've decided to start over from scratch.

I'm porting from scratch too instead of letting the kitchen do the work so I know exactly what it is that I've done.

I'll upload tonight with a logcat once I get past the easy errors that are fixable.
[HTC EVO 3D] sellers86:
I'm thinking dalvik iis crashing honestly. PM me your gtalk
[HTC EVO 3D] VictoriousShooter:
The Ville c2 now has jb. It's the one with the s3.
[HTC EVO 3D] ______:
If this work out I'd try to make it work on GSM. So far no one even tried to port sense 4+ to EVO 3D.
[HTC EVO 3D] beneath-a-burning-turtle:
I would think it'd be easier to get it on gsm first honestly, since the one s is gsm, and we're porting to cdma

Also your username is by far the most creative I've seen. That **** is pretty awesome lol
[HTC EVO 3D] Tribulattifather:
If it wasn't a banable offense, and the fact that I used to moderate, I'd create a name that is like __Name_goes_here__, lol.

Back on topic:

I'll grab ahold of that gsm rom and see what I can do.
[HTC EVO 3D] ramjet73:
Someone posted a link to the OTA zip file if you haven't seen that already. I grabbed it in case the link goes down.

ramjet73
[HTC EVO 3D] xxbabiboi228xx:
If those kernel devs out there can make a kernel thats universal cdma/gsm I don't see why you guys couldn't get this working on the cdma EVO 3D.
[HTC EVO 3D] 1ackass:
It would be easyer to port from the one S gsm phone to gsm version of evo3D, AND then it would be easier to port to cdma.Atleast that would be my logic :D
[HTC EVO 3D] Tribulattifather:
Well, here it is:

http://goo.im/devs/Tribulattifather/Sense 4.5/Dec_31

This is the port that Chris and I have in our hands right now.

There is a logcat also in the link.
[HTC EVO 3D] pancho32392:
OMG O.O
[HTC EVO 3D] Tribulattifather:
It's not bootable yet ^>^

This is for the devs that can help or the ppl who can read logcats and see what is next to do to figure out what can make it boot.

Right now it's stuck at the bootanimation.
[HTC EVO 3D] Flashalot:
After cleaning again my work folder still a no go boot logo

Note to any body is add one lib at a time
[HTC EVO 3D] ______:
:) glad some1 appreciates the nick i use.

some mod delete my acc on the other site just because it can't be pronounced. he said it's an offense to the "community harmony" becuz others wasn't able to speak it...wtf?!

anyways, not really a android/java guy here, but will see what's next then. keep up all the good work!:good:
[HTC EVO 3D] ramjet73:
Things are more flexible here. We'll just call you "blankety-blank". ;)

ramjet73
[HTC EVO 3D] beneath-a-burning-turtle:
We've narrowed it down to that being the problem. We just don't know how to fix it lol
[HTC EVO 3D] Indirect:
I'll look into it when I'm home tomorrow if I don't go to the beach. ^^
[HTC EVO 3D] beneath-a-burning-turtle:
Sweet, we've been trying for days with no avail, we need whatever assistance we can get
[HTC EVO 3D] iDannyPR:
maybe the program accessed a memory location that was not assigned

Edit: sorry didnt saw that was posted.

I will look in other sources for you guys :)

-iDanny
[HTC EVO 3D] beneath-a-burning-turtle:
Were you quoting me to me? lol

We don't really know how to go about fixing it, which is the issue.
[HTC EVO 3D] Tribulattifather:
After I upload my Senes 3.6 ver 4_0 (yep ^>^) i'll upload the latest installment of "watch us try to get this jb sense 45 rom to port." Lol.

Like Chris said, we've narrowed it down to one error finally.

This new one (test number 49) will have the apk's and framework from the VilleC2.

It'll take me about an hour and a half to finish uploading my updates.

Then i'll upload the latest port test.
[HTC EVO 3D] pancho32392:
Wow, the progression of this port is really fast Ya'll guys are really awesome with a amazing skills:)
[HTC EVO 3D] Shaky156:
You guys want a hand?
[HTC EVO 3D] sellers86:
I'm sure any help is appreciated
[HTC EVO 3D] Shaky156:
I think i can help out but would need to work close with someone that has the device
[HTC EVO 3D] thatotherguy..:
Pm me I have the 3d
[HTC EVO 3D] ______:
Got GSM here, if that matters.
[HTC EVO 3D] Tribulattifather:
Sorry, guys. Been busy porting from the evo 3d to the inspire 4g.

Now that i've got that almost finished i'll get to that upload today.

I'll let you guys know when it's uploading.

Edit: Okay. I'm uploading now:

ETA: Uploaded now

This time we have utilized the VilleC2 ota.

We've added the framework from vc2 and that got rid of the usbnet.jar error with stale dependencies.

We've also added the apks and from vc2 as well.

But, yet again, we have on line 702 and 704 of the logcat:

E/JNIHelp ( 114): RegisterNatives failed for 'libcore/net/RawSocket', aborting

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

Now the interesting thing with this test vs all the others that we've done is the fact that the logcat didn't stop; it kept looping.

With all the other tests the logcat stopped eventually.
[HTC EVO 3D] TheKnux:
CDMA here. On VM.
[HTC EVO 3D] saenz4931:
CDMA here

Sprint

El Demonio in 3D
[HTC EVO 3D] Indirect:
http://kobablog.wordpress.com/2011/05/14/how-to-read-crash-dump-of-android/
[HTC EVO 3D] beneath-a-burning-turtle:
!!!!!!!!

All of this stuff can be found in the SDK right?

EDIT: Nevermind it's in the NDK, silly me :rolleyes:
[HTC EVO 3D] Tourney3p0:
I did an objdump on the libc file, but it's pretty ugly since minimal debugging symbols are included. It puts me into the abort function, so the crash isn't there.

I then did an objdump on libnativehelper.so and checked address c282. It's in the middle of an instruction c280, which is a call to abort. So no problem there.

Going up another level to 1c4b8 gives us a call to jniRegisterNativeMethods as the logcat suggests. Things get murky here since I don't have the source, so I had to Google it in reference to calling abort. The file JNIHelp.c contains this function along with two abort calls. The one in question is:

if ((*env)->RegisterNatives(env, clazz, gMethods, numMethods) < 0) {

LOGE("RegisterNatives failed for '%s', aborting\n", className);

abort();

}

So there's your problem, but I have no solution because I don't know how the RegisterNatives function works. To temporarily get past it, you could hexedit the libc.so file such that the abort isn't called. That would take care of your loop and potentially allow you to continue, but it would still be very broken.

Edit: Just wanted to point out that the error message above matches the logcat output above the stack dump:

E/dalvikvm( 607): Requested: Llibcore/net/RawSocket;.create:(Ljava/io/FileDescriptor;Ljava/lang/String;)V

E/dalvikvm( 607): Candidate: Llibcore/net/RawSocket;.create:(Ljava/io/FileDescriptor;SLjava/lang/String;)V

E/JNIHelp ( 607): RegisterNatives failed for 'libcore/net/RawSocket', aborting

So the dump didn't really help at all other than confirming that was where the loop comes from.
[HTC EVO 3D] Indirect:
Message me your talk.
[HTC EVO 3D] beneath-a-burning-turtle:
What should it be changed to? (I have no knowledge of hexadecimal so I need some help lol)
[HTC EVO 3D] Zarboz:
when i was doing the port of ICS sense 4.5 to One S i had to make an edit to ext.jar to set it to expect sense 4.0 instead of sense 4.5 parts

let me decompile the file ill give you the exact edit
[HTC EVO 3D] beneath-a-burning-turtle:
So much help at once! Things are starting to move along which is good. We'll be awaiting your possible fix
[HTC EVO 3D] Indirect:
Incase I can't work on this; here you guys go:

.text:0000C25E ; ---------------------------------------------------------------------------
.text:0000C25E
.text:0000C25E loc_C25E ; CODE XREF: jniRegisterNativeMethods+1Aj
.text:0000C25E LDR R2, [R4]
.text:0000C260 MOV R0, R4
.text:0000C262 MOV R3, R7
.text:0000C264 LDR.W R6, [R2,#0x35C]
.text:0000C268 MOV R2, R8
.text:0000C26A BLX R6
.text:0000C26C CMP R0, #0
.text:0000C26E BGE loc_C284
.text:0000C270 LDR R1, =(aJnihelp - 0xC278)
.text:0000C272 LDR R2, =(aRegisternative - 0xC27A)
.text:0000C274 ADD R1, PC ; "JNIHelp"
.text:0000C276 ADD R2, PC ; "RegisterNatives failed for '%s', aborti"...
.text:0000C278
.text:0000C278 loc_C278 ; CODE XREF: jniRegisterNativeMethods+24j
.text:0000C278 MOV R3, R5
.text:0000C27A MOVS R0, #6
.text:0000C27C BLX __android_log_print
.text:0000C280 BLX abort
.text:0000C284 ; ---------------------------------------------------------------------------
[HTC EVO 3D] Tourney3p0:
What happens if you remove the reference to libcore.net.RawSocket from framework.jar/preloaded-classes?
[HTC EVO 3D] beneath-a-burning-turtle:
If only I could find it lol
[HTC EVO 3D] Zarboz:
.field public static final Htc_Extra_Sense_Version:Ljava/lang/String; =

null
[HTC EVO 3D] beneath-a-burning-turtle:
Value is already null though..

A lot further down i noticed

.method public static final getHtc_Extra_Sense_Version()Ljava/lang/String;

.locals 1

.prologue

.line 1819

const-string v0, "4.5"

return-object v0

.end method

Should I change

const-string v0, "4.5" to

const-string v0, "4.0"?
[HTC EVO 3D] Tourney3p0:
Should be inside /system/framework/framework.jar. Inside that jar file is the file in question. I don't think it will help though since this is a odex rom, but it couldn't hurt to try if there are no other developments to pursue.
[HTC EVO 3D] beneath-a-burning-turtle:
I know the .jar, I just can't find the .smali that covers that area (I used a deodexed from n earlier test)
[HTC EVO 3D] Zarboz:
yes sorry i was just pointing method to look for

:D
[HTC EVO 3D] Shaky156:
I shouldnt have asked, Thanks for offering but it would take too long working with someone to get it booting, hence why i work myself n get sense booted in past (much faster), i will most likely get it booted, just not on this device i dnt own a evo3d
[HTC EVO 3D] thatotherguy..:
Why you say something then back out?

not really trying to be a **** or anything but you shouldn't have came here saying if we needed your help if your just going to not help
[HTC EVO 3D] Zarboz:
any luck with this?
[HTC EVO 3D] beneath-a-burning-turtle:
I don't know how to repackage a .jar lol, I decompiled using apktool and I don't know how to build it
[HTC EVO 3D] Zarboz:
pm me your Gtalk i have Virtuous Ten studio and other tools i can use to repack and sign the jar for you :P
[HTC EVO 3D] sellers86:
Google how to decompile and recompile a .jar
[HTC EVO 3D] Zarboz:
just in case anyone wants to give it a whirl

(i dont own a 3d anymore :-p)

this should at least get you to the "android is upgrading" screen
[HTC EVO 3D] beneath-a-burning-turtle:
If that's the same one you sent me, unless I did something wrong, it didn't give us a change in really anything lol, but I'll dig deeper when I have some time
[HTC EVO 3D] motoelliot:
You guys are way outa my league but if it helps I opened the peanutbutter.jar for my wife... Lol seriously tho great work fellas! Lookin forward to what u accomplish...:thumbup:

Sent from 3D A.W.E.S.O.M-O
[HTC EVO 3D] beneath-a-burning-turtle:
https://www.youtube.com/watch?v=LekUKeFijxc
[HTC EVO 3D] powduh09:
Lol... Not sure how much I can offer... But perfectly willing to help... Both babt and tribs have my gtalk if u need an extra set of hands/eyes on this

Sent from my PG86100 using Xparent Blue Tapatalk 2
[HTC EVO 3D] Shaky156:
Either you have completely misunderstood or i didnt explain well enough, i will do a port on another device, so if its done on another device then its guaranteed to boot on this device too

Anyways newtoroots got it booting on the rezound (so youre probz asking hom for his build uptp youz), im doing mines from scratch, and its different than his :)

Anywayz ill be setting up a temp thread within the general section of the device ill be deving in, thatll be the old device i deved on before :)
[HTC EVO 3D] ramjet73:
This must be the newtoroot ROM that you are referencing, and that's based on the Evo 4G LTE JB ROM, just as his Sense 4.0 ROM for the Evo 3D was based on ICS for the same device.

There are many differences between older devices and the Evo 4G LTE including a different processor, screen size, WiMax versus LTE, etc., which may be why the things noted in the OP of that thread aren't working. I've had much better luck with the ROM's based on the One S C2 (Ville C2) like Charmander, Charmeleon (now Viper3D) and Elegancia than with newt's Sense 4.0 Evo 3D ROM so I'm hoping that between the Sensation and Evo 3D developers we get a port of that ROM for this device.

ramjet73
[HTC EVO 3D] ivicask:
This is just my opinion, and its very posibble im wrong, but i think this is wrong way to port this rom, even if this boots its gona be broken in so many ways..

I tried to boot in on sensation, ended with same errors like you.

As far i can see you changed alot of key libs from ICS like libandroid_runtime.so and libdvm.so and so..Problem is that those libs require different framework paths than Jelly Bean ones.

E/dalvikvm( 607): Requested: Llibcore/net/RawSocket;.createLjava/io/FileDescriptor;Ljava/lang/StringV
E/dalvikvm( 607): Candidate: Llibcore/net/RawSocket;.createLjava/io/FileDescriptor;SLjava/lang/StringV
E/JNIHelp ( 607): RegisterNatives failed for 'libcore/net/RawSocket', aborting

This error i managed to fix realtive easy by replacing Llibcore inside core.jar (libcore\net)

But its just followed by another errors in framework.jar

If you decopmile ICS framework.jar you have

android
com
javax
org

And Jelly bean has only

andorid
javax

So all the libs you changed from ICS are now FCing because of wrong/missing framework paths.

I'm working with one kernel dev on merging VILLEC2 kernel onto sensation one, so we more nativly boot this without changing so many libs,we already fixed libmemmaloc errors (memmory allcoator im kernel), but still cant get graphics to start , or rom to boot.

But we just started... gonna see whats gonna come up from it.
[HTC EVO 3D] VictoriousShooter:
What we really need are the developers joelz and tmartin. They are the ones who got sense 4.0 on our devices a long time ago. They could definitely be useful here.
[HTC EVO 3D] TruthAEE:
Huh? So happy Virus is in the house.
[HTC EVO 3D] killahrey:
Someone should hit up newtoroot. He's got sense 4+ jb booting on the rezound.
[HTC EVO 3D] johnthephotagrapher:
has anyone figured the problem of the boot-loop yet?
[HTC EVO 3D] beneath-a-burning-turtle:
I unfortunately have to drop my end of development on this project. My 3D broke a few days ago and I have no money to replace it. Sorry about that guys :(
[HTC EVO 3D] ramjet73:
Here's the current status for the Sensation port of the One S C2 (Ville C2) JB 4.1.1/Sense 4+ ROM.

I think if someone gets it working on the Sensation the Evo 3D won't be far behind since that's pretty much how we got the Ville C2 based Sense 4.1 ROM. The Venom team seems to port to the Sensation first and then the Evo 3D.

ramjet73
[HTC EVO 3D] Flashalot:
Man that really sucks

That's how it gos unless trib got it going I'm still bootlooping

Sent from my Sony San S
[HTC EVO 3D] raptoro07:
That does suck. I was wondering why we hadn't heard much from ya.
[HTC EVO 3D] ivicask:
Just a little tip even if we booted it will be no use to you, the trick is in kernel, you need a kernel dev to compile you a kernel with drivers/and parts from VILLEC2 source. (which is not that easy)
[HTC EVO 3D] VictoriousShooter:
As a suggestion, can this Rom use the same principle as this:

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

Where ics is the base and jb parts are added?
[HTC EVO 3D] Shponglized:
Interesting as hell, I'd be happy with this :fingers-crossed:
[HTC EVO 3D] ramjet73:
Since project butter is part of the Jelly Bean base this approach probably wouldn't include the performance enhancements. I also wonder how much of Sense+ is able to be integrated with the ICS base, but it will be interesting to watch that thread, especially once some screen shots are posted.

ramjet73
[HTC EVO 3D] Flashalot:
Downloading now let's see how much 4.5 is in it and how much ics is in

Sent from my Sony San S
[HTC EVO 3D] posedatull:
Any news about porting this to the GSM version of this phone? A lot of people would be more than happy to test it and use it :D
[HTC EVO 3D] Flashalot:
We don't even have it working

Sent from my Sony San S
[HTC EVO 3D] Zarboz:
i dont get how since there is no JB source for villec2 and just using the /drivers folder from the kernel or building it for the rezound/sensation have yielded me little to no results

i also thought maybe the butterfly J or DNA drivers but no avail

really at this point only option is to patch from CAF and pray it works
[HTC EVO 3D] ramjet73:
I'm not a developer but I'm curious. ;)

Does "patch from CAF" mean using generic Qualcomm drivers instead of the ones that HTC supplies?

ramjet73
[HTC EVO 3D] ivicask:
Theres no JB source, but ICS source will get you booting, because you need change in ION drivers (memory allocator) and some other stuff as its on original VILLEC2 device..
[HTC EVO 3D] Zarboz:
still yields black screen with the villec2 egl/HAL

i tried using the drivers from CAF (code aurora forums | Qualcomms github basically) for ion /adreno to no avail as well

when i built the kernel i literally placed the rezound support files into the villec2 source as they are both 3.0.16 based devices

i also tried with sensation (wich i know is almost identical SOC to evo3d)

both would yield black screen on boot with HAL from villec2

please PM me i am curious of the method you used to yield results as far as the kernel is concerned

Currently what I have done is place vigor_defconfig into villec2 sorce /arch/arm/configs

make vigor_defconfig

make

when error occurs "missing file" or w/e i update file fix error and let it compile.... none of the errors have to do with GPU or msmFB or adreno or ion....

unless your referring to just building /drivers/video/msm

instead of /drivers/video/msm-8x60

in wich case im 90% done that way too
[HTC EVO 3D] dastin1015:
What you're doing still doesn't utilize ion memory allocation which the villec2 does. When HTC went from GB -> ICS they did a half assed job with the kernel and chose the route of minimal work instead of leaving behind the deprecated pmem and switching over to ion. Your board files are still calling and allocating for pmem and therefore won't work as intended. HTC's laziness of not updating to ion is a reason why we're most likely never going to see a Jellybean OTA.

私のEVO 3Dから送信される。
[HTC EVO 3D] Thealshear:
Umm there is a test kernel ION support in gsm evo 3d
[HTC EVO 3D] ramjet73:
If you are referring to helicopter's kernel I think dastin is already working on adapting his changes to an Evo 3D CDMA version.

ramjet73
[HTC EVO 3D] Snoob25:
R: [WIP][DEV][ROM][Sense 4+][w/JB 4.1.1]

Just to know, if we build an aosp android 4.1.1 rom with ion (I'm on gsm, camera doesn't work but at the moment that's not important) can we use it as base for sense 4+ quite easily? Or there's more and more work to be done?

Inviato dal mio HTC EVO 3D X515m
[HTC EVO 3D] raptoro07:
smh
[HTC EVO 3D] Snoob25:
R: [WIP][DEV][ROM][Sense 4+][w/JB 4.1.1]

Smh?! Seriously, I'm not asking a sense 4+ ready tomorrow nor claiming I will get it working in few hours, I'm just asking for INFOs.

Inviato dal mio HTC EVO 3D X515m
[HTC EVO 3D] sami055:
I'm pretty sure you can't use Aosp to build a sense ROM. It has to be ported from the HTC one s or something like that.
[HTC EVO 3D] raptoro07:
Sense is not just an App you can layer over Android. It is it's own version of Android and as such cannot be just put on an AOSP base. This is very common knowledge and easily found out by googling. Sorry for my quick smh. It was early. :)
[HTC EVO 3D] sami055:
I'm not the one who needs to be apologized to. I was just explaining to him. I think you quoted the wrong person.
[HTC EVO 3D] Snoob25:
apologies accepted :) i know that, but i don't know if ion implementation will require some libs or other files related to the single device, and a working aosp 4.1.1 with ion could be a "source".

I'll try to repeat more accurately my concerns: mainly we need a kernel for android 4.1.1 that supports ion, so, once we have the kernel, porting will be kinda "easy", or we'll need another entire different kind of work (different from the past i mean) due to ion memory allocator??
[HTC EVO 3D] raptoro07:
I know, I was mainly confirming what you said.
[HTC EVO 3D] dastin1015:
My personal github has the msm8660 kernel with ION implemented.

私のEVO 4G LTEから送信される。
[HTC EVO 3D] Danger Dan:
Can we boot this then?
[HTC EVO 3D] Flashalot:
Is it for GSM WFTN

Or CDMA WFTN

And where you able to get the sound working yet
[HTC EVO 3D] Kitteh:
Looking at the commits, its for both shooter and shooteru

.

https://github.com/dastin1015/android_kernel_htc_msm8660/commits/jellybean
[HTC EVO 3D] sellers86:
If I'm not mistaken, to use ion on this ROM you would need to compile the ion kernel and build the ROM for ion. You can't just compile his kernel with ion and flash it with his latest build.
[HTC EVO 3D] dastin1015:
I have no idea. It works for aosp sans camera when compiled with ION.

Both. Works except camera

私のEVO 4G LTEから送信される。
[HTC EVO 3D] dastin1015:
This is Sense not aosp. You can't compile sense since source isn't released

私のEVO 4G LTEから送信される。
[HTC EVO 3D] Flashalot:
So this isn't the ion drivers from the LTE new(well not that new) Source or...

If it isn't how hard would you think portion a ion sense kernel to evo 3D
[HTC EVO 3D] sellers86:
Yeah I know, I thought I was in the WFTN thread. But sense 5.0 is already compiled for ion, so it doesn't matter.
[HTC EVO 3D] Danger Dan:
So is anyone going forward with this or is it dead?
[HTC EVO 3D] VictoriousShooter:
Why hello there

http://xdaforums.com/showthread.php?t=2216858
[HTC EVO 3D] ramjet73:
That's a great start!

Did you notice the outstanding items:

Still quite an achievement. :good:

ramjet73
[HTC EVO 3D] Snoob25:
HERE some hints about kernel :)
[HTC EVO 3D] Danger Dan:
Isn't that for the sensation?
[HTC EVO 3D] ramjet73:
Yes, but the venom team usually ports to the sensation before the Evo 3D.

The basic hardware is very similar except for the radios and 3D.

ramjet73
[HTC EVO 3D] sami055:
Does that mean we can expect this ROM soon.