Root [ROM] MTDEV-CM9 build 20130120 [BETA]

[rebel69ization]

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

 

[bray462]

What's this Partial camera stuff Please fully explain... does it work or not!

Yes it works...partially.

 

[lfritz3215]

Yes it works...partially.

lol...

 

[jrduncans]

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?

 

[dsmryder]

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?

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.

 

[dsmryder]

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

 

[MikeRL]

Yep. I am no pro now, and can barely write Hello World, but I am probably the last chance we have at fixing it. Just hang in there guys! Once I learn C, I will learn C++ (which is essentially an extension of C). Then I will return. I share the same concern that by that time this phone may no longer be used by anybody. But if you cannot afford to upgrade, once I've acquired knowledge, I'll have your back. Too much time and money has been invested by MTDEV for me to let stuff rot. But it may be dead around here for a while. Just remember my promise! dsmryder try and hold the fort until I get out for summer. By then, if I've tackled C, I should be able to tackle C++ and Android development. This will assist MTDEV, the community, and give me a real world project as practice for my future skills. Everyone else just has too much work to do in real life and the camera has sucked up too much time. We should focus on smoothing out stability, fixing minor issues, and updating MIUI, CM7, CM9, and creating CM10.1. I'd rather see hope and progress than everyone give up. Keep pushing guys! If I cannot fix that camera then, it will either be impossible for anyone to fix, or I will have let you down by being overconfident. But I will try until I am going insane to fix that damn thing! Not a single penny will be accepted by me for fixing it. by then, however, MTDEV could still use assistance financially. I have seen promises made by others. Bounties have been given. And still the camera does not work. I'm here to give an honest approach to help the community, and spur new ROM development, not take the money and disappear. In fact, I will not accept personal donations at all for this project.

 

[jr9306]

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?

 

[dsmryder]

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.

 

[Vortrex]

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.

 

[dsmryder]

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.

Well as you probably know, Linux was built mostly on C. A bunch of the libraries we have are built on C++. The apps are built on mostly Java, as is a lot of the frameworks. I personally work on cars, not build programs for computers, so I struggle with some of the most basic things when I read these files. I do have a book on Android development, but I need to do more than read it. I need to practice it.

I do know some of the more obvious things, like if a files says to copy something over and I remove it and the file doesn't copy over, then I can use that as a template to copy over other files that I think I need. That's the basis of my developing style. Try something, look for changes, try again. I just figured out how to mount the /hidden and /hidden/data partitions tonite (see the Tester folder on the website).

I hope you do decide to help. Any help will, well, help. I can get you to where I am in a relitively short time. Let me know.

 

[sqwerl]

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?

If you have a good handle on C# then Java won't
be that hard. Being a C#/asp.net, Java, and C++ programmer for over ten years the biggest learning curve after you have one down is the platform and IDE. The way Android apps run are totally different than anything I've ever done and will definitely be a change from what you're used to in C#. That's not to say you won't enjoy it or discourage you but I had to stop thinking as a Windows, Linux, C++, or C# developer and even the Java I was used to writing.

There are a lot of things you take for granted when developing on the PC. We get so used to having virtually unlimited memory but you have to manage it efficiently in an Android app because it isn't nearly as large of a heap and you'll get quite a few out of memory exceptions if you aren't careful. If you want to load a bitmap from a C# app you just allocate the buffer and load it. In Android depending on the OS (or SDK) version, you may have to shrink the bitmap or you could throw an exception. C# Windows Forms apps once loaded are kept in memory unless of course they crash or are terminated. With an Android app, you often have to keep track of what state things are in because if you switch to another app the memory the last app was using could be claimed by the new app or a system app at some random time. If the user switches back to the original app, you may not want them to lose the data they had loaded or make the app basically startup all over again.

There are a lot of things I took for granted writing desktop or web apps like various built in utilities that sometimes have to be written from scratch in Android if you don't want to rely on a 3rd party library.

I can send you some links later with some tutorials and helpful tips to get you started. One of the biggest things with Android is learning what not to do which I have some experience with. lol

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.

I wouldn't necessarily say C# is a total Java rip off. Since Java was first, C# became a competitor so its probably fair to assume MS took some ideas from Java. They both share a C++ style syntax but both have automatic garbage collection which C/C++ don't. The two aren't really an apples to apples comparison since C# was introduced with asp.net web development and the two have taken on a life of their own.

Mono is a project that was created to develop Linux apps in C# and now also features a platform called Monodroid which allows Android apps to be written in C# and existing C# libraries to be included as long as the features are supported. It is fairly costly if you want to deploy apps to physical devices but running apps on the simulator is free.

 

[Prevailious]

I just fell in love with the CyanogenMod Dubstep lol!

 

[adamto]

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

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.

 

[allenj2020]

Well, the Bluetooth problem I was having apparently isn't just on this version. I dropped back to the 20121228 CM7 and I still can't connect to either of the Bluetooth devices I used to use back when the phone was stock.

 

[Ken2Chill]

If I change the lockscreen to none, does it.stop the phone from sleeping or going into deep sleep?

 

[BSydz]

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.

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.

I completely feel you on finding stuff taking forever, I have been trying to revert the system gpu drivers but can't get the screen to come up, it only works with the updated kgsl kernel drivers from Doomlord, I have searched for days trying to find the old commits and put them together, but can't seem to figure it out.

As far as the camera goes, there are still some kernel issues. First is the front camera, hm0357 will load fine according to the kmsg but hm0356 runs into an I2C slave addr 0x34 not connected error half way through loading. Also I believe the cameraHal needs to be worked out. I think it is seeing the back camera as both cameras. I can switch cameras and they have different settings but it is always the back camera.

EDIT: I loaded an X6 GB ROM to check out the kernel log and it also has the fail for hm0356 so this shouldn't be an issue.

For anybody who gets a random reboot, if you have time post your last_kmsg, not in this thread, should probably do it here http://androidforums.com/triumph-all-things-root/678555-dev-triumph-kernel-thread-01-19-2013-a.html. List your operating system and what was going on when the reboot happened.

You can get your last_kmsg a few ways it is located in /proc you will need a root explorer or adb to retrieve it.
[HIGH]adb shell cat /proc/last_kmsg
or to save to text file
adb shell cat /proc/last_kmsg > /path/where/save/last_kmsg.txt
[/HIGH][HIGH]adb shell dmesg
or to save to text file
adb shell dmesg > /path/where/save/last_kmsg.txt[/HIGH]

 

[jameyhowell73]

Just when I thought it'd be another month before any activity, BAM, they come back in numbers again. Thanks all you developers!

 

[jrduncans]

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.

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...

 

[dsmryder]

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.

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.

If I change the lockscreen to none, does it.stop the phone from sleeping or going into deep sleep?

The phone goes into deep sleep after the screen shuts off, assuming there aren't any wake locks held.

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...

You would have to use one of the thunderprops that I made for the specific build. Since no one gave me feedback I stopped making them. Let me know.

 

[adamto]

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.

 

[dsmryder]

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.

I know some people have left. I think we could start with them.

 

[dsmryder]

I made a build that has the buttons like the tablets. I'm playing with settings. Looking for more usefull stuff.

 

[jameyhowell73]

Hm, I feel like an idiot here...not sure what's up but for some reason I cannot get my phone to just vibrate... I go into settings - volume - select vibrate, select the mode (select vibrate there)... select vibrate on ringer status etc....(if I don't touch the volume keys after selecting vibrate mode then it'll do fine, when I do up the ringer and try to go down on volume back to vibrate, can't find it, just goes to silent) I actually don't even need a silent mode with no vibrate but I cannot get back to where on the volume up/down keys if I press down volume all the way I cannot get to vibrate mode, only silent mode. Anyone else having this issue? I'm sure it's simple to get back to the right mode I've been using but man, can't figure it out.....

 

[Urfreaky]

So I got a replacement phone yesterday and I activated it, then flashed this ROM. With this ROM whenever I answer/send a phone call the phone reboots. I've tried reflashing a few times and it still does it. I've flashed back to stock and calling works fine. Any ideas why?