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

Root The road to Android ICS 4.0 on the Triumph

If you were to get everything working would you realease it or wait for cm9?

clicked the thanks instead of reply :rolleyes:

Disclaimer: much of what follows is educated guesses and not direct knowledge. Anyone who is in the know, please feel free to correct.

I think the answer to that is no as this is just the SDK and not the actual android os. My understanding of what that means is that it's using emulation to run ICS and not running it natively. This might mean that performance would be terrible and many things just couldn't be made to work. (If I am not correct in my understanding of SDKs on actual phones, someone please correct me).

My guess as to why Isaac will wait for CM9 is because they handle a lot of the background work that can be standardized accross phones. It will give him an interface to work toward for getting different pieces of the hardware working. Because this has already been largely done with CM7 (and since many of the interfaces will likely stay the same), much of the work would have already been done.

Overall, it would likely take less time to wait on CM9 and work from there than it would to start from scratch on his own with the CM9 source.
 
There's a couple things you guys can take away from this. First, and probably the most important one, is that our kernel (2.6.32.9) works just fine. Obviously, the touchscreen doesn't work, but I believe I may have that working soon. There are probably other issues, but I can't test the SDK fully, yet. Secondly, ICS is definitely possible on the Triumph. I'm not sure there were any doubts on that, but it's on there and it comes up (albeit, it is the SDK).

One good thing is the CM device list contains a boatload of MSM7x30 devices (like ours). So, that generic code and configurations that were applicable to us in CM7. should be applicable to us in CM9. Tickerguy gave us a tremendous head start on the CM9 project. I don't doubt that most of the fixes found in CM7 can be applied to CM9.

Who knows? Maybe Motorola/FIH/Huawei whoever will be kind and release us an ICS update...

Thanks IssacJ87! I was pretty bummed when Tickerguy said he was leaving VM-land. CM7 has been the best thing to happen to my Triumph. Living in a semi-rural area, Sprints 3G wasn't very reliable. Now it is! Plus the additional settings on CM7 make it mucho better. I can't wait to see what cool surprises that ICS has to offer our Moto. Thanks for all your efforts, it is GREATLY appreciated!:D
 
I made this post a sticky because it's highly likely it will become a thread involving another very useful rom. It's also good to have stickied because it may help to speed up development as it will make it more noticeable and that may help further the progress!

Thanks Isaac for your continued work on our behalf. ^_^

P.S If I'm wrong about this, Feel free to remove the sticky. I just feel it to be an essential developmental thread which is just as important as a guide (Walkthrough) or rom itself. =]
 
i guess odds are VM will just keep adding better and better phones which gets them off the hook so to speak for keeping the triumph updated..although for me...it doesnt get much better than the triumph..the dual and quad cores these days are quite the overkill..and id hate to see battery size and life on a dual core monster phone

In my opinion, Triumph is still the best phone VM offers. And spec wise, every phone after the Triumph is in fact worse. This is a phone worth an update from VM, but I doubt it.
Ice Cream Sandwich ported to this phone would be outstanding!! :)
 
In my opinion, Triumph is still the best phone VM offers. And spec wise, every phone after the Triumph is in fact worse. This is a phone worth an update from VM, but I doubt it.
Ice Cream Sandwich ported to this phone would be outstanding!! :)

So far the triumph is the best, but also you have to think... we have no contract which means we pay full market price and a lot of newer phones have a market price of $600 or more... I doubt that there would be many people who could afford that or would be willing to spend that much... But ICS would be awesome!

BTW Isaac keep up the good work! :D
 
clicked the thanks instead of reply :rolleyes:

Disclaimer: much of what follows is educated guesses and not direct knowledge. Anyone who is in the know, please feel free to correct.

I think the answer to that is no as this is just the SDK and not the actual android os. My understanding of what that means is that it's using emulation to run ICS and not running it natively. This might mean that performance would be terrible and many things just couldn't be made to work. (If I am not correct in my understanding of SDKs on actual phones, someone please correct me).

My guess as to why Isaac will wait for CM9 is because they handle a lot of the background work that can be standardized accross phones. It will give him an interface to work toward for getting different pieces of the hardware working. Because this has already been largely done with CM7 (and since many of the interfaces will likely stay the same), much of the work would have already been done.

Overall, it would likely take less time to wait on CM9 and work from there than it would to start from scratch on his own with the CM9 source.

Good response. Essentially, the SDK is used to help app developers test and run their apps. What I'm running is a system and boot image dump from the ICS emulator off the SDK packed with our kernel.

The CM team makes it easier for us to build Android for our specific device. Addng the device configs is tedious enough in itself. It would be a royal pain in the ass to try and tailor the ICS AOSP source.
 
So far the triumph is the best, but also you have to think... we have no contract which means we pay full market price and a lot of newer phones have a market price of $600 or more... I doubt that there would be many people who could afford that or would be willing to spend that much... But ICS would be awesome!

BTW Isaac keep up the good work! :D

EXACTLY. This is what kept me from getting a bad arse T-Mobile phone to go with their prepaid plans. The prices on phones off contract are harsh! Especially when compared to a laptop or something. I guess people want the ultimate in portability? Sure the Triumph full price is reasonable I suppose. But I still opted to get my phone through QVC mwuahahahaha. I pay $70 something once per month until its paid off. So if virgin mobile does happen to get more and better phones, I hope QVC will give us the flex pay options for those phones as well :P
 
Hi all,

Sorry for the newb question, but what is the advantage of running ICS? Is there new functionality?

Isaac - thanks for all your work on MIUI - I love it and find something new and cool about it everyday.
 
Hey, you beat me to it!

I just pulled your cm7 repository, as well as AOSP yesterday, intent on making an ugly hack that would work.

I'm interested in helping development. I'm mostly an embedded/C guy, and don't know much about Android, but I'd like to help, especially with more hardware / Linux kernel stuff. What's the best way to contact you about development? Do you have an IRC channel?

I guess I'm not surprised that the 2.6.32 kernel runs ICS userspace. The only exotic kernel features Android uses are its own weird message bus thing. Luckily Google didn't break that.

Unfortunately, the very top bit of my Triumph's touch screen is suddenly not working. I may be without a dev phone for a bit as I don't know if I want to risk running non-stock on my phone in case it fails completely. I hate sending it back over a few pixels of the capacitive screen not working, but not being able to drag the notification bar is annoying...
 
@Isaac - Any chance you'd start letting me test, that way I could make videos as you're working on it so people could see the progress you are making, which might reduce the number of repeated questions...

Either way, glad to see you working on this!
 
@Isaac - Any chance you'd start letting me test, that way I could make videos as you're working on it so people could see the progress you are making, which might reduce the number of repeated questions...

Either way, glad to see you working on this!

He's running the SDK on it. Not really anything for people to test yet.
 
Hey, you beat me to it!

I just pulled your cm7 repository, as well as AOSP yesterday, intent on making an ugly hack that would work.

I'm interested in helping development. I'm mostly an embedded/C guy, and don't know much about Android, but I'd like to help, especially with more hardware / Linux kernel stuff. What's the best way to contact you about development? Do you have an IRC channel?

I guess I'm not surprised that the 2.6.32 kernel runs ICS userspace. The only exotic kernel features Android uses are its own weird message bus thing. Luckily Google didn't break that.

Unfortunately, the very top bit of my Triumph's touch screen is suddenly not working. I may be without a dev phone for a bit as I don't know if I want to risk running non-stock on my phone in case it fails completely. I hate sending it back over a few pixels of the capacitive screen not working, but not being able to drag the notification bar is annoying...

I had the same problem with stock when the phone was brand new and there is a calibration in settings to adjust the touchscreen....try that first before you assume it's hardware failure and send it in....
 
There's a couple things you guys can take away from this. First, and probably the most important one, is that our kernel (2.6.32.9) works just fine. Obviously, the touchscreen doesn't work, but I believe I may have that working soon. There are probably other issues, but I can't test the SDK fully, yet. Secondly, ICS is definitely possible on the Triumph. I'm not sure there were any doubts on that, but it's on there and it comes up (albeit, it is the SDK).

One good thing is the CM device list contains a boatload of MSM7x30 devices (like ours). So, that generic code and configurations that were applicable to us in CM7. should be applicable to us in CM9. Tickerguy gave us a tremendous head start on the CM9 project. I don't doubt that most of the fixes found in CM7 can be applied to CM9.

Who knows? Maybe Motorola/FIH/Huawei whoever will be kind and release us an ICS update...


Wouldn't it be easier to use the ICS source code rather than porting an SDK?
 
I got the touchscreen working. Unfortunately, I wasn't able to use the changes tjstyle shared with everyone here: [DEV]Porting Touchscreen driver for Android 4.0 (ICS) ROMS - xda-developers

I spent hours wondering why the patch wouldn't work. Turns out, we have a completely different touchscreen panel than the other FB0 variants. I wrote some new code into our driver and viola, we have a working touchscreen in ICS.

Time will tell if the kernel changes were actually necessary.
 
I got the touchscreen working. Unfortunately, I wasn't able to use the changes tjstyle shared with everyone here: [DEV]Porting Touchscreen driver for Android 4.0 (ICS) ROMS - xda-developers

I spent hours wondering why the patch wouldn't work. Turns out, we have a completely different touchscreen panel than the other FB0 variants. I wrote some new code into our driver and viola, we have a working touchscreen in ICS.


Awesome, so now that the touch screen is working, whats next? Do you know what's working and what's not? If you need any help with anything I don't know much about linux but I'm a quick learner! :)
 
Well, that's pretty cool, but it's misleading. I'm just running the ICS SDK dump to get the touchscreen working. I don't have any intentions of releasing the ICS SDK as anybody can download that.

To clarify, I don't technically have a a "real" build of ICS that works for the Triumph.

no i figured, but this is good as many devs and such search these sites daily and maybe this could get some possible more help on this for your sake.

also think how this makes people look at google and motorola, and makes google and motorola look at the community. they haven't even released the AOSP source code for 4.0 yet and all these phones are already getting it ported through the SDK. i mean it's expected that the newer higher tier phones are gonna have quick development on this as devs want to get it ported to these quickly because they want the newest and best, but to have what is considered a mid tier phone, and one that is a pre-paid through virgin already getting it ported is not even a kick in the nuts for these people at the companies. it's like throwing napalm on them and burning them in public.
 
Looks great!

If you ever need any help just PM me and I could give you my Skype, I have no experience in coding ROMs and the like, but I have coded in Java on both Android and normal computers and would be willing to learn if you willing to be patient.
 
Back
Top Bottom