[ROM] [02/21/10] Juicy R10 (21892.5.0.89) [Sense UI 2.5.2012] [XDA UC]

[1999TL]

Originally Posted by 1999TL

Boo. kind of disheartening.

I flashed the rom to see if Juicy added roaming options under network service. We'd have Auto A, Auto-B, roaming only for the touch pro. Has anybody gotten these options in the network service?

Nobody seems to answer this question on Mighty's and Juicy's post.

Also, Is there a cab out there that will use Outlook messaging by default and allow you to go to the outlook messaging when you click a favorite contact?

[hotspace]

Damn...I love the twitter tab. I gotta have my twitter. Whats the lesser of two evils?? I guess I could stop being lazy and learn how to cook...But that's labor intensive...OOps, there's my laziness again. LOL

[darren.wlsn1]

Originally Posted by hotspace

Damn...I love the twitter tab. I gotta have my twitter. Whats the lesser of two evils?? I guess I could stop being lazy and learn how to cook...But that's labor intensive...OOps, there's my laziness again. LOL

funny thing is, my twitter tab worked fine, not mms ,youtube or footprints. lol

[cflynt]

Alrighty folks, seriously there is no need to continue tell us that this rom is a deal breaker for you cuz of whatever not working for you. I am sorry if things don't work 100% for you, keep in mind this is TF2.5 which was in no way made for the TP2. I would highly consider it very ALPHA. So if you want something more stable, something that everything works 100% for you, then definitely go back to 2.1 and stop telling us what a deal breaker this is for you. If you aren't willing to make some changes to workaround things till someday they hopefully get ported properly, then you really need to stick with stuff that works out of the box.

Again, I am sorry things don't work for you. But it just gets real old hearing you guys complain about the same things over and over, when it is a known fact that it is in testing.

Good luck, and hopefully 2.5 will be ported more in the future and you can try again.

[slopokdave]

Originally Posted by darren.wlsn1

page 256 "worked" for me. its not now though but it was a hour ago but.... im done making 15 moves just to send a picture. sense 2.1 here i come. works outa the box.

Two cabs, thats all it takes........... no reg edits............... nothing....... the "I'm leaving your ROM" crap has to stop, it's going to make me bonkers. lol.

Originally Posted by cflynt

Alrighty folks, seriously there is no need to continue tell us that this rom is a deal breaker for you cuz of whatever not working for you. I am sorry if things don't work 100% for you, keep in mind this is TF2.5 which was in no way made for the TP2. I would highly consider it very ALPHA. So if you want something more stable, something that everything works 100% for you, then definitely go back to 2.1 and stop telling us what a deal breaker this is for you. If you aren't willing to make some changes to workaround things till someday they hopefully get ported properly, then you really need to stick with stuff that works out of the box.

Again, I am sorry things don't work for you. But it just gets real old hearing you guys complain about the same things over and over, when it is a known fact that it is in testing.

Good luck, and hopefully 2.5 will be ported more in the future and you can try again.

Haleiejehaahhajauahha!

[cflynt]

Originally Posted by slopokdave

Two cabs, thats all it takes........... no reg edits............... nothing....... the "I'm leaving your ROM" crap has to stop, it's going to make me bonkers. lol.



Haleiejehaahhajauahha!

I think what he refers to is after getting it working the workarounds of having to goto the inbox, swipe and click new etc. Instead of being able to do it natively. I understand this, but it is something I am willing to live with for all the other great features of 2.5. Of course, it is much easier going into Album to send a picture or doing it right after you take the picture. But again, think he refers to receiving them as well.

[amw1972]

@darren...here you go again!!!

@those that's having such tremendous issues...stop moaning and complaining...instead...help contribute to the solution. Remember stock ROM is just a flash away.

@those that are looking down at those that don't have everything working...help them instead of admonishing them...we're a community that's supposed to help each other to get the most out of a device right?=D>

@juicy: great ROM....little disappointed that I can't customize as freely as I used to...but I'll get over it. Speed and stability trumps all!!

[8notime]

It would be nice if Post #6 was replaced with a FAQ.

[jmorton10]

Originally Posted by cflynt

I think what he refers to is after getting it working the workarounds of having to goto the inbox, swipe and click new etc. Instead of being able to do it natively. .

yea, that & the slow laggy texting really suck.

I'm torn myself, those problems bug the hell out of me too -but I like everything else about this ROM so much that I really can't see going back to Mighty at this point......

~John

[ChrisCicc]

Originally Posted by jmorton10

Do you actually have MMS pictures opening up full screen right from within the HTC app??

If so, how did you do that??

~John

Yes, see my post here for screen shots. Receiving in Manila 2.5 is very easy, it's the sending that is the hard part. I've been able to get it to "send" from Manila, as in it says sent successfully, but it is not ever actually received.

For receiving you need the following settings in Manila:

IP Address: blank
Port number: 80
Server address: http://mms.sprintpcs.com (note: ignore the /servlets/mms at the end which a lot of people are saying. That may work too, but I flashed back to stock and took a look and they do not use it on the address)
Connect via: Sprint (assumes you completed provisioning, TELUS otherwise)
Send limit: 1024 KB (note: can be changed in registry, but doesn't matter yet as sending isn't working)
WAP version: none (note: this is key!!!! will not work on other WAP versions)

For sending I have found missing header items, and incorrect device identifiers, but I haven't worked it all out yet. I am leaning towards it being a configuration problem, and not a bug in the hard code. Personally, I receive an MMS here and there, but bascially never send them, so this works okay for me for now.