[10-11-11][ROM] gingerbread-evo-deck [1.3][2.3.7 Stable] #Stablistic

[BrooMann]

Originally Posted by teejay89

Happened to me as well. All data and everything came in fine, but it didn't restore my apps. Not that I care that much- it took maybe 5 minutes to get everything up and running again

Also...when I restore wit Titanium Backup...the apps don't show up in Market. But if I search 4 a specific app it shows up as installed. Weird! The 2 "car home's" aren't installed either I noticed. Whatever they r...maybe 4 navigation?

Sent from my Gingerbreaded HTC EVO 4G runnin Deck's 1.1 rom.

[fgcchevy]

Found the link to this thread over on xda. I must say, i like the rom, it is fast and running smooth on my evo. The google video chat worked perfectly over 3g. I do have one question, how exactly does the custom user agent work? I sent a pic and a regular text and the recipient does not show the user agent i selected. TIA

[amw1972]

I do believe that when upgrading android versions its best to do a full wipe.

On 1.0...and have played with tiamat 3.3.7, 3.3.8 and, 4.0.0 3.3.7 has been the most stable and batt friendly.

will be upgrading to 1.1 and flashing to 3.3.7 later...will report back with results.

Sent from my PC36100 using Tapatalk

[XsMagical]

Originally Posted by BrooMann

Also...when I restore wit Titanium Backup...the apps don't show up in Market. But if I search 4 a specific app it shows up as installed. Weird! The 2 "car home's" aren't installed either I noticed. Whatever they r...maybe 4 navigation?

Sent from my PC36100 using Tapatalk

If you have the older gapps for evo deck 1.0 you can pull if from there and push it to /SYSTEM/APP/.

http://download.neweragfx.com/Mobile...30-newtalk.zip

[satur9]

Originally Posted by JADC

Has anyone noticed that with Launcher PRO unlocking the screen (power button) its not very responsive? Is it possible to change the unlock screen button to Volume up or down? To be clear im not talking about the unlock slider, but the unlock button to bring out of standby mode. Thanks

I have had the same problem on pre5_1.0 & also on CM7 (using ADW, not LP). I thought it may have been b/c I turn the lock screen off, but it was not a problem for me on UltimateDroid 3.3.1.

Have yet to try 1.0 or 1.1.

[Brock1909]

everything is great for me except i cant send MMSs (maybe not receive either). it just stays on sending and never goes through, fresh install from 1.0. anyone else have this problem?

[forty01]

Originally Posted by BrooMann

Also...when I restore wit Titanium Backup...the apps don't show up in Market. But if I search 4 a specific app it shows up as installed. Weird! The 2 "car home's" aren't installed either I noticed. Whatever they r...maybe 4 navigation?

Sent from my PC36100 using Tapatalk

Car Home was not in the latest GAPP, so if it's something you want, then I would advise sticking it in the new GAPP or just installing it separately. Either way should work fine.

[The Viz]

Looks like Tiamat 4.0 might be breaking the camera. I hadnt noticed until I tried taking a picture. So I reflashed 1.0 and flashed 4.0 Tiamat and the cam still didnt work. I reflashed 1.1 with Tiamat 3.3.8 and the cam works.

[Vegasden]

Originally Posted by Brock1909

everything is great for me except i cant send MMSs (maybe not receive either). it just stays on sending and never goes through, fresh install from 1.0. anyone else have this problem?

As with the "stock" CM, I can confirm that MMS is not working. I could not receive one this afternoon.

EDIT: toastcfh is aware Connectivity issues with 2.3.4

[mattsm]

Originally Posted by Brock1909

everything is great for me except i cant send MMSs (maybe not receive either). it just stays on sending and never goes through, fresh install from 1.0. anyone else have this problem?

Yes and the only thing that solved it for me was a full wipe. This was the only problem I had, sending mms same as you described.
Receiving mms would work fine as well as everything else in rom.

Edit: Did full wipe before flash of rom, had the problem. Did a full wipe again and then rebooted, problem was solved.