Root The road to Android ICS 4.0 on the Triumph

[isaacj87]

Ugh, I'm very confused about the Android driver landscape right now. I'm used to having all the drivers I needed in mainline... does the Android kernel tree keep any more around? Or is it the job of CM7 to keep track of all the drivers? Or individual port maintainers?

Also, if you're using your Gingerbread kernel, why would the touchscreen suddenly stop working? Or is there some userspace component?

BTW, why are you using prebuilt SDK ROMs? Is AOSP in such bad shape that you can't build the SDK ROM yourself?

Simply put, Android kernels are a mess. I guess, technically, you could say there is a "mainline" kernel (https://github.com/android/kernel_common), but if you were to try and build it for our device, nothing would work. Manufacturers put out kernel sources for each specific device (with absolutely no documentation I might add). They package up what they got and literally just throw it at us. And yes, I know what you're thinking, it is a HUGE pain in the ass.

I'm not sure why they do this, but I'm assuming it's to cut down on the size. Plus, hardware varies so drastically from device to device. So, to answer your question, it's up to individual maintainers. I'm not using a Gingerbread kernel (2.6.35). I'm using the only version Motorola gave to us (2.6.32). I've been looking for a long time to find a mailing list or something that will inform us of upstream changes, but I haven't found anything. Basically, ICS, on the userspace side, changed the way touch events are recognized. The kernel changes I'm doing are a workaround until something like this (Gerrit Code Review) happens.

The reason why the Cyanogenmod team is so important to the community is because they make it possible for anyone to build AOSP for their specific device. Just add your device configs to their tree and viola. ATM, CM9 can only be built for one device (I believe it's the Nexus S). I don't dare try and build AOSP ICS. Honestly, it would probably take less time to just wait until CM9 is ready. However, I want to be prepared for the day that CM9 is in better position. That's why I'm using the SDK to get the touchscreen working. More importantly, if I'm not around when that day comes, I'd like to get the next dev in a good position too.

The touchscreen driver (IMO) was a mess. It turns out we don't have any issues with axis inversion, but if we did, it would of been a pain in the ass to try and fix it in its previous state.

 

[ebnight]

Hey Isaac,

it's been floating around on twitter how alpha builds of CM9 have come out/been leaked for various devices (nexus s, evo 3d, etc.). Anyway you can use that? Just search CM9 on twitter and you will find it.

 

[isaacj87]

Hey Isaac,

it's been floating around on twitter how alpha builds of CM9 have come out/been leaked for various devices (nexus s, evo 3d, etc.). Anyway you can use that? Just search CM9 on twitter and you will find it.

No. I deal with source, not prebuilt ROMs. These builds are being built from source, but are of no use to me in their packaged form.

 

[isaacj87]

I forgot to mention... I got restless and decided to pull the ICS/CM9 source code. I managed to build it (it took about 4 hours to compile, but took me over 8 hours to get it to just build). Needless to say, the CM9 source is definitely not in a "ready" state.

In any case, I got it to build and it starts to boot, but gets stuck in a bootloop (the ICS boot animation is nice). Turns out, half the source didn't even compile. Like I said, the CM9 source isn't ready, yet.

I've pushed more experimental fixes to CM7 for HDMI. I don't actually have the CM7/GB source to test it myself. I think I might be getting closer to getting HDMI working in CM7.

I'm also cleaning up qcom_gps (merging AMSS 50001 protocol into CM's repos). This is probably the biggest thing that's different from the CM7 tree. If I can get this accepted upstream, there's a much better chance of the Triumph being accepted into the CM fold.

The touchscreen driver cleanup/re-write ended up being a success. It has been reported by others that touchscreen performance has improved. This fix is not ROM specific. It can be applied to any ROM.

 

[snail3]

I forgot to mention... I got restless and decided to pull the ICS/CM9 source code. I managed to build it (it took about 4 hours to compile, but took me over 8 hours to get it to just build). Needless to say, the CM9 source is definitely not in a "ready" state.

In any case, I got it to build and it starts to boot, but gets stuck in a bootloop (the ICS boot animation is nice). Turns out, half the source didn't even compile. Like I said, the CM9 source isn't ready, yet.

I've pushed more experimental fixes to CM7 for HDMI. I don't actually have the CM7/GB source to test it myself. I think I might be getting closer to getting HDMI working in CM7.

I'm also cleaning up qcom_gps (merging AMSS 50001 protocol into CM's repos). This is probably the biggest thing that's different from the CM7 tree. If I can get this accepted upstream, there's a much better chance of the Triumph being accepted into the CM fold.

The touchscreen driver cleanup/re-write ended up being a success. It has reported by others that touchscreen performance has improved. That fix is not ROM specific. It can be applied to any ROM.

looking forward for a working HDMI...I know people say it's not a "useful" feature, but it's a "nice to have" thing, especially when you can show other people on how capable this prepaid phone can do. Thanks so much for your effort isaac!

 

[marc12868]

The touchscreen driver cleanup/re-write ended up being a success. It has been reported by others that touchscreen performance has improved. This fix is not ROM specific. It can be applied to any ROM.

Can I download the driver and just install it on my phone or does it have to go through the rom?

 

[isaacj87]

Can I download the driver and just install it on my phone or does it have to go through the rom?

It has to be included in the kernel. Depending on your ROM, look for either Mantera or Austrie's third-party kernels. I believe both of them have added the fix to their respective kernels.

The next MIUI build will have it by default.

 

[Bobomo]

It has to be included in the kernel. Depending on your ROM, look for either Mantera or Austrie's third-party kernels. I believe both of them have added the fix to their respective kernels.

The next MIUI build will have it by default.

Any thoughts on whether it will get built into tickerguy's CM7 kernel now that he's halted development?

(Thanks for your hard work.)

 

[spdlmt150]

I promise not to beg for ics (although I'm quietly hoping to see it) and will say that cm7 has been the best thing to happen to this phone. Everything about it is a drastic improvement. What became the deal breaker for me is the hdmi. Netflix piped into the tv is the only entertainment I have. As good as the Triumph screen is, the 32 inch tv is better for watching movies. I've been hoping to see news of the hdmi becoming functional. I'm not a coder, & have limited experience. Just got adb going last night to play with the nook color. If there's any way to contribute to working hdmi output I'd do it without hesitation.
Thanks to all involved in these projects. Your time & effort is appreciated.

 

[haro138]

Hey really thanks for the work. I know that the HDMI was never a big issue to most but I am VERY excited about having it working.

Off Topic but my stupid PS3 got the YLOD and Ive been having to restore nandroid backups to watch netflix on my tv :/

 

[cdtatum08]

This phone is so much better than what it was when I originally bought it. danke!

 

[ziggy46]

Hey really thanks for the work. I know that the HDMI was never a big issue to most but I am VERY excited about having it working.

Off Topic but my stupid PS3 got the YLOD and Ive been having to restore nandroid backups to watch netflix on my tv :/

there is a fix for the YLOD on the ps3

 

[lifeblows10]

Once again you have outdone yourself Issac. I am hoping that this time around I can get MIUI working on my phone (for whatever reason every reboot ended in bootloop, but that was on my last Triumph. I'm on a new one now. )

 

[MotoTriu]

First of all I would like to start off by saying thank you for all your hard work and dedication you really make all of us Triumph users happy but out of curiousity do you know when The ics Rom would be stable enough for us to flash?

 

[b_randon14]

First of all I would like to start off by saying thank you for all your hard work and dedication you really make all of us Triumph users happy but out of curiousity do you know when The ics Rom would be stable enough for us to flash?

Probably quite some time. CM9 isn't even out for many supported devices yet so it will take some time to get a ROM working on this phone!! Patience my friend.

 

[agentc13]

I unstickied this because I think some people have been confused about the fact that it isn't actually an ICS ROM (not yet anyway). There are plenty of actual ROMs that are under current development that are not stickied. All of which are linked in the Root Guide sticky (as is this).

It is a pretty popular thread and will stay visible for quite a while. So don't worry.

I am excited to see how this will turn out and I know Isaac will do a wonderful job!

 

[Ayered]

I've pushed more experimental fixes to CM7 for HDMI. I don't actually have the CM7/GB source to test it myself. I think I might be getting closer to getting HDMI working in CM7.

I'm also very interested in HDMI output, so I really appreciate your all your efforts to get it working. Thanks for all your work on this and everything else you've done to bring CM goodness to the Triumph.

 

[idbl_fanatic]

So, I'm trying the new touchscreen driver changes (on MIUI) and I think the performance is much better. I won't say it's perfect, but it's much improved. Before, on Shadowgun, it was difficult to play because the touchscreen responded to every nuance. It was annoying as hell. Now, I find that Shadowgun is much more responsive when I'm running and gunning at the same time (something I couldn't really do before).

When I play shadowgun (CM7) everytime I exit out, it says "NO SERVICE" and there is an "X" by the antenna

Anyone know why this is?

 

[samhande]

I forgot to mention... I got restless and decided to pull the ICS/CM9 source code. I managed to build it (it took about 4 hours to compile, but took me over 8 hours to get it to just build). Needless to say, the CM9 source is definitely not in a "ready" state.

I've pushed more experimental fixes to CM7 for HDMI. I don't actually have the CM7/GB source to test it myself. I think I might be getting closer to getting HDMI working in CM7.

Your restlessness is our gain! Thanks Issac for putting out the effort. I agree with others that while the HDMI is not a deal breaker it sure make the MT all it can be. If this could be added to TG CM7, how cool would that be!

 

[PerkinsII]

I unstickied this because I think some people have been confused about the fact that it isn't actually an ICS ROM (not yet anyway). There are plenty of actual ROMs that are under current development that are not stickied. All of which are linked in the Root Guide sticky (as is this).

It is a pretty popular thread and will stay visible for quite a while. So don't worry.

I am excited to see how this will turn out and I know Isaac will do a wonderful job!

I agree there were to many stickies +1

 

[PerkinsII]

I forgot to mention... I got restless and decided to pull the ICS/CM9 source code. I managed to build it (it took about 4 hours to compile, but took me over 8 hours to get it to just build). Needless to say, the CM9 source is definitely not in a "ready" state.

In any case, I got it to build and it starts to boot, but gets stuck in a bootloop (the ICS boot animation is nice). Turns out, half the source didn't even compile. Like I said, the CM9 source isn't ready, yet.

I've pushed more experimental fixes to CM7 for HDMI. I don't actually have the CM7/GB source to test it myself. I think I might be getting closer to getting HDMI working in CM7.

I'm also cleaning up qcom_gps (merging AMSS 50001 protocol into CM's repos). This is probably the biggest thing that's different from the CM7 tree. If I can get this accepted upstream, there's a much better chance of the Triumph being accepted into the CM fold.

The touchscreen driver cleanup/re-write ended up being a success. It has been reported by others that touchscreen performance has improved. This fix is not ROM specific. It can be applied to any ROM.

I am looking forward to HDMI as it would be nice to watch movies on my tv without hooking up my laptop which is more annoying to do .

 

[ziggy46]

any furthur news on this project isaac? also, would you be able to give us something to play with? even if its completely broken... (please dont think im bugging you, i am just curious.)

 

[zachavm]

I LOVE this forum. It's small and isn't overrun like many, but still has very active devs. That means they will actually respond to your posts!!!!!

Issac, thanks again for your help!

General question to any who care. I've got MIUI 11-4 installed. If I want to update to the new one, do I have to reinstall everything or is there an update process.

 

[marc12868]

I LOVE this forum. It's small and isn't overrun like many, but still has very active devs. That means they will actually respond to your posts!!!!!

Issac, thanks again for your help!

General question to any who care. I've got MIUI 11-4 installed. If I want to update to the new one, do I have to reinstall everything or is there an update process.

you should just have to wipe your dalvik cache and flash the new zip, if its the same rom... like updating to a newer version of miui switching to a different rom you would have to do a factory reset to...

 

[iSnow]

sticky please!