yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] alahkel:
Nope, I'll try that later.

I was good on first build with build.prop "modified", so I was lazy about flashing a new rom :P but I'll do it later and report back results :)
[HTC EVO 3D] alahkel:
Ok with last build I have lil problems with music.

If I listen to music without touching my phone, no problems at all.

If I am doing something on the phone while listening to music, playback is choppy.

No problems with screen off.
[HTC EVO 3D] alahkel:
Oh and you would be glad to know that in latest build the torch app and status bar widget are working properly ;)
[HTC EVO 3D] UnderZone7:
I have not been able to get this to boot. I got 4Ext recovery and it finally worked yet it wouldn't move past the boot screen. It dident even boot loop. The boot animation just kept going. Any fix?
[HTC EVO 3D] tomanlam:
I still can't access the camera app on build 6/16...:confused:

Did anyone get the camera working on the latest build?

But still this rom is speedy enough as a daily driver!:D
[HTC EVO 3D] cwillison94:
Same here, I thought maybe it was a corrupted download so downloaded again, but same thing.
[HTC EVO 3D] tomanlam:
here u go!;)
[HTC EVO 3D] edruig:
Hey i've got bootloop with this: cm-9-20120613-UNOFFICIAL-shooteru.YesCam.zip
[HTC EVO 3D] jekyll86:
There is a New build, check previous posts. Try that build

Inviato dal mio HTC EVO 3D X515m
[HTC EVO 3D] alahkel:
It looks like ppl with 5+5 cam with 6/15 build are getting bootloops. In last build agrabren and kali tried to fix 5+5 cam. Which cam model do ppl getting bootloops have?
[HTC EVO 3D] silvbm:
Rom is working good so far. Camera working with 5+2 Cam.

Only Problems are high battery drain which is probably just a calibration issue and face unlock can't be started in maybe half the time.

Otherwise it is insanely fast my new daily driver now.
[HTC EVO 3D] SecFry:
As Kali- said, use this build, it's from developer:

https://plus.google.com/u/0/100349908055803732636/posts/J67AL7qwcJq

Also cirle Kali- in G+.

I think I'll close this thread in some time. For now this would be place for discussion.

P.S. But for now I would prefer to stay on my own build :D
[HTC EVO 3D] zerow:
I don't understand if it's necessary to download the kernel also for this latest build.

If i did the downloading right, the rom is about 128mb and the kernel about 123mb.

Is this possible or i downloaded the wrong thing ?
[HTC EVO 3D] tomanlam:
u probably have messed up sth :S... kernel should be the boot.img inside the zip archive:cool: while the rom refers to the whole zip
[HTC EVO 3D] zerow:
Hm, the post on the link goes as following

Finally, a beta build CM9 for GSM Evo 3D

https://www.dropbox.com/s/ix7z95rnazjn5ds/cm-9-20120616-UNOFFICIAL-shooteru.zip

Know bug:

BT Call

with BT enabled phone cant sleep

HDMI

3D

Camera/Camcorder is not 100% stable

Kernel: https://github.com/TeamEvo/htc-kernel-msm8660/tree/20120616

due to what can be readed in my previouss message there are some limitation and agrabren, the dev who bringup the cam have decided to add signature check (swapping thing can broke cam)

i to hope to convince him to remove this check and finally add Evo 3D GSM and CDMA to the CM9 nightlies build :)

For CDMA build look on xda forum

Cheers

Kali-

>>>>>>

So i clicked both links provided and downloaded twice.

Guess i'll stick with the rom.zip for now and test to tell if this build is any better.

I bootlooped with the old:(
[HTC EVO 3D] SecFry:
Bootloop caused by system partition crash as it mentioned on first post. 4ext recovery somehow fixes that problem.
[HTC EVO 3D] Kali-:
the attempt to add 5+5 cam completly broken 5+5 boot

i have pushed a new build with this cam disabled so it will boot (i hope) on all devices

a this point i'm not sure if we can fix it blindy :/

i hope someone with this device can be able to fix it
[HTC EVO 3D] SecFry:
What should I read (except of that big commit) to fix 5+5 cam? I had a lot of development on PC (c++, java), but not on mobile devices.
[HTC EVO 3D] testman86:
Thats strange. I tested the first build with working cam and I have a 5M*2 Device and it was working for me. I did not test the build from 15th June and 16th June but the 13th June was working for me. I could open the cam without any error or any bootloop. I wrote this a few pages ago where people were asking if 5M*2 Devices are working http://xdaforums.com/showpost.php?p=27419261&postcount=173. Maybe I have the time to check the newest available build 16th June in the evening and give feedback.

Another question is where can I get the newest build from today with deactivated cam to use it if the cam does not work in the 16th June build?

Edit: You posted it on your google+ site. For everyone who is looking for it I post the link to your google plus page to find it. https://plus.google.com/100349908055803732636/posts (I think its better then directly linking to Dropbox because its not mine ^^ )

And thanks again for your and the other devs nice work! :-)
[HTC EVO 3D] runkle6:
flashed 20120616. flashed boot.img via adb manually afterwards. 1st boot everythings okay, even cam! but second boot: phone app fc loop, cant do anything against that, have to pull battery ... :(﻿

s-on, unlocked via htcdev.com
[HTC EVO 3D] alahkel:
Someone with 5+5 model cam send them the phoneeeee :P

Really, they could have fixed it if they have one ._. Unfortunately we can't do

any collect of donations to buy them a 5+5 model 'cause.. I don't think they're sold anymore :/
[HTC EVO 3D] cwillison94:
Is it possible for a dev with a 5+5 to work in collaboration with them? Or do they really need a device to see what's going on
[HTC EVO 3D] agrabren:
I'm not done with the blind fixing yet....
[HTC EVO 3D] alahkel:
That's good to hear! :)
[HTC EVO 3D] agrabren:
Ok, I need something to help you guys... Someone with a 5+5 cam config that can't use the current ICS stuff, I need a dmesg log from startup of your device running a ROM that works.
[HTC EVO 3D] SecFry:
adb shell dmesg > dmesg.txt

UPD: awww attached a wrong one

UPD: now its the right one

UPD: or you need dmesg from ROM which have 5+5 cam working?
[HTC EVO 3D] agrabren:
I need a dmesg from a ROM which has 5+5 working. :)
[HTC EVO 3D] cwillison94:
here you go, hope it helps! I am running predator's rom if that makes a difference
[HTC EVO 3D] agrabren:
Other than the obnoxious double-spacing, it's perfect! Thanks!!!
[HTC EVO 3D] cwillison94:
not sure what you mean about the double-spacing but your welcome! :p

-ps. Thank you devs for looking into this!!
[HTC EVO 3D] Evengard:
As I understand, Kali- and agrabren are working on full support on AOSP of our sweet HTC EVO 3D, including 3D stuff? This is excellent! Anything for donations? :)

PS: and I have this famous 5+5 model. If you need any help I can at least try to help...
[HTC EVO 3D] bahrianabbas:
What recovery are you using?
[HTC EVO 3D] maurimauri29:
+1 Battery drain is high for me too. After calibration it went down from 100% to 80% from 11pm to 6am just on stand-by.

Apart from that I am loving this. Everything is so fast and responsive.
[HTC EVO 3D] KrewsialNL:
Same here, seems like deep sleep isn't working at all.

What about your device temperature btw? Mine is getting way too warm :o
[HTC EVO 3D] SecFry:
7 hours only for 20%? This is great stats, not so much devices could show this and you name it battery drain. Obviously, my iPad discharges slower, but I mainly would say that the only iPad showed such performance for me.
[HTC EVO 3D] jekyll86:
20% in standby is big battery drain
[HTC EVO 3D] SecFry:
Stand-by? Every 1 or 2 or 3 hours phone asynchronously checks twitter, facebook, vk, g+, gmail, calendar, contacts, news, weather, locator, etc., etc.

20% is perfect battery work for 7 hours.

Put it in 2g network mode, switch-off Wi-Fi, GPS, screen rotation, screen brightness, turn off all synchronization and will get 72-144 hours of work, but I think you use Evo 3D just to have that features.

Actually only message of 20% for 7 hours means nothing if there no information about settings.
[HTC EVO 3D] :
secfry , do you think camera is fixable - maybe by porting over some stuff from cdma - they got working camera (well , it's the only reason for staying with sense....) on CM9

..(http://xdaforums.com/showthread.php?t=1703070)
[HTC EVO 3D] SecFry:
As TeamEvo said (Kali- and agrabren actually) it's fixable 100%.

I can't do that actually, trying to do something (actually read a commit) and nothing helps.

I think devboard with 5+5 should be enough to speedup development.

Actually I can even send my phone - the only thing that Russian post service could stole it (I don't care, but that would be not to good).
[HTC EVO 3D] VladBelsky:
The reason that the camera works on all CDMA devices is because they all have the 5+2 megapixel camera sensor. Some GSM users and I have the camera sensor that has two 5 megapixel sensors, which the AOSP ROMs currently are unable to connect to. Currently, the camera on AOSP ROMS only works with devices that have a 2 megapixel sensor for the second camera.
[HTC EVO 3D] :
yeah, i'm one of the proud with twice 5mp sensors ... :(
[HTC EVO 3D] agrabren:
I'm jealous. But fear not, then we'll make it work.
[HTC EVO 3D] tomanlam:
just a foolish question...

y not reroute the driver to the 5MP camera on both (5*2 and 5+2) devices?:confused:
[HTC EVO 3D] Evengard:
agrabren - hope you will receive my small donation ;) At least something to help you...
[HTC EVO 3D] maurimauri29:
Don't get me wrong. I think this is absolutely great. :cool: The work you guys have put into this is nothing short of brilliant. I was simply comparing to other ROMs I used before (some of the ICS Sense-based ones for example) which for the same amount of time at night, with the screen off and WIFI on, syncing the same stuff, used only 5-7% of the battery. For example, right now I am back from work, and soon I'll have to go out again. In about 17 hours my phone is down to 6% battery left, with only moderate use (no calls at all today, no games, only usual mail syncing and a bit of music playing while I was on the bus) and that makes it difficult for me to use it like this daily. That's the only point I was making.

So no criticism at all, I was just letting the devs know about my experience and my feeling about this, in the hope it will help them to make this better.

Keep up the great work.
[HTC EVO 3D] vipirius:
Because it's not that simple :D
[HTC EVO 3D] tomanlam:
i c, i thought the 5MP camera on both hardware revisions (5*2and 5+2) are the same :S
[HTC EVO 3D] alahkel:
Mmh, so htc released the GSM version before the CDMA one, I suppose.

Lucky cdma guyz xD

If only sense source code was open... :(
[HTC EVO 3D] agrabren:
To help make it clearer, you don't have a rear camera, you have a rear camera assembly. We talk to that camera assembly, and it does it's hardware magic. The 5+2 camera assembly is made by Sharp, and is known in the code as the sp3d. This assembly handles both cameras, as well as the important task of combining the images into a single 3D image (which we then transcode into a usable file format). On the 5+5 devices, they use a different camera assembly. This goes by the name qs_s5k4e1 in the code. On all known shooter devices, and some shooter_u devices, you'll see the qs_s5k4e1 report "Bridge Failed". This happens if you don't have the 5+5 module. But for those of you with the 5+5, the bridge will be programmed either in 2D or 3D mode, and can be switched between modes. Theoretically, it should be that simple. The problem is, it's not exactly that simple. Much like the initial porting of the sp3d module, we have to get all the clocks within tolerance, we have to get the voltages correct, etc. These are the same reasons some people are having difficulty with the kernel booting, while others have no issues at all. It's little finicky controls of the regulators and clocks. Anything goes wrong, and boom. Device crashes, locks up, etc. (Generally, no real damage is done, but a battery pull is usually needed).

Thank you for the donations, they're a big help in convincing the wife that I'm not just hiding from her. ;)

Hope this explanation helps everyone understand the technical aspects of what we're trying to do, and why it's tricky.
[HTC EVO 3D] :
i hope you'll get the cam working on 5+5 models... i'm one of the (proud?????) owners...
[HTC EVO 3D] alahkel:
Great explanation, dude :) keep up the great work!
[HTC EVO 3D] alahkel:
Ps I have a high batt drain too but I don't complain - got a lot of replacement batteries :p p.p.s. no wifi/mobile/sync/gps enabled but during night in sleepmode my phone goes from 100 to 80. Batt calibrated :) just to let u know
[HTC EVO 3D] KrewsialNL:
20% in 7 hours is too much. Period :)

Please tell me what good deep sleep would be for?

Others have a 2-5% drain in 8-9 hours, which would make the 20% in 7 hours look a bit silly :)
[HTC EVO 3D] bahrianabbas:
How Would I find out what sensor I have?
[HTC EVO 3D] areestocrat:
Try any non-sense rom with 2d camera work. If ur cam doesn't work then its 5+5 mpx.
[HTC EVO 3D] IFLPI:
If it comes to buying a 5+5 model. In Poland i got it a month ago from my operator contract. So they must be in magazines in many places. I'm into a donation to buy a dev this model. Cause blind developing must be hard.
[HTC EVO 3D] bahrianabbas:
Give me a link of such rom?
[HTC EVO 3D] shirioko:
MIUI
[HTC EVO 3D] alahkel:
I'm in too, but... I don't think the 3devos sold now have 5+5 model, 'cause htc began to sell gsm evo 5+5 model then they understood that having two 5mp sensors was stupid and more complicated so they decided to make evo with 5+2 assembly, then they start selling cdma evos that were all 5+2 models... dunno if you understand what I mean.

But if you're sure where to find a 5+5 model for devs, I'm in on donations collect! :)
[HTC EVO 3D] tsalas:
+1
[HTC EVO 3D] agrabren:
Give me a chance to solve it first.
[HTC EVO 3D] alahkel:
Yeah, we wish you the best luck in blind fixing :) you (and kali) have all our respect and gratitude for working so hard! ASAIC donations coming from me :) (a link to donate to you?)

Sent from space
[HTC EVO 3D] IFLPI:
Even if it is not being sold now the one who has 5+5 can send his phone to dev, and buy new one from donations. Its also a solution, but maybe the problem can be solved without it. Its only a rescue idea.
[HTC EVO 3D] scariola:
E3dlight 1.1 damn I miss cm7, it flies on this phone. http://xdaforums.com/showthread.php?p=22215135

Working cam, so me 5+2.
[HTC EVO 3D] alahkel:
You're right, I haven't thought about it o_o

Let's see if they can find a fix for 5+5 models first :)

Then I'm in for the donations collect! :)
[HTC EVO 3D] Evengard:
Any news? Do we have a chance? :)
[HTC EVO 3D] alahkel:
Let 'em work and do their magic :P
[HTC EVO 3D] Evengard:
Yeah, you are right... Just they ressurected my hope)
[HTC EVO 3D] agrabren:
Sorry, was on a small family vacation for two days. :) I'm bouncing back and forth between getting the 3D framework in place (YouTube, Camera, etc) and getting shooter_u 5+5 figured out.
[HTC EVO 3D] KrewsialNL:
How dare you spend time with your family! ;) (Obviously, i'm kidding! :D )

Good luck with all the awesome work you doing for the community!
[HTC EVO 3D] Evengard:
I hope that this small vacation gave you some ideas, hein? :)
[HTC EVO 3D] alahkel:
Great! :) (alahkel likes this element ahahah)
[HTC EVO 3D] KrewsialNL:
Hey guys,

Does anybody know, why the phone turns so hot upon using this build?

It heats up really bad and it starts around the camera lenses.
[HTC EVO 3D] maurimauri29:
I am not using this at the moment, because the battery drain made it impossible for me to use this as a daily driver. However, before replacing it, I gave it a very good test run and I too have noticed the phone heating up considerably; I noticed especially when playing games.

I really want to thank the devs because they have done an amazing job on this, both for CM9 and the kernel, and I am sure that soon CM9 will be 100% working. :fingers-crossed:
[HTC EVO 3D] bahrianabbas:
So when we are getting the next release? I am eagerly waiting.
[HTC EVO 3D] Temoi19:
For those who keep asking when the new release is coming. DO NOT! Go read the Cyanogenmod Page. It will clearly state that you do not ask when the next release is coming. It will come when THE DEVELOPERS believe it is ready to be released.

Keep Up the great work guys!!! Enjoying the ROM so far!!
[HTC EVO 3D] bahrianabbas:
Okay I am sorry If I am breaking the rules.
[HTC EVO 3D] Temoi19:
It has nothing to do with breaking the rules..its just common sense...this is a developers site..if you nothing to say or just want to thank them hit the thanks button, Dont go on complaining about the ROM..or ask when it will be done..it will come when they believe that it is ready..like I said this is a site made for those who develop, not those who nag and bug.
[HTC EVO 3D] agrabren:
I'm not a member of TD anyway, so the rules on their website don't apply to me. As for an ETA, I wish I had one. I'm working to get my kernel building again with the latest changes, and I'll be asking for kernel testers to get my dmesg and logcat results so I can see what is happening. We've had friends out visiting for almost a week, which has greatly reduced my time for programming.
[HTC EVO 3D] :
a great thanks for you efforts! i hope you will get the camera working.

T H A N K S.

how about opening a thread?
[HTC EVO 3D] testman86:
I have a 5M*2 Megapixel Device (System Information say so) and on the 13th June build I could open the Camera App without any error. If I can help you and test something I would like to help to get CM9 working.
[HTC EVO 3D] dre1187:
I think have the 5*2 camera as when I installed the 6/17 build I would get "error connecting to camera". I would really like to get CM9 on my phone, so please let me know if you need help testing out builds
[HTC EVO 3D] agrabren:
Looking for daring individual or two to flash the following ROM:

http://goo.im/devs/agrabren/cm9/shooteru/cm-9-DevilToast-0.6-shooteru.zip

What I need is the following (don't bother flashing if you don't understand the following requests, since it's really just designed to get this data)

1. dmesg and logcat from booting the device

2. dmesg and logcat from launching the camera app

Thanks
[HTC EVO 3D] johnnyslt:
logcat after boot : http://dragbox.org/f/5cdws

dmesg after boot: http://dragbox.org/f/7okx7

______________________________________________

logcat after camera : http://dragbox.org/f/mi7ga

dmesg after camera : http://dragbox.org/f/cinad

P.S I have a 5+2 camera
[HTC EVO 3D] agrabren:
oops, should have clarified, 5+5. Did the camera work for you? It should have, you have the sharp module. :-)
[HTC EVO 3D] crisvillani:
flashing now, got 5+5 camera, will post in a few minutes :good:

---------- Post added at 08:29 PM ---------- Previous post was at 08:12 PM ----------

well i tried flashing and getting some sort of logcat and dmesg but the rom did not boot. It shows the htc screen for two seconds then it goes black and then goes back to the htc screen :( , i cant even give u a logcat as it doesn't stay connected to the computer long enough. Also had these same problems with latest builds of AOKP by helicopter. To clarify I used 4EXT to flash it, wiped everything , and have 5+5 camera. Sorry couldnt help :(
[HTC EVO 3D] agrabren:
That helps. Thanks. :-)
[HTC EVO 3D] agrabren:
Ok, same favor, but have an addition zip file to go with it.

http://goo.im/devs/agrabren/cm9/shooteru/shooter_u-camtest.zip

(And yes, I know, the link doesn't work yet. Give goo.im 15 minutes or so to update the mirrors, etc)

This may or may not boot any better. But even the complete failure gives me useful information which I can use to help debug the problem. :) I'll also come out now and say that yes, it contains a modified kernel. Patch file is available upon request to anyone who downloads it (although it really isn't very exciting, it's just swapping in the correct GPIO configurations in the board-shooter-camera.c file)

Special note: This build is *only* for 5+5 configs. In an effort to reduce effort, I used #ifdef to switch from the Sharp 3D module to the Liteon 3D module. So it breaks everyone else.
[HTC EVO 3D] Evengard:
This is kernel only? I need to use an AOSP based ROM to test?

How do I get logs if the ROM won't boot? Sorry, total noob... Any tutorials?
[HTC EVO 3D] testman86:
@ agrabren

So first I should flash http://goo.im/devs/agrabren/cm9/shooteru/cm-9-DevilToast-0.6-shooteru.zip after that flash http://goo.im/devs/agrabren/cm9/shooteru/shooter_u-camtest.zip ? And then a dmesg and logcat from boot and starting the camera? And only on a 5+5 Device? I was asking how I could help you and the other Devs, but your post were, at least for me, sometimes a little bit confusing :-)
[HTC EVO 3D] johnnyslt:
^ yes thats the right way to do it
[HTC EVO 3D] teihoata:
Still not getting to the boot animation although its on the htc logo a bit longer than the previous build. Unable to get a dmesg from it
[HTC EVO 3D] wILLRoiD:
may help with this. rom for gsm
[HTC EVO 3D] SecFry:
ROM boots without this package. Currently it optimizing my dalvik-cache, so I'll upload logcat and dmesg in a while.

Should I flash camtest then?

Try to "adb logcat" and check what it says. I think you have problem with system partition.

[UPD:] ok, first dmesg/logcat's uploaded, currently flashing camtest.

[UPD2:] ok, with camtest ROM boots, creating and uploading new logs.

[UPD3:] OMG MY CAMERA WORKING!!!!

[UPD4:] Video + panorama works perfectly.

Video proof of working
[HTC EVO 3D] johnnyslt:
^ I think you have the 5+2 cam model.

Agrabren wants logs from 5+5 models.
[HTC EVO 3D] SecFry:
/* this line of text was too aggressive, so I decided to delete it */

Never before camera worked for me.

Also I know that I have 5+5 model.

Also this build is only for 5+5 as agrabren said.
[HTC EVO 3D] johnnyslt:
If that's the case it seams that Agrabren managed to fix 5+5 cam.

:-)
[HTC EVO 3D] Evengard:
Well... Didn't managed to get it booted at all. cm-9-DevilToast-0.6-shooteru.zip only didn't booted, nor it haven't booted with shooter_u-camtest.zip.

Maybe I am doing something wrong? It just shows "HTC" and then it just switches off after something around 10 seconds.

UPD: and yes, I did a full wipe.
[HTC EVO 3D] teihoata:
I managed to get it to boot by flashing cm-9-DevilToast-0.6-shooteru on top of the old stable cyanogen build cm-9-20120617-UNOFFICIAL-shooteru and then flashing the camtest kernel afterwards. It still doesn't connect to my camera but it does show that I'm running the rom under settings.

Here's my dmesg of the first boot and a logcat of what happens when I open the camera if you want it
[HTC EVO 3D] agrabren:
teihoata: That's a great log! Thanks!

SecFry: You're camera module is a Sharp 3D Module, so yours is expected to work. We've been likely misusing the term 5+5 and 5+2, since those reference the CCDs themselves, and not the camera module as a whole. There are two camera modules, the Sharp 3D module and the qs_s5k4e1 camera module. The was, from the boot dmesg log to differentiate is the engineerid. On the qs_s5k4e1 devices, the engineerid is 0x1. Everyone else, it's generally 0 (for shooter_u). That also means that likely, the qs_s5k4e1 came later, not earlier, than the sp3d module.

So it appears we have multiple issues (which isn't surprising). This lines up with the problems we're seeing on the shooter (CDMA) where many people have trouble getting it to boot. And we still have a camera attach issue, but that's probably a lot easier to debug and fix than the current issues of no kernel support (regulators failing).

I'm going to keep cracking at it, but thank you very much for everyone who has been flashing back and forth to test and verify this stuff. Your help is really moving forward on full camera support for all EVO 3Ds, as well as preventing the need for getting one of the "picky" devices into a developers hands.
[HTC EVO 3D] agrabren:
Oh, and I know why your camera app failed. I *may* be able to get a new build today with a fix (unfortunately, it's a full spin of the ROM, not just a kernel build).