rebel69ization
Well-Known Member
Try the Pro version for complete camera features include front camera, flash light, more image layout and effects!
Anyway that's what they say.
Pro fcs when you try to open the app
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Try the Pro version for complete camera features include front camera, flash light, more image layout and effects!
Anyway that's what they say.
What's this Partial camera stuff Please fully explain... does it work or not!
Yes it works...partially.
Just installed this ROM last night. One of the reasons I wanted to upgrade was to try to play Ingress, which required a newer Android version. If I go to the play web site to install it, it says "This app is compatible with your Motorola WX435." and claims to install it. But on the phone it doesn't install, and you go to the app in the Play Store, it says "Your device isn't compatible with this version." From the Ingress website it appears that the Triumph should meet all the requirements once you have an Android version higher than 2.2. Is it possible there's something else I need to do to get the Play Store app on the phone to recognize its updated state, or is this something anybody else has hit?
I'm in my 2nd semester of C# in college. Is it any good for Android development? If so can anyone steer me in the right direction to get started?
I am assuming that Android requires C++ for development? I know that to create apps, one would need Java. Does this same thing apply to everything else pertaining to Android? If not, what language(s) are used?
By looking at the github, I can tell it's some sort of C language from the (very) basic C knowledge I understand. Unfortunately, I only fluently know irrelevant languages for Android development (Javascript, PHP, SQL, HTML, CSS, Pawn, Squirrel, and Lua). I guess if anybody needs help with something of that sort, I could pitch in. I have found though, that once I have one language down, most of the rest come a LOT easier, as basic statements, methods and etc seem to work the same.
I own a Triumph (running CM9 currently) and would like to help in any way I can.
I'm in my 2nd semester of C# in college. Is it any good for Android development? If so can anyone steer me in the right direction to get started?
Without actually knowing the different languages I can't say for sure, but what I have read I would say no. C# isn't used in Android as it seems to be a Java rip-off by Microsoft. Again, that's what I have read. If you want to have a look at what I was thinking you could start here.
For the time being, I've decided to work on other things. Maybe when we find another "C++" guy (Mike is working on being that guy) we can come back to the camera. I hope that this won't go beyond the life of the phone. Many people have moved on because of whatever. I know I will keep working on this project for quite some time.
I just want to have some wins instead of failures. More in the future
Good to see you back. I have been working on the kernel side of things and trying to figure out what most of our issues are. The two biggest issues that I have found scanning through countless last_kmsg is that we have wifi and kgsl(gpu driver) issues. We also have issues with our init.triumph.rc, as seen by the countless "init: cannot execve('/'): Permission denied" lines. I have about five different kernels for CM9, the one with the cam stuff from the 2.6.35.7 kernel that we use now plus two using the M410 kernel as a base one with the updated kgsl drivers from Doomlord sources and one not. Also have the 2.6.35.7 kernel that gets a reset call from the modem/amss which reboots the phone like clockwork. And I have put together one with all the camera stuff from the 3.0.8 kernel. I wish I knew how to debug the errors, I have read a few write ups but just don't get a few concepts as they are written for people that actually write the code, and know how to use switches and stuff.Hey dsmryder and all,
I've been out of the loop for a while, but I should be able to find some time to help look into this again. It looks like you guys have made some great progress!
My problem is I can only put in a couple hours here and there, and when I was looking at this stuff before I would spend so much time just tracking stuff down I was left with very little time to actually try changing things. Anyway, it sounds like you may have nailed down a kernel, which is good, and is what I had been struggling with.
I'll try to catch up on some of the forum activity, and try to get the camerahal test going. Again, I'm seeing you need c++ help, is there some specific c++ thing I can help with, or is it just because this camera stuff is in c++? From what I've seen of the c++ code it's pretty simple; the binary blob (and making sure we have the right interface to the version of the blob/kernel we are trying to use) is much more scary to me.
It might be an issue with the build.prop. What happens is the play store looks at this file and can match items for compatablity. This is why the thunderprop worked for us. It told the play store we has GB instead of FroYo and we had a Thunderbolt.
Hey dsmryder and all,
I've been out of the loop for a while, but I should be able to find some time to help look into this again. It looks like you guys have made some great progress!
My problem is I can only put in a couple hours here and there, and when I was looking at this stuff before I would spend so much time just tracking stuff down I was left with very little time to actually try changing things. Anyway, it sounds like you may have nailed down a kernel, which is good, and is what I had been struggling with.
I'll try to catch up on some of the forum activity, and try to get the camerahal test going. Again, I'm seeing you need c++ help, is there some specific c++ thing I can help with, or is it just because this camera stuff is in c++? From what I've seen of the c++ code it's pretty simple; the binary blob (and making sure we have the right interface to the version of the blob/kernel we are trying to use) is much more scary to me.
If I change the lockscreen to none, does it.stop the phone from sleeping or going into deep sleep?
For what it's worth, it now works correctly for me when I switched to the CM7 ROM (flashing thunderprop just caused my phone app to constantly FC). That makes me believe that there is something not quite right with the settings installed by this ROM. I also just noticed that it identifies my phone as "Motorola Triumph" in CM7 instead of "Motorola WX435" on CM9. I'm sure that part doesn't matter, but I just wonder why the CM9 build.prop shouldn't have the exact same phone attributes (other than the Android version) as the CM7 build...
Well, it's C and C++. I know, I know, they are simular, but not the same. One of my main issues is I don't have any experaince in programming. I work on cars for a living, not computers. Most of my triumphs (pun intended) have been through simple trial and error, with a side of logic. BSidz (sup bud) mentioned the error logs he has been working through, which I have just started on my own. Still not sure how to work that side of things. Anyway, I was hoping someone who knew C could work through the camerahal and put in some debugging code. That would help trace what is going on. Of course the person with the experiance would be free to dictate the proper cource of action.
I can certainly put some debugging code into camerahal. I'll start there after I finish getting my environment setup again.
Also, does anyone know if there are any extra developer phones around? I know g60 mentioned there may be one available before.