-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][Beta][FINAL] CM7 Android For Triumph [Tickerguy Edition, Kernel: mine] 11/19
- Thread starter tickerguy
- Start date
-
- Tags
- motorola triumph
If TG does leave then you are the next candidate. You two have many fans and dedicated modders that will follow you. We may give you a hard time at times but we are always willing to help. Plus this rom isn't 100% stable and is not in the rom manager download section yet. We are proud of you guys for all the work and patience two have put into this rom. Thank you.
Upvote
0
Help with battery life...I have two motorola triumph running the newest cm7 from TG. They both are running juice defenders and smartass. One of the phone last the whole day with a full charge with moderate use. The other last about 4-5 hours with hardly any use...it drains battery like crazy MF. I have wiped the phone clean and cleared all cache...still no luck. Any idea what else I can try? TIA
Upvote
0
Upvote
0
I couldn't agree more. I have tried many ROMs over the past few years and I have to say this work has been phenomenal. Very thorough yet quickly evolving especially considering the problems the Triumph was shipped with right out of the box. I haven't seen anything like it. This is what I love about Android and its community/forums. Very resourceful and resilient. I think it's safe to speak for everyone by saying we are thankful for ALL developers, and are personally grateful for developers like Tickerguy and Isaac. The users and developers behind Android is what makes it such an awesome OS.
Though the possibility of TG leaving us is unfortunate, I am confident enough in the community to think that someone will come along and pick up the awesome work left behind... and as many have said.. I vote for Isaac!! We need to set up a PayPal link so we can all buy him a kegger ;-P
Upvote
0
The decision isn't made yet; if I DO leave I will endeavor to make sure my Git repos are all up to date and build from scratch (I WILL pull it down; I'm resizing my VM for Linux right now which is a many-hour process as I ran out of space trying to fix the Vibrant source for CM7.) The decision will be made this upcoming Friday one way or another and I'll post here when it is. Once I port out my number will die and so will my ability to test, so that's kind of the "zero hour."
The only way I could justify keeping the Triumph rather than selling it is if I was receive donations sufficient to both pay for what I'd get out of it (probably $200 more or less) and enough on a continuing basis to keep a minimum-level Virgin account running (~$35 a month now.)
That's darn unlikely when all is said and done, but it's the only way it makes sense as I'm not going to do development on a device I can't test against personally. The CM7 folks tried to do that with the Vibrant and got excoriated over on XDA for what appears to be a one-line miss in their code - entirely unreasonable on the part of the users but also entirely expected without someone having one of the devices to test against!
I ain't going there.
In any event the codebase as it stands has the following things that need to happen to get the CM7 people interested in picking it up officially:
1. The Triumph RIL changes need to be stuck in their own file (like the Samsung RIL driver) and the phonefactory code changed to call the right one. That's pretty simple; a couple hours of work.
2. Ditto on the MMS changes picked up from inferiorhumanorgans although it's possible those can be slipstreamed into the base code and not screw anything else up. I don't know if that's true or false, but it's possible. If it's true then it should be merged into the base, but if not, it needs the same treatment as the RIL.
3. The camera code changes (libcamera and the APK itself) need to be either cased for the build or otherwise moved.
4. The big one: The AMSS 50001 GPS stuff has to be merged. That's a pain in the ass. It's not hard, but it's a royal pain.
5. There are a few similar and minor changes in the hardware driver section for the sound interface (the headset controls.)
Finally, there's an issue of the Cherry drivers and other stuff in the prop directory. You can't commit that back so anyone building has to find the originals (on XDA and elsewhere) and grab the necessary bits to be included, just like you do from the phone for the Froyo pieces. Sucks, but is what it is.
Frankly, I'd not do any of it, and simply maintain against the manifest I'm using instead, merging as required, especially since it appears CM7 will be going to maintenance-only once ICS drops. As such keeping it up to date shouldn't be very hard.
The only way I could justify keeping the Triumph rather than selling it is if I was receive donations sufficient to both pay for what I'd get out of it (probably $200 more or less) and enough on a continuing basis to keep a minimum-level Virgin account running (~$35 a month now.)
That's darn unlikely when all is said and done, but it's the only way it makes sense as I'm not going to do development on a device I can't test against personally. The CM7 folks tried to do that with the Vibrant and got excoriated over on XDA for what appears to be a one-line miss in their code - entirely unreasonable on the part of the users but also entirely expected without someone having one of the devices to test against!
I ain't going there.
In any event the codebase as it stands has the following things that need to happen to get the CM7 people interested in picking it up officially:
1. The Triumph RIL changes need to be stuck in their own file (like the Samsung RIL driver) and the phonefactory code changed to call the right one. That's pretty simple; a couple hours of work.
2. Ditto on the MMS changes picked up from inferiorhumanorgans although it's possible those can be slipstreamed into the base code and not screw anything else up. I don't know if that's true or false, but it's possible. If it's true then it should be merged into the base, but if not, it needs the same treatment as the RIL.
3. The camera code changes (libcamera and the APK itself) need to be either cased for the build or otherwise moved.
4. The big one: The AMSS 50001 GPS stuff has to be merged. That's a pain in the ass. It's not hard, but it's a royal pain.
5. There are a few similar and minor changes in the hardware driver section for the sound interface (the headset controls.)
Finally, there's an issue of the Cherry drivers and other stuff in the prop directory. You can't commit that back so anyone building has to find the originals (on XDA and elsewhere) and grab the necessary bits to be included, just like you do from the phone for the Froyo pieces. Sucks, but is what it is.
Frankly, I'd not do any of it, and simply maintain against the manifest I'm using instead, merging as required, especially since it appears CM7 will be going to maintenance-only once ICS drops. As such keeping it up to date shouldn't be very hard.
Upvote
0
Err I've got another option, although it might be a little annoying it's better then no work at all. You could possibly get 2-3 people to volunteer to do testing for you either by video chatting on skype or google voice or something. that way if they run into an error they can mention it before you release one to the general public. I'd get if that just sounded too annoying to be workable however.
Upvote
0
Hi: Try swapping out the batteries to the other phone to see if one battery is bad. You may also need to calibrate the battery meter in one of the phones. If the batteries are both good then check and see if there is an app that is not on both phones to see if an app is running your battery down.
Upvote
0
First off thanks for all the work you've done! I couldn't have done it and its made my phone much better and a lot more fun!. Now to the stupid questions: Whats the likely-hood that someone is going to take over development IF you leave? from a noobs uninformed view at face value there doesn't appear that much NEEDS doing except perhaps working on the GPS lock problem...do you think the remaining slowness (which is much better than stock) is from Motos code or just bad hardware? is this something that will be in the next build IF there is one?
Upvote
0
Unless we get a new radio load there's nothing realistic to do with the GPS. It is what it is.
The remaining issue that really matters is the HDMI output and the Wifi/Bluetooth spinlock problem (the latter appears to be an interrupt storm and those are a real bitch to find in any event - if it's coming from the libra.ko driver, and I think it is, it may be flatly impossible without source.)
There may be a way to hack on the Cherry libra.ko driver and get it to load. That's not going to be easy though.
The remaining issue that really matters is the HDMI output and the Wifi/Bluetooth spinlock problem (the latter appears to be an interrupt storm and those are a real bitch to find in any event - if it's coming from the libra.ko driver, and I think it is, it may be flatly impossible without source.)
There may be a way to hack on the Cherry libra.ko driver and get it to load. That's not going to be easy though.
Upvote
0
Probably not by next Friday - I don't know why it doesn't work, and while I have put some effort into it I'm also not sure where the codepath is that is being taken to define those soft keys.
I suspect it's a missing flag somewhere (easy fix if I find it) but my search for that has come up empty thus far.
I suspect it's a missing flag somewhere (easy fix if I find it) but my search for that has come up empty thus far.
Upvote
0
TickerGuy, Why are you leaving (or considering leaving) Virgin Mobile?
To all: I saw that there is a new wireless company which starts on the 8th, called Republic Wireless, I believe. They will have unlimited everything for...GET THIS: $19/month...
Anyway, just curious if that is why you are leaving, TG.
To all: I saw that there is a new wireless company which starts on the 8th, called Republic Wireless, I believe. They will have unlimited everything for...GET THIS: $19/month...
Anyway, just curious if that is why you are leaving, TG.
Upvote
0
I for one, would like to see this kept going by you TG. you and Isaac have done some amazing work with this phone. I wish I could give you the $200 so you would keep the phone. I can't do that, but if enough people will pitch in for that, I would be more than happy to pay the $35 month to keep it in service so that you can test it. I understand that if it's not your primary phone, the updates might be a little slower, but your work has been amazing. if you get the donations for the $200, pm me and I'll work out the details for paying you're monthly payment
Upvote
0
How do you calibrate the battery meter? I tried swapping the battery this evening...no luck. The phone that was having the problem, still has it. So is not the battery. I am going to calibrate the battery but don't know how. If that doesn't work, will have to delete all apps and try loading one by one
Upvote
0
How do you calibrate the battery meter? I tried swapping the battery this evening...no luck. The phone that was having the problem, still has it. So is not the battery. I am going to calibrate the battery but don't know how. If that doesn't work, will have to delete all apps and try loading one by one
Wipe the battery stats,let your phone die.
Then charge it fully, phone goes into trickle charge after 90%.
So keep it plugged in overnight.
Upvote
0
I found out something interesting about WIFI sleep policies. Turn out, WIFI sleep policies are being followed in CM7. The reason the WIFI doesn't immediately turn off when you lock the phone is because there's a 15 minute delay. To clarify, if the device has an active connection (i.e. there is an IP address read), then WIFI service won't deactivate the connection until after 15 minutes.
I can change this, but I think it's probably this way for a reason. The comments in the source code indicate this behavior is due to avoiding a race condition. Personally, I'd like it if the WIFI driver unloaded immediately after the screen goes off (like one would assume the sleep policy would do), but at least I know it's working now.
I can change this, but I think it's probably this way for a reason. The comments in the source code indicate this behavior is due to avoiding a race condition. Personally, I'd like it if the WIFI driver unloaded immediately after the screen goes off (like one would assume the sleep policy would do), but at least I know it's working now.
Upvote
0
ive got about the same battery life but it might be the reception of the school sites i go to. Ive got juice defender ultimate and y5 battery saver. What else can i do to improve my battery life? I plug my phone in to charge every night. It occasinally turns off when i cant find a charger in time though so i constantly "exercise" the battery i guess you could say. What can i do with SetCPU? Whats a good min mhz? I suppose i can setup profiles for setcpu to help with battery life too right?
Upvote
0
I think we need some clarification on this - I was always taught that you charge the phone to it's maximium level (FULLY charged, see TG's earlier posts about watching the charging current), then wipe battery stats in CWM (or delete batterystats.bin), then unplug the phone and use it as normal until it's totally dead, and finally charge it back up fully again.
I've actually been having a problem with my Triumph where the phone always goes dead when the meter reads around 7 to 10 percent. I've not been able to solve it yet and I've tried the above three times now. All of this since 10/26 (or whatever the build right before 10/30). I honestly don't think it's a problem with CM7 but with the battery calibration. Next time I'm going to try and manually delete the batterystats.bin just in case the 'Wipe battery stats' option in CWM isn't actually doing anything.
Aside from the above I've had a stellar experience with 10/30. With juice defender and my usual careful usage of wifi and data it's not at all unusual to see 24+ hours out of the phone when it's used lightly. Heavier usage (lots of web browsing, facebook, and camera) and I still see at least 15 hours. It's been awhile since I ran the phone on the stock Froyo but I wouldn't be surprised if that's double the battery life of Froyo. You just gotta love it....
With CM7 the Triumph is one of the most well behaved and responsive Android experiences I've seen short of some of the new fancy dual core tablets. And now with the WiFi sleep bug fixed it's past the point where I would now feel comfortable getting this phone for a member of my family and throwing TG's CM7 on it without having to worry about issues.
It never ceases to amaze me what determined people will come up with that either significantly increases the utility of an Android handset or downright decimates the stock experience in favor of something better. We saw it happen to a degree with the Samsung Intercept (ugh!), then the Optimus V, and now the Triumph in only a few short months. If TickerGuy DOES leave for T-Mo we will have definitely lost a powerful force in the scene for the Triumph, and this is in a scene that really has very few solid knowledgeable contributors. I will be very sad to see him go but I am also thankful he got so much done. Hopefully Issac or someone else can take up where he left off!
Upvote
0
Doesn't MIUI suffer from the same problems since it's based on the same code? I could have sworn it did back when I tried it... if not that's pretty awesome!
Upvote
0
Ticker is considering leaving for TMobile's new $30 plan which is 100 voice minutes and 5GB 4G capable data. Since T-mo's network is GSM you can pretty much use any unlocked GSM phone you want with this plan... so any number of countless high end Android handsets, iPhones, etc. It's pretty sweet.... I just hope it doesn't go to crap when the Death Star (AT&T) finally get to buy the company mid 2012.
Republic Wireless will be CDMA phones on the Sprint network (same network as Virgin Mobile). The phones will run specially modified versions of Android so that whenever the handset has a WiFi connection they will use it for voice calls instead of the CDMA network. So you can think of them as sort of hybrid VOIP phones. We will know for sure in a few days but I can imagine that at $19 these handsets will be locked down tight and probably pretty low end. I'd love to be proven wrong though...
Hell, maybe they will push VM to lower it's cheapie plan back to $25 instead of $35!
Upvote
0
Ticker is considering leaving for TMobile's new $30 plan which is 100 voice minutes and 5GB 4G capable data. Since T-mo's network is GSM you can pretty much use any unlocked GSM phone you want with this plan... so any number of countless high end Android handsets, iPhones, etc. It's pretty sweet.... I just hope it doesn't go to crap when the Death Star (AT&T) finally get to buy the company mid 2012.
Republic Wireless will be CDMA phones on the Sprint network (same network as Virgin Mobile). The phones will run specially modified versions of Android so that whenever the handset has a WiFi connection they will use it for voice calls instead of the CDMA network. So you can think of them as sort of hybrid VOIP phones. We will know for sure in a few days but I can imagine that at $19 these handsets will be locked down tight and probably pretty low end. I'd love to be proven wrong though...
Hell, maybe they will push VM to lower it's cheapie plan back to $25 instead of $35!
I expect the same from Republic Wireless, however, I'd rather save money than have features. The main thing I need is calling capabilities. I'm trying to pay off my student loans by the end of next year, so every little bit helps.
That T-Mo deal sounds good if it suits your needs, but I must have unlimited minutes for my business (and I don't have a land line).
That would be awesome if VM brought the $25 plan backs, several people in my family are on that.
Upvote
0
BEST TECH IN 2023
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.
Smartphones
Best Android Phones
See All- Google Pixel 8 Pro Check Price
- Samsung Galaxy S23 Ultra Check Price
- Samsung Galaxy Z Fold5 Check Price
- Google Pixel 8 Check Price
- Samsung Galaxy S23 Check Price
Upcoming
See All
Best iPhones
See All- Apple iPhone 15 Pro Max Check Price
- Apple iPhone 15 Pro Check Price
- Apple iPhone 15 Plus Check Price
- Apple iPhone 15 Check Price
- Apple iPhone SE (2022) Check Price
Upcoming
See AllTablets
Best Tablets
See All- Samsung Galaxy Tab S9 Ultra Check Price
- Apple iPad Pro (2022) Check Price
- Apple iPad Air (2022) Check Price
- Apple iPad Mini (2021) Check Price
- Microsoft Surface Pro 9 Check Price
Upcoming
See AllLaptops
Best Laptops
See All- Apple Macbook Pro Check Price
- Apple Macbook Air (2023) Check Price
- Dell XPS 13 Check Price
- Acer Chromebook Spin 714 Check Price
- Dell Alienware m18 (2022) Check Price
Upcoming
See AllTelevisions
Best TVs
See All- Samsung The Frame TV Check Price
- Samsung Neo QLED 4K QN90C Check Price
- LG G3 OLED Check Price
- LG A2 OLED Check Price
- ROKU Plus Series Check Price
- Samsung S90C OLED Check Price
- SunBriteTV Veranda 3 Check Price
Upcoming
See AllGame Consoles
Best Game Consoles
See All- Nintendo Switch OLED Check Price
- Microsoft XBOX Series X Check Price
- Sony Playstation 5 Check Price
- Microsoft XBOX Series S Check Price
- Nintendo Switch Lite Check Price
Upcoming
See AllWearables
Best Wearables
See All- Oura Ring 3 Check Price
- Apple Watch Series 9 Check Price
- Google Pixel Watch 2 Check Price
- Samsung Galaxy Watch 6 Classic Check Price
- Fitbit Inspire 3 Check Price
- Amazfit Amazfit Band 7 Check Price
- Apple Watch SE Check Price
- Apple Watch Ultra 2 Check Price
Upcoming
See All
Similar threads
