Of course they do everything stock ICS does, except the bugged stuff.
So once they get the camera working it's possible the built-in face-unlock feature will work.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ICS Camera Ideas
- Thread starter amzer81
- Start date
-
- Tags
- motorola triumph
Of course they do everything stock ICS does, except the bugged stuff.
So once they get the camera working it's possible the built-in face-unlock feature will work.
If you have it set in device_triumph.mk to build, then the only other reason that I can think of offhand is if you don't have it set to build in one of the Android.mk files in the actual repo. Perhaps you don't have a condition set properly to build in the Android.mk file.
rukin5197
Android Enthusiast
Looks like it's going to need some edits for our devices, but until we can get it to boot there's no telling for sure.
cacingkalung
Newbie
Guys... TJ_style use 2.6.35.x kernel for ICS with this camera on our fb0 device while i read you guys using 2.6.32.x on your triumph, is that could be the problem?
No. Our camera is slightly different than the FB0 devices. And I also tried with the 2.6.35.7 kernel and it still doesn't boot up.
cacingkalung
Newbie
owh... months ago our roms are just very similar just different by RIL and very easy to port vice versa, and then different by touchscreen and has to changed kernel when porting, and now by camera
.What new camera libs? Also, it's the camera.msm7x30.so that is causing the boot loops. So if you're not building it, then you won't boot loop.
Also, if you haven't made this change or something similar, then it won't build:
https://github.com/mantera/hardware_qcom_camera/commit/ad4bd01035ceda5015ea968b20f85f38ea240ecd
markzombie82
Android Enthusiast
Thanks for still being around
Tokens210
Android Expert
if mantera, gannon and g60 continue trying i would give it a maybe, but just to be sure i also wouldnt raise hopes to high, just in case lol
as far as ive been able to tell, recently like the beginning of this thread, some new camera info came down from tj, who from what ive read so far has been able to get our devices camera to atleast turn on, on an ICS rom
so first the devs here were going thru trying to find what changes if any he had that they didnt that were causing their cameras to not function
i believe, altho im not 100%, that they have made it passed that portion and are now attempting to test the changes they have made, except from what ive been reading, the camera is now giving issues while its building which is causing it to not work again
My understanding of the issue, and I'm very new to development, so please correct me if I'm wrong
, is that we are having trouble implementing the new code from tjstyle to our device. This trouble is that their device uses a proprietary library camera.fb0.so while our uses camera.msm7x30.so(not sure why we use a different one, I'm still learning) These libraries are closed, meaning we can't see the code or modify it. Basically we have to poke it with a stick and see what falls out and try to reverse engineer the program calls. Then we can modify tjstyle's code with the correct calls and test from there. Right now the device won't boot with the camera code, so it is hard to troubleshoot the issue. I did find another device that uses camera.msm7x30.so, and they only have very limited camera function.I'm sure all the devs would love to have testers, but right now there is nothing to test. We don't have a working rom with any camera support.
My understanding of the issue, and I'm very new to development, so please correct me if I'm wrong
I'm sure all the devs would love to have testers, but right now there is nothing to test. We don't have a working rom with any camera support.
Hmm ok so if what you said is correct couldn't we like find some type of way to get that section that's keeping the camera from working look at a library that has camera.msm7x30 or something similar and try to reproduce that proprietary library but with the needs of the Triumph then tweak it so the original proprietary library camera.fb0 that tj gave us can work with the tweaks that we put in there for our Triumph thus turning it into our own needs of the proprietary library camera.msm7x30 ...
Hmm ok so if what you said is correct couldn't we like find some type of way to get that section that's keeping the camera from working look at a library that has camera.msm7x30 or something similar and try to reproduce that proprietary library but with the needs of the Triumph then tweak it so the original proprietary library camera.fb0 that tj gave us can work with the tweaks that we put in there for our Triumph thus turning it into our own needs of the proprietary library camera.msm7x30 ...
Kinda, we can't modify anything in the camera.msm7x30 file. I can't even open it to see what calls it supports. I've been working on getting the camera working over the last few days. I've had to teach myself everything(with some help from g60), so it was a slow start. I now have a better understanding of the issue. The camera.msm7x30 is the driver. We are asking it things like how many cameras it has, right now it's not returning a number. I am trying to get that to work(so we can move to the next step) and one possible fix it to manually tell it there are 2 cameras. But that may cause other issues. I don't believe the fb0 file works at all on our device.(I could be wrong, and I might try that down the road). I did find a typo in tj's code, but after correcting it, it still won't boot.
This will be a slow process as every change and update requires a complete rebuild of the code, that even with a fast computer(4Ghz quadcore with 12GB ram) takes over an hour! So I make a change, try it, log the results, compare, make a new change, wait for rebuild, and repeat. So I can only get 3-4 updates a day
I'm sure I will eventually get the camera working, it will just take some time 
k i see, the more Intel you have on it the better job you can do at the task, But i wish i could help more with this task but being that i don't know anything at all about this i might not be that much help. And i don't think it works on our phone either. Seeing as though if we flash a FB0 nandroid it could give you a boot loop or possible brick. That's why i was thinking that if we can modify the fb0 file and turn it into the file we need (msm) their is possibly more hope than what we had from the beginning. Ya know?You can use EditPlus 3 or Beyond Compare 3 to see what is in the .so files. Which just gave me an idea for the Sharp ROM.Kinda, we can't modify anything in the camera.msm7x30 file. I can't even open it to see what calls it supports. I've been working on getting the camera working over the last few days. I've had to teach myself everything(with some help from g60), so it was a slow start. I now have a better understanding of the issue. The camera.msm7x30 is the driver. We are asking it things like how many cameras it has, right now it's not returning a number. I am trying to get that to work(so we can move to the next step) and one possible fix it to manually tell it there are 2 cameras. But that may cause other issues. I don't believe the fb0 file works at all on our device.(I could be wrong, and I might try that down the road). I did find a typo in tj's code, but after correcting it, it still won't boot.
This will be a slow process as every change and update requires a complete rebuild of the code, that even with a fast computer(4Ghz quadcore with 12GB ram) takes over an hour! So I make a change, try it, log the results, compare, make a new change, wait for rebuild, and repeat. So I can only get 3-4 updates a day
EDIT: you may need to install plugins for Beyond Compare.
I hear ya. I wish it was that easy!
I only stepped up to becoming a dev because I saw all the devs leaving and I wanted ICS with a working camera. And with no one working on it, it was going to be up to me to get it done. I already know java and C++ and I know how to use linux so it wasn't a big deal to make a move. I just didn't realize how much of a pain it is to wait for a rebuild of the code. It's light waiting at a red light when you are running late for work!You can use EditPlus 3 or Beyond Compare 3 to see what is in the .so files. Which just gave me an idea for the Sharp ROM.
EDIT: you may need to install plugins for Beyond Compare.
Thanks man! This should help if I can compare the fb0 file to ours and see the difference.
Also, If I were you I would look into the Xperia play ICS beta source, as the phones are built on the same platform.Thanks man! This should help if I can compare the fb0 file to ours and see the difference.
Tokens210
Android Expert
I hear ya. I wish it was that easy!
not trying to take this thread off topic or turn you away from working on it, i like that someones working on it
, but your above quote is why alot of the devs said they didnt like working on the CM projects, cause after all the work they do to make all the fixes, then the rom runs beautifully, then when the CM master source gets and update and they pull it down it breaks all the fixes they had created so they'd have to either reenter ones that still worked, or completely start over with ones that didntnot trying to take this thread off topic or turn you away from working on it, i like that someones working on it
I totally understand. As a web developer I have build many websites based on Drupal or WP. At first i just hacked them together to make it look right and function the way I wanted. Then an update would come out and I would have to redo the whole thing completely.
The work I'm doing on the camera is low level. I'm just trying to get it to open and load. I'm sure there will be other issues in the camera app that will need correcting. It's those edits that could be undone with an update. However, if you write your code using the supported calls, and make wrappers or bridges for edits that can't conform. It should reduce the possibility for undoing your fixes.
This takes a lot of work, and most have decided it wasn't worth the effort. We just want it to work. I may come to the same conclusion, but I have yet to have the frustration of my fixes being undo, so for now I am staying positive
Tokens210
Android Expert
I totally understand. As a web developer I have build many websites based on Drupal or WP. At first i just hacked them together to make it look right and function the way I wanted. Then an update would come out and I would have to redo the whole thing completely.
The work I'm doing on the camera is low level. I'm just trying to get it to open and load. I'm sure there will be other issues in the camera app that will need correcting. It's those edits that could be undone with an update. However, if you write your code using the supported calls, and make wrappers or bridges for edits that can't conform. It should reduce the possibility for undoing your fixes.
This takes a lot of work, and most have decided it wasn't worth the effort. We just want it to work. I may come to the same conclusion, but I have yet to have the frustration of my fixes being undo, so for now I am staying positive
oh i want you to stay positive lol, i was like i said in no way trying to turn you away or anything, ive just seen devs say it and i understand a lil about coding so i know it lol
was just putting it out there lol, but again as i said i like that people here are atleast trying to figure things out, and continue the projects
Yea i understand what you are saying. I watched almost all the Devs leave and we may just have a few left but i'm sure they all had apprentices lol. And even though i am switching over to the EVO V or possibly going to sprint i stick my head in from time to time just to see whats happening in the MT forum just to see the progress and i may try to help from time to time ya know?I hear ya. I wish it was that easy!
freakboykevin
Newbie
Kinda, we can't modify anything in the camera.msm7x30 file. I can't even open it to see what calls it supports. I've been working on getting the camera working over the last few days. I've had to teach myself everything(with some help from g60), so it was a slow start. I now have a better understanding of the issue. The camera.msm7x30 is the driver. We are asking it things like how many cameras it has, right now it's not returning a number. I am trying to get that to work(so we can move to the next step) and one possible fix it to manually tell it there are 2 cameras. But that may cause other issues. I don't believe the fb0 file works at all on our device.(I could be wrong, and I might try that down the road). I did find a typo in tj's code, but after correcting it, it still won't boot.
This will be a slow process as every change and update requires a complete rebuild of the code, that even with a fast computer(4Ghz quadcore with 12GB ram) takes over an hour! So I make a change, try it, log the results, compare, make a new change, wait for rebuild, and repeat. So I can only get 3-4 updates a day
What computer do you have?