• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [DEV] WIP CM9 (Camera) [updated 2/23/2013]

Perhaps gingerbread with an ICS theme will be the best we can expect on the Triumph. maybe Motorola didn't do the coding, but we all know that they have to have access to it and could release it if wanted. So Motorola /Foxconn are to blame for the lack of support for this phone. Thank you G60 and MTDEV for the valiant effort. Have we given up hope on trying to get help from Foxconn?
:thinking::thinking::thinking:
 
Upvote 0
Hold your head high G60 you and MTDEV have done more for this community than Motorola has and they are the ones getting rich off of us. They should be ashamed of themselves. you guys have been doing their dirty work for them and still raking in the dough.
All,

I have finally hit a brick wall with the code :banghead: My skills at C++ are just not solid enough to get us over the hump with the camera at this time. Also there has been so many changes in the code from Gingerbread to Ice Cream Sandwich in the kernel that I am not sure if that is not causing some of our problems or not?!? Dorregaray has been a humongous help, however I can not rely on him to write all the code out for the Triumph or expect him to solve our issues when does not own the device. Until we get some more people involved with the device that have a stronger level of C++ background we will not be able to solve the camera.

Also since I don't know anyone else in our community that is solid at C++, or has the time to program on the Triumph, I have decided I am going to stop developing all together, and use that time to learn C++. While it may not be the news everyone wants to hear this is where we are right now in this project. So again the race is not over, it's just going to be very slow and very steady like the :turtle: and hopefully we will win it!

Respectfully,
-g60
 
Upvote 0
All,

I have finally hit a brick wall with the code :banghead: My skills at C++ are just not solid enough to get us over the hump with the camera at this time. Also there has been so many changes in the code from Gingerbread to Ice Cream Sandwich in the kernel that I am not sure if that is not causing some of our problems or not?!? Dorregaray has been a humongous help, however I can not rely on him to write all the code out for the Triumph or expect him to solve our issues when does not own the device. Until we get some more people involved with the device that have a stronger level of C++ background we will not be able to solve the camera.

Also since I don't know anyone else in our community that is solid at C++, or has the time to program on the Triumph, I have decided I am going to stop developing all together, and use that time to learn C++. While it may not be the news everyone wants to hear this is where we are right now in this project. So again the race is not over, it's just going to be very slow and very steady like the :turtle: and hopefully we will win it!

Respectfully,
-g60

Thanks for all your work man. I think I speak for everybody here, we're very proud of the work you put into this project.
 
Upvote 0
You are all to kind with your comments! I have really tried to get this working. As it stands I just wanted to give everyone ample time to make a move if they so choose to another phone before xmas. I really hope in time I can fix this camera as I have so many hours invested in this little device. But the fact of the matter is until I learn more on C++ there just isn't any more I can do to benefit the community in terms of making this phone work better than it already is. It's really disappointing to get so close to solving the damn thing. I never regret in life but right now I regret not solving this camera as I feel I have let down so many of you....

-g60
 
Upvote 0
No G60, as they say $$$$ rolls down hill. We can start with VM, They are the ones marketing the phone to the end consumer, then we can roll down hill to Motorola/Foxcon, whoever has the source code and refuses to release it. You are another user of the device that just happened to have more coding knowledge than the rest of us. You were simply doing what Motorola should have been willing to do 6+ months ago. All without pay!!:D:D You and MTDEV are simply awesome.:D:D
You are all to kind with your comments! I have really tried to get this working. As it stands I just wanted to give everyone ample time to make a move if they so choose to another phone before xmas. I really hope in time I can fix this camera as I have so many hours invested in this little device. But the fact of the matter is until I learn more on C++ there just isn't any more I can do to benefit the community in terms of making this phone work better than it already is. It's really disappointing to get so close to solving the damn thing. I never regret in life but right now I regret not solving this camera as I feel I have let down so many of you....

-g60
 
Upvote 0
You haven't let me down. You busted your butt on this thing! Besides, I have a digital camera which is way better quality than the Triumph's camera. I will try and learn C++ in my free time as well, if that helps. Hell, you were one of the only ones that gave a damn about this device. Motorola didn't care. You did! We should all get you a Christmas gift for all your hard work! I don't know what, but at least we can all say thank you. You can always come back to this thing later. And think of yourself if you must learn C++. Maybe you can use that to expand your career in real life. You don't really have to commit more to this phone if you are stressed, but maintenance by repo syncing once a month would be appreciated. Also, keep in touch with the rest of MTDEV. It's your life, code only when it is enjoyable. You clearly cannot enjoy coding now since you are obsessed with fixing the camera. Hone your skills in coding, take some breaks, and come back later (if you want). You are once again a workaholic. Spend some time with your family, spend some time alone, whatever, just give the Triumph a break for a little while before you crash! You are more important than a stupid rebranded Motocrap phone! You decide if, when, and how you can fix it. I know way less about coding than you do, so don't feel bad. I do suggest you learn C++, but learn it not just for this damned phone, but learn it for yourself. Learn it for your job, financial security, and your future. Don't bother if you grant no benefits from it until you've taken a break. g60madman>stupid Triumph
 
Upvote 0
It's kinda funny in a way, VM is still selling Triumphs due in part (mostly???) to the efforts of the developers here. Maybe VM would actually prefer to see us throw our phones away and buy new ones.

G60 and MTDEV, thank you for your efforts. They are appreciated. Don't let the bastards get you down.
 
Upvote 0
G60 you did an awesome job with the triumph. I loved uses all the differnt roms for it but it wasnt the phone that made me leave it was the service. Granted my plan was 25 a month but when you can barely stream music or lose signal when inseide a building then you are getting what you pay for.. Shame too i loved the triumph especially with miui rom. So no i pay 30 dollars more pageplus verizon towers super fast 3g on a droid razr. Shame on virgin all that money spent on ads and the sevice is crappy :(
 
Upvote 0
Well said MikeRL, and I concur. It's not like we don't have the camera on any of the Roms. Take off as much time as you need brother:D:D
You haven't let me down. You busted your butt on this thing! Besides, I have a digital camera which is way better quality than the Triumph's camera. I will try and learn C++ in my free time as well, if that helps. Hell, you were one of the only ones that gave a damn about this device. Motorola didn't care. You did! We should all get you a Christmas gift for all your hard work! I don't know what, but at least we can all say thank you. You can always come back to this thing later. And think of yourself if you must learn C++. Maybe you can use that to expand your career in real life. You don't really have to commit more to this phone if you are stressed, but maintenance by repo syncing once a month would be appreciated. Also, keep in touch with the rest of MTDEV. It's your life, code only when it is enjoyable. You clearly cannot enjoy coding now since you are obsessed with fixing the camera. Hone your skills in coding, take some breaks, and come back later (if you want). You are once again a workaholic. Spend some time with your family, spend some time alone, whatever, just give the Triumph a break for a little while before you crash! You are more important than a stupid rebranded Motocrap phone! You decide if, when, and how you can fix it. I know way less about coding than you do, so don't feel bad. I do suggest you learn C++, but learn it not just for this damned phone, but learn it for yourself. Learn it for your job, financial security, and your future. Don't bother if you grant no benefits from it until you've taken a break. g60madman>stupid Triumph
 
Upvote 0
g60madman said:
I never regret in life but right now I regret not solving this camera as I feel I have let down so many of you....

-g60

Ahh hell no!!! You are trying to do what Motorola and VM SHOULD have done. You never promised us anything other than you would try your best and I feel you and the MTDev Team have gone beyond that. At least you are honest and are not blowing smoke.

CHEERS!!!!
smiley-eatdrink009.gif
 
  • Like
Reactions: g60madman
Upvote 0
G60, you have no reason to feel like you've let anyone down. What you did for the Triumph community was a great act of philanthropy. You made a phone I regretted paying for into something I rely heavily upon and enjoy pulling out of my pocket when I'm bored. Thanks for your hard work and your continuing dedication to development. I...I love you...haha :)
 
Upvote 0
Thanks for the code link, I will look more when I get home. I assume the camera stuff is in the hardware_qcom_camera repo? Is it somewhat self contained, in that I could just build the camera portion and put it on top of the CM9 portion?

Sorry for the noob questions, but a little direction would help save a lot of time in terms of knowing where to start. I've done some android app development but never messed around with the base system before.
 
Upvote 0
OK....I am new to Android Development like this...so are there any instructions I can follow for how to develop?

And does the kernel driver currently hose the system as in the previous post?


To build all the guides are online at Team MTDEV under the wiki section. It will show you how to setup your environment and build the code using Ubuntu 10.04 which I highly recommend to use for OS. Others have used other version but have run into multiple problems. So if you are wanting to get in and start working I would use 10.04 and not mess around with other flavors.

EDIT: Sorry as for the Kernel, Mantera made some changes to bring it inline with ics_chocolate for the camera. I am not 100% that maybe some of the problems, and or me updating the egl drives for video could be some of it. Right now my recommendation would be to take the stock Motorola kernel and update the ICS changes to it. As soon as we know the kernel is functioning properly it would be best to then move onto the camera. It's possible that fixing what we have is possible, however there maybe to many possibilities which maybe causing problems that are not accounted for.
 
Upvote 0
Thanks for the code link, I will look more when I get home. I assume the camera stuff is in the hardware_qcom_camera repo? Is it somewhat self contained, in that I could just build the camera portion and put it on top of the CM9 portion?

Sorry for the noob questions, but a little direction would help save a lot of time in terms of knowing where to start. I've done some android app development but never messed around with the base system before.

There is a handful of camera folders added. When you repo sync the code the directories you need to worry about are

camera-test: This folder builds the CameraHal which creates the camera.msm7x30.so located in the system/lib/hw of the ROM. The folder in the source when synced locally will be located in android/hardware/qcom/camera

libcamera2: This folder will build libcamera2.so which is located in system/lib/ of the ROM. This folder is basically building the libcamera.so from source. Once the ROMis created you can delete the stock libcamera.so and rename the libcamera2.so to libcamera.so. Both the stock libcamera.so and libcamera2.so both crash the phone when launching the camera. The located in the source will be android/hardware/qcom/libcamera2

Honestly I am really leaning on the kernel is having problems but I am not savvy enough to say. Also I believe when I added all the egl updates for video it could also be causing issues. Let me know if there is any more info you need or want :D
 
Upvote 0
There is a handful of camera folders added. When you repo sync the code the directories you need to worry about are

camera-test: This folder builds the CameraHal which creates the camera.msm7x30.so located in the system/lib/hw of the ROM. The folder in the source when synced locally will be located in android/hardware/qcom/camera

libcamera2: This folder will build libcamera2.so which is located in system/lib/ of the ROM. This folder is basically building the libcamera.so from source. Once the ROMis created you can delete the stock libcamera.so and rename the libcamera2.so to libcamera.so. Both the stock libcamera.so and libcamera2.so both crash the phone when launching the camera. The located in the source will be android/hardware/qcom/libcamera2

Honestly I am really leaning on the kernel is having problems but I am not savvy enough to say. Also I believe when I added all the egl updates for video it could also be causing issues. Let me know if there is any more info you need or want :D

Do we know what changed in terms of the camera interface from CM7->CM9?

Are we using the same version of the kernel for CM7 and CM9? I wonder what makes you lean towards the kernel having the issue.
 
Upvote 0
There is a handful of camera folders added. When you repo sync the code the directories you need to worry about are

camera-test: This folder builds the CameraHal which creates the camera.msm7x30.so located in the system/lib/hw of the ROM. The folder in the source when synced locally will be located in android/hardware/qcom/camera

libcamera2: This folder will build libcamera2.so which is located in system/lib/ of the ROM. This folder is basically building the libcamera.so from source. Once the ROMis created you can delete the stock libcamera.so and rename the libcamera2.so to libcamera.so. Both the stock libcamera.so and libcamera2.so both crash the phone when launching the camera. The located in the source will be android/hardware/qcom/libcamera2

Honestly I am really leaning on the kernel is having problems but I am not savvy enough to say. Also I believe when I added all the egl updates for video it could also be causing issues. Let me know if there is any more info you need or want :D

What ever happened to the 2.6.35 kernel?
 
Upvote 0
Do we know what changed in terms of the camera interface from CM7->CM9?

Are we using the same version of the kernel for CM7 and CM9? I wonder what makes you lean towards the kernel having the issue.


Let me explain :D Our kernel is taken from CAF (Code Aurora Forum) through the project MSM/QSD. IssacJ was the first on the Triumph scene with ICS and ported the CAF kernel to be used and imported settings from ICS into to make it work. Here is his work

https://github.com/ikarosdev/triumph-kernel-msm7x30/commits/2.6.32.9-chaos-ICS

When IssacJ left Mantera took over the kernel and updated the camera files of the kernel and also updated from 2.6.32.9 to 2.6.32.59 along with the camera files located here

1. https://github.com/MTCM9/android_ke...mmit/5951a507ecb9744025d05455489fed4ed7a57593
2. https://github.com/MTCM9/android_ke...mmit/f8c75271b950913631f22c5bc6315b227fd192b5
3. https://github.com/MTCM9/android_ke...mmit/04c68e5e3dab7b5423f887b0de0e9d5dae9ef983

If you look at our sister phone's kernel the X6 the camera files where also updated as well to ICS but not as many settings where added.

https://github.com/tjstyle/android_kernel_fih_msm7x30/commits/android-msm-2.6.35.7

Also tjstyle was also able to get the camerahal to work as well which is located here
https://github.com/tjstyle/hardware_qcom_camera/tree/fb0. I have tried multile time to get this to work, and while it will build it just boot loops the phone even after I imported our msm_camera.h

As it stands we have never been able to take the Sharp camera lib files and make them work on our phone for CM7. The libs we are using are from the Cherry Phone which is another sister phone of ours. Here is the libs

https://github.com/MTCM9/android_vendor_motorola_triumph/blob/ics/triumph-vendor-blobs.mk#L42-L46


Our stock Kernel is here
https://github.com/MTDEV-KERNEL/MOTO-KERNEL

And here is the stock x6 kernel. Both kernels are 2.6.32.9
https://github.com/tjstyle/FIH-Kernel-MSM7x30

If you look at the following files on each stock kernel and also the ics kernels you see that Mantera added in more settings from ics_chocolate and I am not sure that is not hurting the stock liboemcamera.so from launching.

arch/arm/mach-msm/include/mach/camera.h
drivers/media/video/msm/msm_camera.c
include/media/msm_camera.h

I have tried to do multiple changes to the kernel based on tjstyle, and also the zte_blade which has the same camera as us but with no luck.

Also in both directories of our new camera files I have worked on with Dorrey are here. Both have the msm_camera.h from here
include/media/msm_camera.h of the kernel. This is why I think it maybe kernel.

https://github.com/MTCM9/camerahal-test
https://github.com/MTCM9/libcamera2

As for the ICS camera changes here is a brief overview of what Google did.
http://forum.xda-developers.com/showthread.php?t=1379368

If you need more let me know.
 
  • Like
Reactions: wildplace
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones