|ROM|¯`·.¸¸.- Energy -.¸¸.·´¯ * |July 4| 21916|29022 * Sense 2021 + flavors

[muzicman82]

[QUOTE=sly;1984351]That's been answered a billion times Just install NRG.ROM.Sprint.MMS.Settings-Boushh.cab from the paperclip

Thanks. Like I said, it's nearly impossible to find anything quickly with this many posts on a single thread. I've suggested before that PPCGeeks allow large threads to be give their own sub-forum for organizational purposes.

Also, there used to be a FAQ post on the first page, but it is gone.

As for the cab, why doesn't the fix get implemented into the Sprint provisioning cab?

[Wizzard]

+1 on the pictures.

Thanks Monfro.

Wish he would also answer the requests about the Cemonex patch.

[bteljuice]

Originally Posted by Monfro

This is a screen of the dialer i install, that shown contact pictures:
02_Added.Jpeg

Please report on Twitter (or here), so NRGZ can know what is the situation.

So which Dialer did you install? We would all like to have that

[jeffx]

Originally Posted by cmai

Does the Oct 7 ROM fixes the DRM issue?

Thank you.

I was loving this ROM, until I tried to play any of my DRM music. Is there a fix or CAB to get DRM working on this ROM? Thanks!

[tootseroel]

Originally Posted by slimbrown29

Hey there forum. From about 2am last night I have had the folllowing problem that I can resolve and its driving me mad.

Once the device goes to sleep ( either by me pressng the power button, or automatcally), the screen remains turned off when I try to re-awaken the device. I can tell the phone is on because all the LEDs work, I can even recieve calls. But I cant see s**t on the screen!
The only to turn the screen on is a soft reset. I even tried a hard reset, but the problem still remains. I am not usng any lockscreen. Just the Sept 25th GTX rom.
Any ideas on solvng this prob are appreciated.

Im still having this problem with the last few Roms i have been using. currently using the sencity 21683 oct 25 rom. i did hard reset, task 29, rom install, hard reset and still keeps happening. im using ninja duck oct 1.5 at 690, which i had running for a couple weeks, no prob. i also have android installed, which i think is the problem now. any way to fix this situation without getting rid of xdandroid ?

[cashmoney121]

Here is Monfro's dialer lite post: http://forum.ppcgeeks.com/cdma-tp2-upgrades/86489-rhodium-cdma-energy-oct-25-21916-21683-sense-2018-a-2748.html#post1983010

[apet8464]

Originally Posted by tootseroel

Im still having this problem with the last few Roms i have been using. currently using the sencity 21683 oct 25 rom. i did hard reset, task 29, rom install, hard reset and still keeps happening. im using ninja duck oct 1.5 at 690, which i had running for a couple weeks, no prob. i also have android installed, which i think is the problem now. any way to fix this situation without getting rid of xdandroid ?

I've been having these issues as well with the last few ROMs and I OC with Ninja Duck Oct 1.5 as well. I usually stay with the stock OC settings (max clock of 729 MHz). Given the symptoms, I concluded that it was related to the OC.

Anyway, I just flashed to Oct 25 21683 this morning and decided to go back to SetCpuSpeed-1.0d and Msm7kCpuSpeed_v2 since i never really had any issues with that combo. I'll let you know if the SOD problems persist.

[puff601]

Originally Posted by tootseroel

Im still having this problem with the last few Roms i have been using. currently using the sencity 21683 oct 25 rom. i did hard reset, task 29, rom install, hard reset and still keeps happening. im using ninja duck oct 1.5 at 690, which i had running for a couple weeks, no prob. i also have android installed, which i think is the problem now. any way to fix this situation without getting rid of xdandroid ?

hey man I had this same issue on stock sprint 6.5, never unlocked or anything. I tried several hard resets and it seems to be a hardware issue. there were a few others having the exact same issue around the time I was having it and one guy took theirs to the sprint repair center, they satis the ribbon cable was torn a little. so I want to say you have a torn ribbon cable too. so when the screen refuses to wake, you can still use the screen but can't see anything right? I got a warranty replacement...

[muzicman82]

[QUOTE=sly;1984351]That's been answered a billion times Just install NRG.ROM.Sprint.MMS.Settings-Boushh.cab from the paperclip

Ok, so I installed that cab and rebooted. I still get the "Invalid Argument" message. I can receive MMS messages just fine... and I could before I installed the cab. I hardly ever send picture messages.

Any idea?

[KIOWA69]

[QUOTE=muzicman82;1984694]

Originally Posted by sly

That's been answered a billion times Just install NRG.ROM.Sprint.MMS.Settings-Boushh.cab from the paperclip

Ok, so I installed that cab and rebooted. I still get the "Invalid Argument" message. I can receive MMS messages just fine... and I could before I installed the cab. I hardly ever send picture messages.

Any idea?

did you say that you have been getting this message for the last couple of roms? what i would do if i was you would be to flash back to stock, hard reset and see if it does it with that rom, if it does then you have something wrong with the phone, if not then it's something with the way you are setting up the NRG rom or something your importing because no one else is having that issue which tells me it's something with the way you are flashing, a bad flash or the phones messed up, just my 2 cents.