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

Root [ROM] CM7 TG-Reloaded (Final: 03-25)

All of your contrabutions are apperciated. Those with CM7 & CM9, as well as your generosity and willingness to answer our questions. Even the dumber ones.;)
 
Is there a way to force EVDO and stay receiving phone calls?
My phone keeps switching from EVDO to 1xRTT while I use data... I set the phone to EVDO only but can no longer receive phone calls.
Thanks
 
Oh, and great Whyzor! Just when I decided to come back to CM7 from CM9 because I wanted my camera back! Nah...just kidding. I fully understand and don't blame you. I sincerely thank you for everything that you did for the Triumph & for all of us who have struggled with it. You have become a true hero in the eyes of many people here! Thank you again and I hope to see you on other threads helping others with which ever device you decide to get.
 
Chingling said:
So I just did a complete fresh install of your latest build, and still no dice. Cannot send or receive, even with a fresh install! There is also another user in California who has this same problem, but we can call fine. Is there a such thing as just an SMS outage?
Click to expand...

I had the same problem earlier. Couldn't send text and I wasn't receiving them either but I could make and receive calls. About an hour ago (7:30pm)I got a bunch of text that I should have gotten earlier. And people are calling me saying that they just got my text that I sent about 9 hours earlier. Seems like it was an outage and I'm all the way in NJ. I'm still receiving text now from earlier but I think it's fixed now anyway.
 
NOOoooooOOO!!!!!!

Who is the next smartest person on the list who can take this over? :-)

Thank you for all you have done. I love(d) to come to this forum to see what the next latest and greatest is to download to my phone.

Whyzor said:
I've decided to sell my Triumph and go back to the trusty old Optimus V until the next VM phone worth buying comes out (The HTC one V looks promising if the rumors are true). The MT's unreliable touchscreen gets on my nerve every time I use it and I can't stand it any longer.

I'll make a final build & test it on the phone before I part with it. It's been quite a learning experience for me the past few months, I'll stick with VM's $25/mo plan since nothing else can beat it for my type of usage. So maybe you'll see me on another VM phone forum.

BTW If anyone wants to buy my Triumph w/ everything that came in original box + an extra 1600 mAh battery (mint condition) + a soft & hard case, PM me. Looking to sell for $180 or more, first/highest offer will be accepted. Otherwise it'll go on ebay tonight. I'll update this post if it's been spoken for.
Click to expand...
 
Thanks for all your great work - although I only started using CM7 TG-Reloaded at February 18 build, I can see you've always been responsive and contributed a lot to development. I look forward to seeing you at whatever device's forum you next frequent. All the best.
 
Can't understand why a lot of talented developers are leaving. :(

Take care Whyzor and thank you for all ur hard work!
 
Unofficial - " Developer Retention Program" - Idea:

Whyzor, I just logged in today and saw that you've made up your mind to leave us....

I have used every version of your ROM and am very happy with my MT. and don't want to see you go -

I would like to see if everyone here might look at helping convince you to stay...

It seems that we have a problem that could be easily solved with every one's help:
You have a phone that you value at $180 today and wish to capture that value before it diminishes into the future.

I see it as simply a "present value" vs "future value" problem that if we can solve it - might persuade you to continue working on the MT?

So here is my proposed solution to mitigate that risk:

I propose that everyone who has benefited from Whyzor's Reloaded ROM and would like to see him continue his efforts, pledge to donate $5 or $10 to you now - If you will simply keep your MT (unactivated) and continue to occasionally update the CM7 code as it becomes available (as well as work on anything else you want to.) until a solid Beta of CM9 (with camera etc.) becomes available. If you needed to test the phone "live" - you could transfer your account back and forth from your OV phone.


<See the Donate button in the first post in this thread>


If we got just $100 that should more than make up for any lost value in the MT over the next few months - and you could then sell the MT once the Beta happens.

I for one would start the ball rolling with $10 if you would be in agreement? (Heck I'm gonna go do it now anyway for all the work you've already done!...)

So, Whyzor can we convince you?

Everyone else - Who would go in on this idea with me? Speak up now and let Whyzor know how you feel....:o
 
johnnyrocket said:
Unofficial - " Developer Retention Program" - Idea:

Whyzor, I just logged in today and saw that you've made up your mind to leave us....

I have used every version of your ROM and am very happy with my MT. and don't want to see you go -

I would like to see if everyone here might look at helping convince you to stay...

It seems that we have a problem that could be easily solved with every one's help:
You have a phone that you value at $180 today and wish to capture that value before it diminishes into the future.

I see it as simply a "present value" vs "future value" problem that if we can solve it - might persuade you to continue working on the MT?

So here is my proposed solution to mitigate that risk:

I propose that everyone who has benefited from Whyzor's Reloaded ROM and would like to see him continue his efforts, pledge to donate $5 or $10 to you now - If you will simply keep your MT (unactivated) and continue to occasionally update the CM7 code as it becomes available (as well as work on anything else you want to.) until a solid Beta of CM9 (with camera etc.) becomes available. If you needed to test the phone "live" - you could transfer your account back and forth from your OV phone.





If we got just $100 that should more than make up for any lost value in the MT over the next few months - and you could then sell the MT once the Beta happens.

I for one would start the ball rolling with $10 if you would be in agreement? (Heck I'm gonna go do it now anyway for all the work you've already done!...)

So, Whyzor can we convince you?

Everyone else - Who would go in on this idea with me? Speak up now and let Whyzor know how you feel....:o
Click to expand...

I'm in. i love your work whyzor it wont be the same without u
 
Whyzor said:
I've decided to sell my Triumph and go back to the trusty old Optimus V until the next VM phone worth buying comes out (The HTC one V looks promising if the rumors are true). The MT's unreliable touchscreen gets on my nerve every time I use it and I can't stand it any longer.

I'll make a final build & test it on the phone before I part with it. It's been quite a learning experience for me the past few months, I'll stick with VM's $25/mo plan since nothing else can beat it for my type of usage. So maybe you'll see me on another VM phone forum.

BTW If anyone wants to buy my Triumph w/ everything that came in original box + an extra 1600 mAh battery (mint condition) + a soft & hard case, PM me. Looking to sell for $180 or more, first/highest offer will be accepted. Otherwise it'll go on ebay tonight. I'll update this post if it's been spoken for.
Click to expand...

Sucks that you're leaving the MT, but I wish you the best.
 
I appreciate all the support. Another factor is the time and effort, since I have a full-time job as a software engineer, I don't want to spend my free time doing the same, life is too short to be in front of a screen all the time :) This was originally only supposed to be a small project for the holidays.

There are many capable people here, I'm sure MT's development will continue just as well. I'll wait until this weekend to try to grab all the CM7 changes upstream for a final build. Here are some of the fixes merged already:

- Fixed EXIF data writing for camera
- Fixed soft keyboard appearing on dialer sometimes
- Show PIN entry even if lockscreen is disabled
- Backported "disappearing SD media" fixes from CM9
- Fixed ext4 image generation when size is exact multiple of block size
 
Dang nab it. I just got Ubuntu installed tonight. And I have another 2GB of RAM coming so I could try to work on the EXIF bug. Oh well, glad to see it's been fixed (maybe). I did notice some other things that I may be able to contribute. I'll see later. Work and family has kept be busy lately. Again, thank you for what you have done. I know with the budding DEVs we have here, we can inch toward even greater things.
 
Completley Grateful for your work good job on everything you helped make a crappy phone very worth while! :) If The HTC V One came out for VM would you be back on the dev team by any chance? just wondering :)

Whyzor said:
I appreciate all the support. Another factor is the time and effort, since I have a full-time job as a software engineer, I don't want to spend my free time doing the same, life is too short to be in front of a screen all the time :) This was originally only supposed to be a small project for the holidays.

There are many capable people here, I'm sure MT's development will continue just as well. I'll wait until this weekend to try to grab all the CM7 changes upstream for a final build. Here are some of the fixes merged already:

- Fixed EXIF data writing for camera
- Fixed soft keyboard appearing on dialer sometimes
- Show PIN entry even if lockscreen is disabled
- Backported "disappearing SD media" fixes from CM9
- Fixed ext4 image generation when size is exact multiple of block size
Click to expand...
 
Just wanted to echo in what others have said, thanks for your work on CM7R Whyzor.

On another matter, I managed to get a logcat of one of the "random" reboots that started with the 03-04 build (using the CatLog app to record a log to the SD card every 5 lines).

If it helps any, these are the lines it recorded for the last couple of minutes:

03-21 05:32:46.414 I/dun_service( 155): process rmnet event
03-21 05:32:46.414 I/dun_service( 155): Post event 4
03-21 05:32:46.414 I/dun_service( 155): received event: DUN_EVENT_RMNET_UP
03-21 05:32:46.414 I/dun_service( 155): received event(DUN_EVENT_RMNET_UP) in state(DUN_STATE_USB_UNPLUG)
03-21 05:32:46.414 I/dun_service( 155): Ignoring the event DUN_EVENT_RMNET_UP in USB_UNPLUG_STATE
03-21 05:32:46.414 I/dun_service( 155): Moved to state(DUN_STATE_USB_UNPLUG)
03-21 05:32:46.414 I/dun_service( 155): process rmnet event
03-21 05:32:46.414 I/dun_service( 155): Post event 4
03-21 05:32:46.414 I/dun_service( 155): process rmnet event
03-21 05:32:46.414 I/dun_service( 155): Post event 4
03-21 05:32:46.414 I/dun_service( 155): received event: DUN_EVENT_RMNET_UP
03-21 05:32:46.414 I/dun_service( 155): received event(DUN_EVENT_RMNET_UP) in state(DUN_STATE_USB_UNPLUG)
03-21 05:32:46.414 I/dun_service( 155): Ignoring the event DUN_EVENT_RMNET_UP in USB_UNPLUG_STATE
03-21 05:32:46.414 I/dun_service( 155): Moved to state(DUN_STATE_USB_UNPLUG)
03-21 05:32:46.414 I/dun_service( 155): received event: DUN_EVENT_RMNET_UP
03-21 05:32:46.414 I/dun_service( 155): received event(DUN_EVENT_RMNET_UP) in state(DUN_STATE_USB_UNPLUG)
03-21 05:32:46.414 I/dun_service( 155): Ignoring the event DUN_EVENT_RMNET_UP in USB_UNPLUG_STATE
03-21 05:32:46.414 I/dun_service( 155): Moved to state(DUN_STATE_USB_UNPLUG)
03-21 05:32:46.464 I/TelephonyRegistry( 239): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=apnSwitched interfaceName=rmnet0 networkType=6
03-21 05:32:46.534 W/NetworkStateTracker( 239): net.tcp.buffersize.evdo not found in system properties. Using defaults
03-21 05:32:46.584 D/NetUtils( 239): failed to add 28.209.210.193 as default route for rmnet0: File exists
03-21 05:32:46.604 D/Tethering( 239): MasterInitialState.processMessage what=3
03-21 05:32:46.614 I/TaskReceiver( 546): action = android.net.conn.CONNECTIVITY_CHANGE
03-21 05:32:46.614 D/GTalkService( 438): ##### Network broadcast (connected=true) type=mobile, state=CONNECTED
03-21 05:32:46.644 D/GTalkService( 438): [GTalkConnection.1] setInternalNetworkState: type=0, state=CONNECTED
03-21 05:32:46.674 I/MediaUploader(11165): No need to wake up
03-21 05:32:46.916 D/CMStats (11176): CONNECTIVITY_ACTION: noConnectivity = false
03-21 05:32:47.004 D/Beautiful Widgets(10699): CONNECTIVITY_CHANGE
03-21 05:32:47.454 I/AmazonAppstore.UpdateCommands( 1778): Self-updating enabled: true
03-21 05:32:47.454 D/AmazonAppstore.UpdateCommands( 1778): Adding self-update command to UpdateService
03-21 05:32:47.464 V/AmazonAppstore.UpdateService( 1778): onCreate
03-21 05:32:47.464 V/AmazonAppstore.DiskInspectorServiceImpl( 1778): Available blocks: 212867, Block size: 4096, Free: 871903232, Threshold: 5242880, withinThreshold? true
03-21 05:32:47.464 V/AmazonAppstore.ReferenceCounter( 1778): Reopening reference (UpdateService).
03-21 05:32:47.474 V/AmazonAppstore.DiskInspectorServiceImpl( 1778): Available blocks: 212867, Block size: 4096, Free: 871903232, Threshold: 5242880, withinThreshold? true
03-21 05:32:47.474 D/AmazonAppstore.UpdateService( 1778): Received action: com.amazon.mas.client.framework.UpdateService.CONN_CHANGED from intent: Intent { act=com.amazon.mas.client.framework.UpdateService.CONN_CHANGED cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService (has extras) }
03-21 05:32:47.494 V/AmazonAppstore.ReferenceCounter( 1778): Reference (UpdateService) count has gone to 0. Closing referenced object.
03-21 05:32:47.494 V/AmazonAppstore.UpdateService( 1778): All UpdateService refs released. Calling stopSelf.
03-21 05:32:47.494 V/AmazonAppstore.UpdateService( 1778): onDestroy
03-21 05:32:49.786 I/JuiceDefender.Service( 1439): Connected: mobile
03-21 05:32:50.324 I/JuiceDefender.Service( 1439): Data disabled
03-21 05:32:50.585 W/JuiceDefender.Service( 1439): Throttling data toggle
03-21 05:32:50.736 I/dun_service( 155): process rmnet event
03-21 05:32:50.736 I/dun_service( 155): Post event 3
03-21 05:32:50.736 I/dun_service( 155): received event: DUN_EVENT_RMNET_DOWN
03-21 05:32:50.736 I/dun_service( 155): received event(DUN_EVENT_RMNET_DOWN) in state(DUN_STATE_USB_UNPLUG)
03-21 05:32:50.736 I/dun_service( 155): Ignoring the event DUN_EVENT_RMNET_DOWN in USB_UNPLUG_STATE
03-21 05:32:50.736 I/dun_service( 155): Moved to state(DUN_STATE_USB_UNPLUG)
03-21 05:32:50.884 I/TelephonyRegistry( 239): notifyDataConnection: state=0 isDataConnectivityPossible=true reason=dataDisabled interfaceName=rmnet0 networkType=6
03-21 05:32:50.974 D/NetUtils( 239): failed to remove default route for rmnet0: No such process
03-21 05:32:51.010 D/Tethering( 239): MasterInitialState.processMessage what=3
03-21 05:32:51.014 I/TaskReceiver( 546): action = android.net.conn.CONNECTIVITY_CHANGE
03-21 05:32:51.044 W/Smack/Packet( 438): notify conn break (IOEx), close connection
03-21 05:32:51.044 I/MediaUploader(11165): No need to wake up
03-21 05:32:51.064 D/GTalkService( 438): ##### Network broadcast (connected=false) type=mobile, state=DISCONNECTED
03-21 05:32:51.064 D/GTalkService( 438): [GTalkConnection.1] setInternalNetworkState: type=0, state=DISCONNECTED
03-21 05:32:51.064 D/GTalkService( 438): [GTalkConnection.23] connectionClosed: connId=351484, error=NO NETWORK
03-21 05:32:51.084 D/Smack ( 438): [XMPPConn] close connection, notifyClosed=false
03-21 05:32:51.174 D/CMStats (11176): CONNECTIVITY_ACTION: noConnectivity = true
03-21 05:32:51.238 D/Beautiful Widgets(10699): CONNECTIVITY_CHANGE
03-21 05:32:52.228 I/JuiceDefender.Service( 1439): Data disabled
03-21 05:32:54.144 I/JuiceDefender.Service( 1439): Disconnected
03-21 05:33:14.754 D/GTalkService( 438): [GTalkConnection.1] connect: network unavailable, set state=PENDING, err=NO_NETWORK
03-21 05:33:37.414 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:37.707 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:37.735 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:37.735 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:37.735 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:38.214 I/WifiHW ( 239): Lock released
03-21 05:33:38.214 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:38.214 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:38.464 D/Beautiful Widgets(10699): WIFI_STATE_CHANGED_ACTION
03-21 05:33:38.514 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:33:42.644 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:34:58.524 I/dun_service( 155): The value returned from dun_getusbmodemstate_fromsys is 2
03-21 05:35:00.504 D/Email (10950): *** synchronizeMailboxGeneric ***
Click to expand...
Again, not sure what help it is but perhaps there is something useful in there that I'm not seeing.
 
Whyzor said:
Actually not as much as I thought, my Optimus V can be overclocked to 864 and since I don't do a lot of 3D gaming, the Triumph's higher specs doesn't apply to me. Only thing I do miss is the bigger screen, but I also like the smaller rounded shape of the OV.
Click to expand...

Whats the development like for the V? Is it about on par with the Triumph? Worse? Better? Do you think ICS will ever be fully functional on it?
 
I've found that OV dev work is very good, jerryscript really knows his stuff.

I'm hoping for better battery performance when using WiFi out of Whyzor's final build :D
 
Why, Whyzor, Why?

Anyway... thanks for your hard work on the Triumph. Whatever phone you end up with the forums for it will be lucky to have you!
 
Nocturnal86 said:
Completley Grateful for your work good job on everything you helped make a crappy phone very worth while! :) If The HTC V One came out for VM would you be back on the dev team by any chance? just wondering :)
Click to expand...

Possibly, I'll make small contributions, but hopefully the HTC One V won't need as much work.

Gaffadin said:
On another matter, I managed to get a logcat of one of the "random" reboots that started with the 03-04 build (using the CatLog app to record a log to the SD card every 5 lines).

If it helps any, these are the lines it recorded for the last couple of minutes:

Again, not sure what help it is but perhaps there is something useful in there that I'm not seeing.
Click to expand...

Logcat captures app level logs in a FIFO (first-in first-out) buffer. So should just grab everything instead of every 5 lines, the critical lines may be part of the 5 that got skipped. 'dmesg' grabs kernel-level logs, which may have clues to a crash too. I couldn't see anything in what was posted suggesting anything wrong, but you could try uninstall juice defender for a few days to see if it improves, don't overclock or undervolt if that's enabled. Also try uninstalling amazon appstore, beautiful widgets, smack? to try to narrow down what's causing the problem, then after finding it, you can decide whether it's worth keeping. I've never used any of those.

garrmack said:
Whats the development like for the V? Is it about on par with the Triumph? Worse? Better? Do you think ICS will ever be fully functional on it?
Click to expand...

The Optimus V is what I had before the MT and it has a good dev community still going. Jerryscript helps a lot of users, blarf is the main guy who inspired me to dabble in dev work (they're more active on xda-dev & androidcentral along with others). I think they're all ready for a new phone, but it has to be worth the upgrade, so that'll depend on what VM releases next. If we all unite behind one device it would be bliss :)
 
Whyzor, really enjoyed your contribution to the Triumph. I also enjoyed your willingness to respond to the communities questions. Enjoy your new free time!
 
You must log in or register to reply here.
Back
Top Bottom