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

Root [Q/A] MTDEV Open Discussion

G

g60madman

Guest
Since I don't want to leave anyone out I figured I could continue here

Taken from
http://androidforums.com/triumph-all-things-root/582999-rom-port-u9000-81-2-2-2-triumph-3.html

Izzard said:
g60,
do you mind shifting a bit MTDEV minds and forces toward this ROM?
If you guys polish this thing to perfection, and release under back_to_stock_better_everything edition, you may start charging Virgin Mobile and Moto for fixing their fails.
Click to expand...

I don't think we can ever change their minds at least IMHO. I have no issues with working on this ROM or having others from Team MTDEV work on it that would like to work it. Honestly though the only major issue is the voice mail bug, which can be fixed by wsimon's hack. Unless I am missing something else?

Also I have tried some hacks on the GB Rom Bsydz created but I have had no success. The problem with all these ROM ports is there is no source code at all so it's all decompiling and editing code which is a pain in everyone's butt. Specially because it's smali code.

Right now I have contacted one of Qualcomm's developers from the MSM/QSD Android Enablement Project and hoping he can guide me to picking the right branch and hopefully we can build code for our phone. I am hoping we can succeed like dzo has done for the Huawei X5 not to be confused with our sister phone the X6. It would basically be stock Android with out all the CM settings. They have Cupcake all the way up to Jelly Bean so this maybe another option for source code built ROM's.

Also Chairshot has gotten really close with the CM7 ROM running Sharp Camera libs. If we can solve the Camera lib issue it should be pretty straight forward for using tjstyle's CM9 Camera libs in our CM9 ROM. Still won't have HDMI right this second, but something we can focus on.
 
Any and all help is always appreciated by all of the devs here. We are working our butts off trying to get the community the best ROMs possible for our phone. I would love to do an AOSP GB ROM built from scratch, I think the only way that we can get our phone to the next level is to not include as many prebuilt files. I know it is impossible to not use any, but I think that is the way to go. I am willing to help in any way possible. I am gonna shift my focus to CM7 and GB, so I can get better acquainted with the system files and source. CM10 is kicking my butt, but was a good place for me to get deeper into source code. I'm also gonna try some experiments with taking telephony code from the Stock ROM framework and getting it to work on the U9000 ROM. If I can figure out how to edit the smali files between two working ROMs and get it working, then it will be more attainable with GB.

Good luck everybody.
 
I certainly understand where Izzard is coming from as the U9000 ROM seems to be the most flawless, and most functional ROM our phone has for now. The Sharp ROM is great but I wasn't crazy about the launcher and I was also having weird issues with Sharp ROM such as random hard locks causing me to have to pull the battery to reboot the phone - that might have been due to me using the experimental kernel though.

With that said, I think the devs should work on whatever interests them. It's their spare time so they should work on whatever keeps them motivated.

If the devs are looking for opinions though, I'd be happy to chime in :D. Over the time I've owned the MT I've tried a bunch of roms: Tickerguys, CM7, CM9, CM10, Sharp, and U9000. IMO, I think the devs should dump CM7 and focus on CM9. I really wanted to stick with CM9 and it seems so close to being great but there were just a couple of things that were too problematic for me to stick with it. Once the devs nail down the issues with CM9, there is no doubt it will be the #1 ROM for the MT by far. CM10 still has a long way to go. I can't lie and say I wouldn't like to see the U9000 get some love also because that ROM is already #1 in my book, but I definitely miss some of the features of CM9.

In any case, I'm extremely grateful to all of the devs for spending their free time working so hard to make the phone great for all of us. I know how easy it is to burn out working on this stuff, especially when you don't have the source code and have to decompile and decipher everything - that's why I think it's best for the devs to work on whatever keeps them motivated and us users just have to be patient and wait for good stuff to happen.
 
Inc0gnit0 said:
I certainly understand where Izzard is coming from as the U9000 ROM seems to be the most flawless, and most functional ROM our phone has for now. The Sharp ROM is great but I wasn't crazy about the launcher and I was also having weird issues with Sharp ROM such as random hard locks causing me to have to pull the battery to reboot the phone - that might have been due to me using the experimental kernel though.

With that said, I think the devs should work on whatever interests them. It's their spare time so they should work on whatever keeps them motivated.

If the devs are looking for opinions though, I'd be happy to chime in :D. Over the time I've owned the MT I've tried a bunch of roms: Tickerguys, CM7, CM9, CM10, Sharp, and U9000. IMO, I think the devs should dump CM7 and focus on CM9. I really wanted to stick with CM9 and it seems so close to being great but there were just a couple of things that were too problematic for me to stick with it. Once the devs nail down the issues with CM9, there is no doubt it will be the #1 ROM for the MT by far. CM10 still has a long way to go. I can't lie and say I wouldn't like to see the U9000 get some love also because that ROM is already #1 in my book, but I definitely miss some of the features of CM9.

In any case, I'm extremely grateful to all of the devs for spending their free time working so hard to make the phone great for all of us. I know how easy it is to burn out working on this stuff, especially when you don't have the source code and have to decompile and decipher everything - that's why I think it's best for the devs to work on whatever keeps them motivated and us users just have to be patient and wait for good stuff to happen.
Click to expand...

Thank you, we have been working so much on CM7 because most of it translates to other ROMs, like the gps fixes, the 3g improvement, and whatnot.

Working in smali code sucks. On top of that, it doesn't always recompile back. We have a good group and, I for one, am not that experianced in working smali, but I could learn. Maybe learning some smali code will help me work through some of the other ROMs.
 
Today MTDEV team has a very organized team of people working hard to keep this phone alive. So far under the brand of MTDEV we have CM7, CM9, CM10 and GB Roms. Why not add old Froyo to the portfolio? Or even MIUI ? I don't use it at all, but people do. There are plenty of us who still enjoy the feel of it, still have problem with it. While I have no clue what smali is and I don't want to take your time working on something that does not motivate you, I think having fully working 2.2 with everything working out of the box is a big plus.
The idea of dumping Stock Froyo all together and not to bring it from back up even if you need to re-activate or HDMI.

I do appreciate BSydz's work but I feel that 4 (6,8,12) devs are better than one, especially taking the fact that U9000 is almost there. I mean maybe forking around X6's code will give you guys better ideas how to fix GB Rom 3G or fixing HDMI on any future builds.

Anyway, I'm trying not to take your valuable time on going back in time and fixing stuff that most people don't use anymore. However I do feel that X6 ROM still needs a bit work to become a full superior stock (yes even in build.prop), will all the goodies what we have and big MTDEV logo on it.

Again, this is open discussion, the community decides there no time to look back and beat the dead horse, let be it. We will jump to CM9, 10 or 11 and 12 with no regrets, just keeping stock for very rare occasions.

Thank you developers for keeping it interesting, for keeping it alive and exciting. On behalf of all noobs like myself who have no idea what QEMU_HARDWARE := true does I thank you.
 
dsmryder said:
Working in smali code sucks. On top of that, it doesn't always recompile back. We have a good group and, I for one, am not that experianced in working smali, but I could learn. Maybe learning some smali code will help me work through some of the other ROMs.
Click to expand...

I don't think learning smali (ie. assembly language / machine code) is the hard part. In my experience when you take something written in a higher level language and decompile it into assembly it basically turns into spaghetti-code and trying to make sense of it can be a real headache :-).
 
I don't even own a triumph. I mod my buddies at his request. I do have an hp touchpad. The devs just got camera to turn on. Buggy, but progress. And the tab came with webos on it. There were no drivers to begin with. Somehow, they got it.

You guys are close. Keep with it. It's just a matter of time. Look around at the way some of the other older phones managed to get camera on ics. I know its not same hardware but i assume patching old drivers was something other devs had to figure out too.
 
havikx said:
I don't even own a triumph. I mod my buddies at his request. I do have an hp touchpad. The devs just got camera to turn on. Buggy, but progress. And the tab came with webos on it. There were no drivers to begin with. Somehow, they got it.

You guys are close. Keep with it. It's just a matter of time. Look around at the way some of the other older phones managed to get camera on ics. I know its not same hardware but i assume patching old drivers was something other devs had to figure out too.
Click to expand...

Yeah I have been following his work for some time as a lot of the errors we are getting, he was getting. I will try and spend some time on this and see if I can make some head way with CM9.
 
Inc0gnit0 said:
I don't think learning smali (ie. assembly language / machine code) is the hard part. In my experience when you take something written in a higher level language and decompile it into assembly it basically turns into spaghetti-code and trying to make sense of it can be a real headache :-).
Click to expand...

Exactly, I looked something a long time ago when I was still having trouble downloading my first repo. I was thinking, when I was looking through Tickerguy's original commits, I saw somewhere there was a change from*86 to "me" on voicemail. I don't know if BSydz got a chance to look at it, but I know I can find it again.
 
the two biggest things I think should be focused on is CM9's camera and CM7's video flicker soon as cm9 gets a working camera idc if its buggy just as long as it works soon as that happens that will be my daily i could really careless about any other roms except cm10 and thats what I would be focused on next
 
I found this if it is any help..I am not too good with these os, i am microsoft os admin, with some Linux experience just trying to help, i want my triumph to be awesome and updated , especially since someone in here found the nice 25 dollar monthly plan ) I am on leave right now for back pain so if this makes no sense its the pain killers sorry.


Triumph Kernel Source Released - SDX-Developers Forum


http://sourceforge.net/projects/triumphwx435.motorola/files/

http://sourceforge.net/motorola/triumphwx435/home/Home/
 
boondox22 said:
I found this if it is any help..I am not too good with these os, i am microsoft os admin, with some Linux experience just trying to help, i want my triumph to be awesome and updated , especially since someone in here found the nice 25 dollar monthly plan ) I am on leave right now for back pain so if this makes no sense its the pain killers sorry.


Triumph Kernel Source Released - SDX-Developers Forum


Triumph WX435 - Browse Files at SourceForge.net

Triumph WX435 / Home / Home
Click to expand...

Thanks for posting. We have been aware of the site for some time and still waiting for Motorola to play nice

Triumph WX435 / Discussion / Discussion

I think if everyone signed up for an account and posted we might get some where but I doubt it :p
 
dsmryder said:
Exactly, I looked something a long time ago when I was still having trouble downloading my first repo. I was thinking, when I was looking through Tickerguy's original commits, I saw somewhere there was a change from*86 to "me" on voicemail. I don't know if BSydz got a chance to look at it, but I know I can find it again.
Click to expand...

I found the commit I was talking about. I also looked for a system.prop in the ROM, but I didn't see one. I wonder if it's parsed somewhere else?

I guess my real queston is, sense this isn't built from source, how could one push this through?
 
dsmryder said:
I found the commit I was talking about. I also looked for a system.prop in the ROM, but I didn't see one. I wonder if it's parsed somewhere else?

I guess my real queston is, sense this isn't built from source, how could one push this through?
Click to expand...

Keep in mind that I currently know very little about the Android file structure, so forgive me if this sounds stupid - and I'm sure it will because someone probably would have done this already if it were this simple, but here goes.

Couldn't the line that Tickerguy added to the system.prop (ro.cdma.voicemail.number=mine) just be added to the build.prop instead? I wasn't able to find an actual system.prop file in the file system so I'm assuming that it's normally compiled with the source code? Or is the data in system.prop loaded after build.prop and therefore any changes in the build.prop are overriden by the system.prop?

I don't want to clutter the thread so there's no need to reply if you don't want to :-)

Edited to add: After a little reading, it appears that build.prop and system.prop actually have the same contents? Is it renamed during compile?
 
dsmryder said:
I found the commit I was talking about. I also looked for a system.prop in the ROM, but I didn't see one. I wonder if it's parsed somewhere else?

I guess my real queston is, sense this isn't built from source, how could one push this through?
Click to expand...

The system.prop actually turns into the build.prop after the code is compiled. You can try to edit the build.prop and see what happens.

Sleepingsirens said:
Why not do it? I just made one, make a thread about it g60, youve got nothing to lose, and you got my support, and the support of the whole forum :)
Click to expand...

I already did post on there about device files and got spanked, also we have asked for camera libs and got spanked. I just got done posting a plea on the following group

https://groups.google.com/forum/#!forum/android-building

Will see if they approve my post.
 
Inc0gnit0 said:
Keep in mind that I currently know very little about the Android file structure, so forgive me if this sounds stupid - and I'm sure it will because someone probably would have done this already if it were this simple, but here goes.

Couldn't the line that Tickerguy added to the system.prop (ro.cdma.voicemail.number=mine) just be added to the build.prop instead? I wasn't able to find an actual system.prop file in the file system so I'm assuming that it's normally compiled with the source code? Or is the data in system.prop loaded after build.prop and therefore any changes in the build.prop are overriden by the system.prop?

I don't want to clutter the thread so there's no need to reply if you don't want to :-)

Edited to add: After a little reading, it appears that build.prop and system.prop actually have the same contents? Is it renamed during compile?
Click to expand...

I know the build.prop is modified by over rides in the system.prop. One reason I know is the bootanimation sound entry is on the build.prop, but isn't pulled over like some of the other lines. If I knew what responded to the system.prop, I could concentrate in that area. I tried looking around, but didn't find where the file that wsimon made his change for gets made. I didn't search for all scripts, just boot, voice, 86, and some other stuff.
 
g60madman said:
The system.prop actually turns into the build.prop after the code is compiled. You can try to edit the build.prop and see what happens.
Click to expand...
then why isn't the entry for running the bootanimation sound in threre?

I am either going crazy, our have already gone crazy. I knows I made the changes. Now I can't find the commit for it. I'll have to figure this out when I get home. I'll also test the build.prop idea when I get back to work.
 
dsmryder said:
then why isn't the entry for running the bootanimation sound in threre.
Click to expand...

As far as I can tell it's calling the hidden and hidden data folders. Since we never use those areas it still contains the stock VM bootanimation, and VM start-up sound in there. If you delete your bootanimation from a ROM and and flash the ROM it will default back to VM's boot animation and startup sound.

Just for an example when you download the stock Bsydz Sharp Froyo there is no bootanimation.zip located in system/media and the same goes for b_randon14's stock VM and MTDEV-UNROOT. However if you check say CM7 through CM10 you will see the bootanimation.zip in system/media.

Hope this clarifies.
 
Another question about hidden data folders.
Stock, Sharp and U9000 - when you flash either of them and plug phone to USB Windows PC, it shows up as CD drive with some installations folders.
When you flash CM+ roms, the PC won't recognize it till you check Turn USB storage on your phone.
It's not crucial at all, just wondering.
 
Izzard said:
Another question about hidden data folders.
Stock, Sharp and U9000 - when you flash either of them and plug phone to USB Windows PC, it shows up as CD drive with some installations folders.
When you flash CM+ roms, the PC won't recognize it till you check Turn USB storage on your phone.
It's not crucial at all, just wondering.
Click to expand...

With the stock ROM's there is scripts that calls the hidden folder which activates the ISO and mounts it as a CDROM. Those scripts where never included in CM builds since the start.
 
All the Froyo ROMs for the X6 variants including ours, call on the hidden partition, cause they all have one. So, before I changed the stock theme on the Sharp ROM it would boot after install with the pink VM wallpaper and a few other VM things. The .iso file with the drivers is in there. I also use the drivers from the Sharp nb0 on my PC. The build.prop edit for voicemail=mine has been tried and few other things also. The thing is, when the ROM reads our amss.mbn, it connects to the network specified, so while GSM is the main network on these ROMs with WCDMA built in, it shows as the normal network. There are icons in the framework-res that are for GSM(regular phone signal icon), CDMA(has a C in the signal icon), Roaming(R), and so on. But it shows just the regular. I didn't try gsm instead of cdma in the build.prop edit though. It is confusing but it just works, I haven't quite figured it out yet. I believe the kernel is what points to the boot sounds and animations, and is why the boot animations are in system for the CM ROMs. I think that the phone.apk and things in the framework are what allow it to get our number for voicemail. *86 is the default VM number for almost all GSM phones, I believe.

Sorry about the scattered thoughts as I read back through some of the posts I just added them in.
 
i also inquired with virgin mobile but same answer

Thanks for contacting Virgin Mobile Customer Care.

We regret to inform you that currently, we do not have any updates for your Motorola Triumph phone. Whenever there is one available, we will let you know.

We are sorry for any inconvenience this may cause.
 
You must log in or register to reply here.
Back
Top Bottom