yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] beneath-a-burning-turtle:
We would need to reverse engineer it because we don't have the full source. Yeah we can compile kernels, but HTC doesn't exactly like handing out source to their proprietary drivers, precisely why we don't have 3D or 4G support for sense 4.0/4.1. If we don't have their drivers, we can't change how those drivers handle ION, meaning we can't implement ION support
[HTC EVO 3D] jlmancuso:
Hate to burst bubbles but trying to use aosp ion drivers will not work. The difference between aosp and sense are huge. Best bet will be trying to port over ion from a sense 4.1.1 kernel from a similar device. This will not be an easy task.
[HTC EVO 3D] sellers86:
That does not mean ION support can't be implemented, at all. All that means is that 3d and 4g won't work. But with ION, camera won't work at all, because you need to completely rewrite the camera drivers for ION. Again, that does not mean ION can't be implemented.
[HTC EVO 3D] Flashalot:
So your saying take certain files from a aosp kernel and puting them in a sense kernel and wouldn't those certain files be looking for aosp components instead of sense and our current kernel is ics. So it would be a mix of ion and pemn
[HTC EVO 3D] sellers86:
Not at all. I'm saying port the ION portions of the AOSP ION KERNEL SOURCE to the SENSE KERNEL SOURCE. I don't know how I can make this any clearer.

You can't port a file from a ROM to a kernel. That just doesn't make sense.
[HTC EVO 3D] Flashalot:
I ment to say kernel

Still it makes no sense we should try to port the sensation kernel its been stated here count less times I think we could do it instead of porting the ION portions of the AOSP ION KERNEL SOURCE to the SENSE KERNEL SOURCE
[HTC EVO 3D] sellers86:
That would be harder. Sense kernel source and aosp kernel source isnt as different as you seem to think it is.
[HTC EVO 3D] kiewee3:
I'm 16 also.... Sorry I think everyone was getting angry over my signature... I was just quoting what was already stated earlier :/

But seriously if you don't know how to read you probably won't understand any of this.
[HTC EVO 3D] jlmancuso:
Yes guys this is about being a group not an individual. Work together and accomplish greatness fight each other and nothing can get done. Now everyone keeps throwing out thoughts which can make things happen but yall are going around and around chasing each others tails. Now time to step up and take a shot. What is the worst you can do? Get no further than we are already. I will be pulling the source for pyramid tonight along with our kernel sources and a couple of similar device kernels. Time to dig in and see what might be done. I will advise yall to do the same and who knows someone just might get lucky.

They say put a thousand monkeys infront of typewriters for a thousand years and you can get the complete works of Shakespeare. So this monkey is getting started what other monkeys going to join in?

Do I know what I am doing? Well I know some of it but am no expert. Will that keep me from trying? Heck no! In the past couple years I have learned Linux, android, html, c, c++, java and while not a pro I strive to achieve what I can. After many failures the fruit becomes sweeter. If anyone wants to link up around 12:00 am cst hit me up on talk (jlmancuso1134@gmail.com).

I welcome everyone to join in even if this is your first look at code or you have done this for years.
[HTC EVO 3D] beneath-a-burning-turtle:
If I'm up at around then I'll join you and try and add in whatever I can. I suck at kernels and source but I know how code works, to an extent, so maybe I can provide some useful information.

And what you said before all that was worded perfectly. If we can't work together as a team then nothing can get done. If everyone has to try and place themselves above the rest then no teamwork exists and no progress can be made. We just need to shut up about all these petty little issues, and realize that's not why any of us are here. We just need to work on this and try to get this booting.

So aside from that, I'd be more than willing to help out with comparing code and seeing what needs to be implemented with what. I don't have a 3D so I can't test anything but I have my two cents.
[HTC EVO 3D] Flashalot:
I'm up for it got my evo back I can stop deving then and help out some only know bits and pieces of code
[HTC EVO 3D] Tribulattifather:
Good to see the youngins playing together again, lol.

I have ported the One S kernel and the Sensation XE and XL kernel and no go still for me just to update.

I built each from source and then injected 3vo info to it.

To test, I ported a One S aosp kernel and used it on my 4.2.2 (which I still am not finished with) and it worked. So that means to me that still, something else is missing.
[HTC EVO 3D] beneath-a-burning-turtle:
Something here just doesn't make sense *badum-tiss*
[HTC EVO 3D] Flashalot:
From what kernel if I may ask
[HTC EVO 3D] #WB:
the VilleC2, JB kernel? and it still wouldn't boot? hmm..
[HTC EVO 3D] Thealshear:
Are you able to get a dmesg or log that will give us a slight idea of what is working and what isn't
[HTC EVO 3D] Tribulattifather:
This is what I'm using from currently for my 4.2.2 to test if I could port:

https://github.com/Sportsstar89

And this is what I've tried porting after porting stock :

http://xdaforums.com/showthread.php?t=2097612&page=14

And after stock and this didn't work I even tried sense 4+ from sensation.

This is driving me nuts lol.

I have logcats in my goo.Im working folder for evo
[HTC EVO 3D] #WB:
maybe try this instead? I don't know..
[HTC EVO 3D] Thealshear:
Screen drivers did you replace them?
[HTC EVO 3D] gmzombie:
I don't know if anybody seen this as well but the kernel source for the isw13ht valente is here

http://www.htcdev.com/DevCenter/downloads/P40

It is the j kernel. Maybe this will maybe not but is thought is throw that out there
[HTC EVO 3D] jlmancuso:
I have been looking around and I came across this http://xdaforums.com/showthread.php?t=2084970 it is for the HTC Rezound but we use the exact same processor as the rezound. I will try my hand at trying to get it working with the 3vo but my porting skills are not that good.

here is the link to the rezound sense ion kernel source. https://github.com/zarboz/Rezound_ION

Edit: Looks like this just might work. Been playing with it and have gotten it to boot just a bit further than any of the others I have tried. Now from reading some of the other threads about ion, jb and sense 4+ the next big step after the kernel will be building drivers for the audio :( Well one mountain at a time huh?
[HTC EVO 3D] gmzombie:
Can't wait to see this get off the ground running.
[HTC EVO 3D] kiewee3:
I have a spare 3d laying around if anyone needs a tester. I'll also try to throw something together while One development takes off
[HTC EVO 3D] gmzombie:
I to have a 3d to test both one for flashing and one that I use so if it works with the flasher phone ill put it to ly phone to test.

looking at

http://www.au.kddi.com/english/mobile/product/smartphone/isw13ht/spec/

the official page for that japan phone it actually shows a msm8660a for the cpu. do you think the kernel from that phone really be that different cpu wise? also i was thinking about it and the stock rom for that phone has android 4.0 which is ICS. So the ION kernel should not matter right? Im just posting this as i see it. im no dev'er im only a helper. so with that said is it possible to port that stock rom first due to the fact that it has Wimax? Just thinking outside the box guys
[HTC EVO 3D] Tribulattifather:
Not sure if you mean to say you'd be willing to give your 3d to someone or not, but I trully believe that there are a few devs around here that could truly benifit from your generosity, such as [MENTION=4318807]THC Butterz[/MENTION] . People like him are the future of developing. Ppl like me are older devs and do not have as much time as they'd like to to dev. Please consider him.
[HTC EVO 3D] Snoob25:
well, i don't know if there's still anyone working on this, but just as info: sebastianfm released a sense 4+ rom with kernel 3.4 for sensation, source will be uploaded!

http://xdaforums.com/showthread.php?t=2349756
[HTC EVO 3D] kevin130:
This man is purely amazing!! I really hope someone can get this to work. I want to continue learning to develop to do it myself but my machine broke :(
[HTC EVO 3D] Ch1ngl1ng:
Wow, working camera as well! This is amazing, now we just need someone to port :)
[HTC EVO 3D] CNexus:
It does work. I've tried it. And I've gotten Sense 5 ported to the S3 using a modified AOSP boot.img. And we have nothing even remotely close to a Sense kernel.

I have also gotten a Sense 4 port to the boot ani using the same technique.

The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
[HTC EVO 3D] hightech316:
Can you give us a hand?
[HTC EVO 3D] CNexus:
Give me your CM boot.img and the boot.img from the rom you guys are porting (attach them to your post).
[HTC EVO 3D] Snoob25:
source uploaded :fingers-crossed: http://xdaforums.com/showthread.php?t=2356371
[HTC EVO 3D] Kiinasu:
Here you go
[HTC EVO 3D] CNexus:
See attached
[HTC EVO 3D] kevin130:
What happens now? Lol what do?
[HTC EVO 3D] CNexus:
You use that as your boot.img to port Sense 4.
[HTC EVO 3D] Kiinasu:
could someone test it with the rom from Tribulattifather?: http://goo.im/devs/Tribulattifather/Evo_3D/Sense%204.5

i would do it myself, but i dont own an cdma device. if someone tested it, please post the logcat
[HTC EVO 3D] bjones8515:
I'm dl rom, and boot img now. Will report back as soon as I can. Might be couple of hours. Getting ready for work.
[HTC EVO 3D] Flashalot:
Ziping up now :)

Edit wish my computer wasint slow 1 GB ram so 35% and counting last zip failed to zip
[HTC EVO 3D] Flashalot:
No go :(

Did not go passed the boot up not even to boot logo
[HTC EVO 3D] CNexus:
That means nothing if you didn't grab a logcat.

I highly doubted that it would boot up completely. It took a lot more than just the boot.img for me to port Sense 5.
[HTC EVO 3D] Flashalot:
Ill pull along cat

but yes it did not boot IP completely but that may just be me

And the boot.IMG was all we

need trib said he got it to almost boot but all we need was the kernel
[HTC EVO 3D] kickyoace:
Dling now will flash when I get home from summer school and provide a logcat when I get it setup on my laptop
[HTC EVO 3D] kickyoace:
Nope cant get a logcat what so ever I tried it on all hboots after I flashed boot with fastboot
[HTC EVO 3D] salvy512:
Same, Stuck at htc logo.
[HTC EVO 3D] beneath-a-burning-turtle:
Why don't we just port that sensation kernel instead of running in circles.. We know its there so why just do that and finally get this booting instead of beating around the bush. Just saying lol
[HTC EVO 3D] #WB:
exactly. just need someone who wants to do said port, be it kernel or the whole ROM.
[HTC EVO 3D] CNexus:
Because it's a lot easier to say, than to do.

I'll edit the boot.img to give logcat.

Sent from my S3 on Sense 5 (you jelly?)
[HTC EVO 3D] beneath-a-burning-turtle:
The 3D and the Sensation are basically the same exact phone, with the exception of WiMax and 3D. The two phones go hand in hand, I don't really see why it would be a majorly difficult task, but I'm not a kernel dev so I can't really say much other than that
[HTC EVO 3D] Flashalot:
As for the boot still no logcat on my end tryed on 2 computers still no go
[HTC EVO 3D] VictoriousShooter:
I know this thread is quite old now, but considering that the 3D now has kernels with ION, will it add anymore hope for this system
[HTC EVO 3D] Ch1ngl1ng:
Correct me if I am wrong, but I was made to believe that we needed a 3.4 kernel as well to get this booting. I know Dastin is working on one currently, but nothing released.
[HTC EVO 3D] VictoriousShooter:
I don't know about what kernel version we needed, all I remember was all of the hullabaloo about how all of these non-boot errors are related to the kernel not having ION.
[HTC EVO 3D] Flashalot:
We need a 3.4 kernel for sense the ion kernels you see are for aosp only if we could get the kernel then we coud (hopefully)have a 4+ rom but it looks like all the kernel devs are gone and moved on to other phones

Sent from my SPH-L710 using Nightmare Rom
[HTC EVO 3D] jose51197:
i do confirm you dont need 3.4 kernel for this to boot, i deved at the incredible lte community and brang succesful ports of sense 5 and 4+ but without camera, 3.4 is needed for camera to work
[HTC EVO 3D] 24ky:
Glad to see you here mate
[HTC EVO 3D] Flashalot:
Well that's has not been the case here unfortunately we have only been able to port 4.0 and 4.1 if you would like to share how you did so it would be very helpful

Sent from a potato running Android
[HTC EVO 3D] 24ky:
[MENTION=4678269]Flashalot[/MENTION] well I'm [MENTION=4440065]jose51197[/MENTION] dev friend from the HTC Droid Incredible 4G LTE.. and what he said is true, we were able to port sense 4+ and 5 to the divice with a 3.0 kernel and only Bluetooth and Camera were borked after he fixed everything else..... And we were able to do it because I told him how the DrInc4g stock sense 4.1 kernel has ion in it but isn't active. And him doing kernel work he got it working.... And I just recently sold him my " Virgin Mobile HTC Evo V 4g "... So I'm sure he will do the same here. So be patient lol
[HTC EVO 3D] Flashalot:
Sounds good I hope we can get it going if we do ill be porting like crazy

Sent from a potato running Android
[HTC EVO 3D] 24ky:
Most likely camera and Bluetooth will be borked
[HTC EVO 3D] Flashalot:
Ya that's more kernel side that's usually the case with ports with out the kernel

Sent from a potato running Android
[HTC EVO 3D] 24ky:
I'm curious on if he can port the sensation kernel over.
[HTC EVO 3D] Damix2:
So is there any progress? Does anybody work on it?
[HTC EVO 3D] Snoob25:
I don't know if there's still anyone willing/capable to work on this, if so check this in GSM section ;)

http://xdaforums.com/showthread.php?t=2800107
[HTC EVO 3D] Tribulattifather:
I'm up, donor Roms are downloaded and about to look into them and see if I can get the files I need.

NOTE: I've already looked at Toro, Toro plus and Maguro yesterday (Maguro just for the hell of it, lol, being that it is GSM).

Then I'll check all my Rom's I have made. But, i'm thinking that if we don't find these filese, these may not be our concern and it might be kernel relatetd or something else.
[HTC EVO 3D] beneath-a-burning-turtle:
What I saw is at the beginning of every log, it says it can't open some ISO, and looking at the stock deodex JB from the sensation forums, there's an ISO in system/lib. Later in my logs, it hits system/bin a few times, and then goes straight to battery alignment, and then it just cuts off completely. Not sure what to make of that. Also, about 1000 lines in, it says "system/etc/customer/bootanimation.zip can't be found (no directory)" and then gives a ton of boot animation errors (no width, height, sound, part0,1,2,3)
[HTC EVO 3D] Tribulattifather:
I've seen that bootani error before on working Roms. But you're def right about that iso. I've seen that in all my logs too.

I'll flash and test. If doesn't work then i'll look for that iso.
[HTC EVO 3D] beneath-a-burning-turtle:
Pm me a list of everything you've done so far that way I can compare to mine. I have the ISO on hand so I'll add it to whatever you've done and get back to you
[HTC EVO 3D] Tribulattifather:
Oh man, I probably should have kept notes on what i've done since my last upload, lol; I've done 13 more tests since then.

But, the test that I am doind now is flashing with the libaudcal.so, AIC3254_REG_MFG.csv and AIC3254_REG_COMMON_DualMic.csv from Sense 4.1. This was the test that I had prepared for myself for when I got up. If these errors disappear then I will upload my current test build and it's logcat.

NOTE: all the donor Roms i've downloaded I did look at and found only the libaudcal.so in a few of them. But I did not find any other of these files that I listed yesterday.
[HTC EVO 3D] beneath-a-burning-turtle:
I'll do the same based on what changes I've made, and add the ISO

Can I have those files btw? Lol
[HTC EVO 3D] Tribulattifather:
No need to give em v.v They didn't even work, lol.

This is a snipet of my last logcat I just did a second ago:

D/HTC Acoustic( 435): failed to open file /system/etc/AIC3254_REG_MFG.csv: No s
uch file or directory (2).
D/HTC Acoustic( 435): int android_audio_legacy::support_audience(), support_a10
26: 0
D/HTC Acoustic( 435): failed to open file /system/etc/AIC3254_REG_MFG.txt: No s
uch file or directory (2).
D/HTC Acoustic( 435): failed to open file /system/etc/AIC3254_REG_COMMON_DualMi
c.csv: No such file or directory (2).

Even after I added these files from the only Rom that had them, which was the Sense 4.1 Rom. Every other AOSP and Sense donor Rom did not have these files in them..

**Perplexed**
[HTC EVO 3D] beneath-a-burning-turtle:
Hmm.. I wonder if those pop up even with a working rom.. I'll bet you we're not even addressing the right issue lol. A dalvik error caught my eye in all my logcats. I'll pull it and attach the line in a sec. There's a fatal error as well. Didn't notice that before

[ 12-26 01:41:09.955 114:0x72 E/dalvikvm ]

ERROR: couldn't find native method

[ 12-26 01:41:09.955 114:0x72 E/dalvikvm ]

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

[ 12-26 01:41:09.955 114:0x72 E/dalvikvm ]

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

[ 12-26 01:41:09.955 114:0x72 E/JNIHelp ]

RegisterNatives failed for 'libcore/net/RawSocket', aborting

[ 12-26 01:41:09.955 114:0x72 F/libc ]

Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

That signal 11 has got to be the culprit. I'm looking into what it means right now

**Edit: It's killing the dalvik operation, why? I do not know**
[HTC EVO 3D] Tribulattifather:
You know, I think this is where our problem lies. I've learned through looking at all these Roms that none of them really have any of these files that are listed.

I did take care of that libaudcal.so error, but that was easy. Here you are:
[HTC EVO 3D] beneath-a-burning-turtle:
My exact thoughts. That Signal 11 is the ONLY fatal operation in the entire log. What we need to do now if figure out why/what is killing the dalvik. It said it couldn't find the native method, so whatever that is, we need to fix, and it should (keyword: should) boot, but that's my guess.

Google calls that 0xdeadbaad error corrupt memory. What if.. I'm curious as to maybe the system partition is too big for our phones, and it can't flash EVERYTHING? A sense 4 rom I have has 686 mb in the system folder. Your 4.5 has well over 800. I'm trying to slim it down now, and then flash
[HTC EVO 3D] Tribulattifather:
Okay, my friend and I have been also working on this privately. We came up with the idea that the dalvik is erroring out because of something audio related. That's the given.

Here's my snippet of the logcat I just did again:

09:48:11.283 Error ExtendedExtractor 2008 Failed to open MM_PARSER_LIB, dlerror = Cannot load library: reloc_library[1290]: 2008 cannot locate '_ZN7android11MediaSource23getNumberOfVideoBuffersEv'...
09:48:11.283 Error ExtendedExtractor 2008
09:48:11.283 Error ExtendedExtractor 2008 Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1096]: Library 'libmmparser_lite.so' not found

[B]
09:48:11.287 Info dalvikvm 2039 mlock: /data/dalvik-cache/system@framework@core.jar@classes.dex, fd=8
09:48:11.287 Info dalvikvm 2039 mlock(1278423040, 3080976), fd=8
09:48:11.287 Error dalvikvm 2039 ERROR: couldn't find native method
09:48:11.287 Error dalvikvm 2039 Requested: Llibcore/net/RawSocket;.create:(Ljava/io/FileDescriptor;Ljava/lang/String;)V
09:48:11.287 Error dalvikvm 2039 Candidate: Llibcore/net/RawSocket;.create:(Ljava/io/FileDescriptor;SLjava/lang/String;)V
09:48:11.287 Error JNIHelp 2039 RegisterNatives failed for 'libcore/net/RawSocket', aborting
09:48:11.287 libc 2039 Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
[/B]

09:48:11.411 Error HTC Acoustic 2041 read ACOUSTIC_GET_TABLES fail. -1
09:48:11.411 Info HTC Acoustic 2041 TPA2026 CSV File Open From /system/etc/TPA2026_CFG.csv
09:48:11.411 Debug HTC Acoustic 2041 failed to open TPA2026 CSV files /system/etc/TPA2026_CFG.csv.
09:48:11.411 Info AudioHardwareMSM8660 2041 set_tpa2026_parameters fail

09:48:11.411 Error HTC Acoustic 2041 read ACOUSTIC_GET_TABLES fail. -1
09:48:11.411 Info HTC Acoustic 2041 TPA2028 CSV File Open From /system/etc/TPA2028_CFG.csv
09:48:11.411 Debug HTC Acoustic 2041 failed to open tpa2028 CSV files /system/etc/TPA2028_CFG.csv.
09:48:11.411 Info AudioHardwareMSM8660 2041 set_tpa2028_parameters fail

09:48:11.411 Error HTC Acoustic 2041 read ACOUSTIC_GET_TABLES fail. -1
09:48:11.411 Debug HTC Acoustic 2041 failed to open file /system/etc/AIC3254_REG_MFG.csv: No such file or directory (2).

09:48:11.411 Debug HTC Acoustic 2041 failed to open file /system/etc/AIC3254_REG_MFG.txt: No such file or directory (2).

09:48:11.411 Debug HTC Acoustic 2041 failed to open file /system/etc/AIC3254_REG_COMMON_DualMic.csv: No such file or directory (2).

The errors with bold are the main problem in our opinion.

I'm thinking that maybe we might need to be decompiling a jar or dex because of this line:

09:48:11.287 Info dalvikvm 2039 mlock: /data/dalvik-cache/system@framework@core.jar@classes.dex, fd=8

But, what to edit..

It's worth a shot to try to lower the amount in the system folder. The original port had a gig in the system folder O.o lol.
[HTC EVO 3D] beneath-a-burning-turtle:
[ 12-26 16:26:00.694 114:0x72 D/dalvikvm ]

DEX prep '/system/framework/usbnet.jar': unzip in 1ms, rewrite 66ms

[ 12-26 16:26:00.774 114:0x72 F/libc ]

Fatal signal 11 (SIGSEGV) at 0x4edbb272 (code=1)

This is where I'm at Trib, I almost got this, audio problems are a thing of the past now. It's just that usbnet.jar giving us issues
[HTC EVO 3D] BoostmyXb:
is this a ROM?

If so then installation will be the same, place on SD card boot to recovery, wipe and installed from SD.

is that it?
[HTC EVO 3D] Tribulattifather:
Mostly anything with Dev or Wip in the title usually means that a boot is close but non existent ^>^

But, yes, just flash like normal on an hboot 1.50 or less.

Right now it gets hung up at the boot animation.
[HTC EVO 3D] ramjet73:
Sounds like there may be some issues in the One S version of the Jelly Bean/Sense 4+ update based on this post. I'm not trying to be negative about it and haven't heard about these issues with the Evo 4G LTE update, but I'm posting this just for awareness.

ramjet73
[HTC EVO 3D] Tribulattifather:
trouble is is that villeplus is the only one that matches our hdpi..
[HTC EVO 3D] ramjet73:
Yea, that's true even though it has the S4 processor instead of the S3 like the Evo 3D.

At least until JB releases for the HTC One S C2 (Ville C2) and hopefully HTC will optimize that version for a less powerful configuration.

ramjet73
[HTC EVO 3D] Newt:
Not trying to highjack the thread but I have received pm's asking for help... I am not against helping, but right now my time is spent on my own projects and getting this to boot will be to hard to just tell someone how to do it, so what I will do is this... I am working on porting the Evo lte to the rezound I have booted it and now I'm working on fixing the issues once I have a stable build up for the rezound I will do the same for you guys if you haven't made it any further.. keep trying to get it to work and ill jump in and help soon if still needed... Good luck guys practice makes perfect ;)
[HTC EVO 3D] thatotherguy..:
Sweet hopefully you can sooner
[HTC EVO 3D] bjones8515:
Thanks for the response, and words of encouragement! Absolutely appreciated!
[HTC EVO 3D] Tribulattifather:
Sounds good. I've got it close to booting several times with a few friends. We've narrowed it down to a lib problem, which is pretty easy compared to what we've been dealing with. But absolutely, if we don't get it booting, we'd love to have you help us to do so.