On my Eris I was able to use ##PST on my Eris to change my slot cycle index, but for my new D2 it is not working. How would I go about accessing this on the D2? Thank you.
Edit: Did a through Google search, which brought up ##7764726 but then not sure where to go afterwards to adjust the slot cycle for calls.
tbaker077 said:
On my Eris I was able to use ##PST on my Eris to change my slot cycle index, but for my new D2 it is not working. How would I go about accessing this on the D2? Thank you.
Edit: Did a through Google search, which brought up ##7764726 but then not sure where to go afterwards to adjust the slot cycle for calls.
Click to expand...
Click to collapse
you can use qpst to make that change. it's the only way i've heard of on moto phones.
so i just put ##QPST in the dialer then?
tbaker077 said:
so i just put ##QPST in the dialer then?
Click to expand...
Click to collapse
no, it's a program for the computer.
this is how to set it up
http://thewindows7site.com/forum/threads/19170-Diagnostic-Mode-for-Droid-X
And it works for the D2 right?
The article doesn't explain what to do when using the QPST app.
tbaker077 said:
And it works for the D2 right?
The article doesn't explain what to do when using the QPST app.
Click to expand...
Click to collapse
this procedure works practically the same on the droid1, droid2 and droidx. there's only a slight variation with the droidx cause ther is no keyboard.
But the procedure for droid1 and droid2 is the same. see here http://www.howardforums.com/showthread.php/1593533-service-programming-on-the-moto-droid
Using qpst is the easy part. open it. connect to the port you made. then choose Service Programming in qpst, then click on "read from phone", change the slot cycle index, then click on "write to phone"
WARNING: this is very powerful software that can write to the NVRAM of your phone. which means you can bork your **** with one wrong click. i highly recommend you do some googling and reading before you do it. qpst has been around for many years and very popular for reprogramming lots of different phones so there's plenty of info out there on it.
So what is slot cycle index? Why would one need to change it. Just interested to learn more. I've got the qpst program for messing with an old phone and might try this if it's worth it on my D2.
Sent from my DROID2 using XDA App
newk8600 said:
So what is slot cycle index? Why would one need to change it. Just interested to learn more. I've got the qpst program for messing with an old phone and might try this if it's worth it on my D2.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
it's a common cure for phones that have a bad "ring delay". Or, it's a way to save some battery life.
On the CDMA Paging Channel (this is the shared channel that all phones
listen to for incoming calls and other control info), time is divided into
"slots". To conserve power, phones that are currently idle only "wake up"
and listen for messages on the Paging Channel during their assigned
slots. The slot cycle index determines how often the phone's slot comes
around. If the slot cycle index is 0, the phone wakes up every 1.28
seconds. If it's one, it wakes up every 2.56 seconds. If it's two, it's
every 5.12 seconds, and so on. The larger the setting, the more power is
conserved, but the longer it takes to page the phone for an incoming
call. You can imagine that if it were set to 10.24 seconds, few callers
would hang on the line long enough for you to answer your phone.
There are two settings that govern this. One is the "preferred slot cycle
index" in the phone, and can be set via service programming. The other is
the "maximum slot cycle index" set in the base station and broadcast in
overhead messages on the Paging Channel. The phone has to use whichever
number is smaller.
Still can't get HW Virtual serial to connect. It worked once last night, but now it isn't. Any ideas? Real shame I can't just change it like I could on my Eris or Samsung i760, with a dialer code.
Edit: I must have skimmed it, but on the Droid 2 what is the T key?
tbaker077 said:
Still can't get HW Virtual serial to connect. It worked once last night, but now it isn't. Any ideas? Real shame I can't just change it like I could on my Eris or Samsung i760, with a dialer code.
Edit: I must have skimmed it, but on the Droid 2 what is the T key?
Click to expand...
Click to collapse
the letter T on your keyboard
I know that but how do I use to it to enter diag mode, because the HW virtual serial isn't working for me.
tbaker077 said:
I know that but how do I use to it to enter diag mode, because the HW virtual serial isn't working for me.
Click to expand...
Click to collapse
it's right there in the first post of the hofo link i gave you.
I tired what was stated in that link, but I still can't get HW to connect. Still getting an error.
Edit: tired the T key but I don't think it worked? Still getting connection error.
So, I was able to get HW to connect to the phone again but QPST says no phone for the specific port and settings I chose. Could this be some how driver related, or is it something else?
call ring delay is found in the build.prop. if you're rooted, jrummy's apps can help.
Sent from my DROID2 using XDA App
Im pretty sure it is not really a software thing, but a deeper phone things. But, as far as I know if it was software thing then a simple reg edit on my old Samsung i760 would have done the trick instead of putting in a dialer code, to mess around with some slot index settings and then having the phone turn off and restart(was like 4min process total). I could be totally wrong here(kind of hope I am), but if I am not it be nice to get this method working. Thank you.
gunz.jones said:
call ring delay is found in the build.prop. if you're rooted, jrummy's apps can help.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
that only changes the ring delay when dialing out. it has nothing to do with the slot cycle index.
Can you maybe assist me on why the D2 isn't showing up in QPST despite HW is connected to the phone, please?
tbaker077 said:
Can you maybe assist me on why the D2 isn't showing up in QPST despite HW is connected to the phone, please?
Click to expand...
Click to collapse
sorry dude, i dont know what the problem is. i dont have a d2. if you look in that hofo thread, there are lots of suggestions and tips to getting that to work. do you have it shut off, then hold the T, then plug in usb cable. then wait and continue to hold the T till it's done. dont press power button.
do you have an unrecognized devices in your device manager when you're doing this?
I read a portion of that long thread, and most was for the D1 and not really related to what I have. I don't see any issues listed in device manager regarding the D2. Maybe you can post me the full 32bit Droid 2 drivers, because the ones on Moto's site didn't seem to be the right one, and I have used the wrong drives I got doing a google search. Thank you.
Related
I hate to post a thread like this, but after searching and basically pulling my hair out, I've decided it was time.
Anyway, as title suggests I have an I9000m with the 2.2 UGJL2 *Typo in title, sorry!!*
Heres the problem with the phone...
Its a bell phone, unrooted or modified. Its running 2.2 JL2. When used with an bell SIM it will dial out and receive, receive texts, send them. However it won't receive picture messages, well it receives but just says downloading (and the plan does have it)
It also won't connect to the mobile network. If I manually set APN it does, but then its ability to call out is brutal for some reason. Also I threw my virgin mobile sim in it, set apn and it would go onto the internet no problem, but calling and text suffered big time.
It also seems to lag huge all the time, it'll freeze, you hit the center button and it just takes screen shots.
Its a refurb phone if that helps. Its actually my gfs phone, I picked her up a HTC incredible S... she says if we can fix the old one she kinda wants the samsung back.
Any help would be appreciated.
Mike
Have you tried a factory reset to see if that fixes the problems? That would be the best starting point.
Sent from a telephony device
radeon_x said:
Have you tried a factory reset to see if that fixes the problems? That would be the best starting point.
Click to expand...
Click to collapse
Been done twice. Also have had two new sim cards installed aswell. I figured before I tried rooting it would be best to consult you guys. Is it possible that there's a hardware issue?
Thanks
Mike
Based on your description it doesn't sound like a hardware issue, but no way to know for sure.
I think your next best bet would be to try reflashing JL2 (or KC1 even) using Odin; as long as you can get to download mode via the 3 button combo. If you're still having problems after that then probably it is hardware.
Sent from a telephony device
radeon_x said:
Based on your description it doesn't sound like a hardware issue, but no way to know for sure.
I think your next best bet would be to try reflashing JL2 (or KC1 even) using Odin; as long as you can get to download mode via the 3 button combo. If you're still having problems after that then probably it is hardware.
Click to expand...
Click to collapse
Got er fixed. After I put the phone down and enjoyed a beer for a bit, I went back and basically wiped the phone clean, I think I did it 3 times in a row, using both the 3 button download mode one, and two different ones than can be accessed via the dialer. After doing that I retryed the APN settings again and ALAS it finally worked correctly. Its now connecting to the HSDPA and is also downloading MMS messages like it should. Its also yet to lag again. I'm assuming it was an app that was causing that aswell.
Regardless, the misses is happy, I might keep the Incredible S (currently have the HTC legend, lovely phone, but it does feel under powered compared to the I9000 and the Incredible S)
Sometimes I think a guy has gotta step back and relax for a minute lol!!
Thanks again
As of this morning (at least), the earpiece in my phone is no longer functioning. I can't call people and hear them without using the Speakerphone or a Headset. I've initiated contact with Windows Phone and Samsung support, but I was hoping maybe someone here has run into the issue and found a fix, as I imagine the "fix" from MS and Samsung is going to be send the phone in for repairs.
I'm currently running 7392, so I might try rolling back, but the one person I saw on another forum with this issue didn't get it fixed this way.
Also, I'm using a microSD card.
To make things even better, the first boot after a battery pull brings up the red screen.
If you saw the red screen, you probably did the 16-bit reg edit fix. What other reg edits or diagnostics stuff have you done?
Sent from my SGH-i917 using XDA Windows Phone 7 App
I had the exact thing happen to me minus the red screen issue. What i did was use the diagnosis app type in *#0289# and test all the speakers, make sure they are all on too. Then restart your phone and it should correct the issue.
other info. I am running samsung focus stock 7390 on att
also- if you do not have the diagnosis app it is the sticky thread in the top of the general section.
munkeyphyst said:
If you saw the red screen, you probably did the 16-bit reg edit fix. What other reg edits or diagnostics stuff have you done?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Yeah, I forgot that the Advanced Configuration Tool auto-sets it.
Unfortunately, I didn't see siralex's suggestion until after I already got the phone replaced by AT&T. I appreciate the intention, guys.
Confirmed
FishFaceMcGee said:
Yeah, I forgot that the Advanced Configuration Tool auto-sets it.
Unfortunately, I didn't see siralex's suggestion until after I already got the phone replaced by AT&T. I appreciate the intention, guys.
Click to expand...
Click to collapse
I can also confirm. I know this is an old thread but for others who may have developed occasional random reboots and the red screen of death when rebooting, I was having the same issues for a while. What I also found was that I had checked the "fix 32 bit" checkbox in Advanced Configuration when I installed it. I unchecked this box and saw these symptoms disappear immediately and not return. It got to the point I could not reboot without getting the red screen and it took several battery pulls to be able to turn the phone back on.
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
UPDATE: 15 Mar 2012:
I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.
I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.
The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.
For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.
Here's a link to the thread showing the hardware mod http://forum.xda-developers.com/showthread.php?p=23725671#post23725671
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
sageDieu said:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
Click to expand...
Click to collapse
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.
Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.
i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.
the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.
It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.
Sent from my SCH-I500
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
electric bill said:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
Click to expand...
Click to collapse
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Downgrade
I have found that the only thing that works is to downgrade. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.
ssewk2x said:
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Click to expand...
Click to collapse
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
electric bill said:
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
ssewk2x said:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
Click to expand...
Click to collapse
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.
Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.
Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:
http://db.tt/xERensX3
It happens when you have a low signal. It's was so annoying but no longer have that issue.
Keep me Fascinated.
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
SnrSuave said:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
electric bill said:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
electric bill said:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
Click to expand...
Click to collapse
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
th3b3 said:
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
Click to expand...
Click to collapse
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.
dff_jx said:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
Click to expand...
Click to collapse
technically if we change the driver code, which is in the kernel then it's been modded...
If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.
DOH! Flashed to Zero Hero and my phone is now displaying the wrong phone number. Will someone please clue me in on how to fix this?
Additional information: I have 4 Heros all activated on Metro PCS. The other 3 are working and have Damage Control 1.0 installed on them, so possibly I can retrieve settings from one of my working phones?
I have flashed ROM's before and this hasn't happened, not blaming it on the ROM though, could have been my own stupidity. The ROM looks awesome and I cant wait to get it working so I can test it for replacement on my other 3 phones.
Many Thanks!
EDIT: Been searching Google for hours now.. so I guess the fix is not an easy one??
Edit 2 to add that this cant be done. When the phone was originally flashed the guy didnt use my phones MEID for whatever reason.. therefore the phone is not in the MetroPCS system. I tried to get the info from MetroPCS but no dice.
I will not go back to the same place to get it fixed.
Hahahaha!
Sorry.... that's all I got.
Are you sure you're not looking at the wrong thing
Sent from my HERO200 using XDA App
Yeah, looking at the phone info under settings. If I try to make a call I get the standard Sprint "Your account can not be validated" recording.
Not gonna give up.. I know its possible. I may be a nOOb but I know how to follow directions and be persistent.
Will probably need to update the PRL as well.. but I have found some info on that.. just not able to find for changing the MDN. I am guessing I will need to download QPST workshop.. been looking for a download of that as well.. well I have a copy but its from 2006, so I am guessing thats why my phone wont connect.
Its always something.
lol well first of all if your supposed to be on metropcs and your getting sprint recordings, definitely change out your prl to one that works with metro.
second of all, if your getting a weird phone number, flash back to stock sense rom and use the ##msl# (? i think thats the one) to switch your mdn and msid to what they are supposed to be. if you dont know what they are supposed to be im sure you can call metro and find out.
good luck and ask more questions if you need more help
edit: pm me if you need more help, i may be able to help
Yeah I guess changing the PRL is a good place to start... I need a break from trying to fix the MDN anyways.
As far as the msid is concerned.. do you think MetroPCS has that information? Or even willing to give it to me? I dont want to go back to the place that originally flashed my phone to Metro because they charge $65 each time. What would I tell Metro for the reason I need my msid?
Thanks!
Okay got the MSID #. According to the CS rep its the same for all my phones, hope like hell he knew what he was talking about.
Now I am still stuck, unable to get QPST set up properly as I have no options to install any com port at all...... Back to Google.
you shouldnt need qpst, just flash back to a stock rom, nfx stock is pretty good for this, and enter ##msl# (your 6 digit msl number instead of the word msl) into the dialer, and there it should give you the option to change your mdn or msid.
keep us updated, hope you get this phone working again
edit: if you want to use qpst, i know for cyanogenmod you can open up adb shell in your command prompt on computer (or terminal emulator from market i beleive) and enter this
echo 1 > /dev/qct_diag_enable
and windows will see the diag driver needs installed and adds a com port. YMMV but i would think it is universal for roms, but dont quote me on that. here is the link i found this at: http://forum.cyanogenmod.com/topic/...t-cdma-codes-on-dialer-need-diag-mode-solved/
good luck
I have tried
echo 1 > /dev/qct_diag_enable
and it didnt work for me. If I connect my other phone to qpst or CDMA I get the com ports and can connect so I know I have that part right.
Installing another ROM kind of defeats the purpose as I suspect that this ROM is what overwrote my settings, so if I install another ROM I would be back at square one when reinstalling this one. Unless of course there is a way to back these individual settings up that I am not aware of?
I wouldnt go through this much trouble for any other ROM as I feel that Pico Gingerbread is exactly what this phone needs. I like the stock look and feel.
i know it seems inconvenient, but if you cant enter diag mode or use ## codes on zero hero (which i know you cant use the ## codes, those are only able to be used on stock rom) then your hand is pretty much forced to go back to stock. i've flashed many roms on my hero after getting the phone settings set, and never have i lost the phone number, data, etc.
try flashing back to stock with nfx's sprint stock rom, and get your phone all good to go again, and then try to reflash to zero hero. it shouldnt take much time, and if it does it again (where you lose your phone number) then we know something is going wrong in the process, at which time you should ask mattcrystal in the zero hero rom thread.
edit: http://forum.xda-developers.com/showthread.php?t=849024 is nfx rom, i suggest it over stock but remember to flash the kernel that comes with it or your phones cpu will be pegged down around 200 mhz
Thanks for your reply.. I did as suggested and installed nfx's sprint stock rom.
With that I was able to get into diag and I played around with various programs ALL damn day.
Problem was the MIN was wrong. On phones flashed to MetroPCS sometimes the MIN is not the same as the MDN.
Now when I call 611 I get the proper MetroPCS recording.. but when I make a normal call I get a strange recording about "if I would like to make a prepaid call"
(Virgin mobile perhaps??)
But, progress is good. In the end I will try the Zero Hero ROM again.. at least if something goes wrong I will know how to fix it.
At the rate I am learning I should be cooking ROMs in a couple weeks.
EDIT: I have the information I need to make this phone work, but I am doing something wrong. Gonna make a new post in a non-legacy forum in hopes that I get some much needed help.
your mdn is your phone number, and your min(msid) should be the routing number (a generic phone number that i think is like a routing number, metro should be able to give it to you, it sounds like you already have it.) your close to being done, just program your mdn as your phone number, and your min(msid) as the number you have that isnt your actual phone number. (that metro gave you)
hopefully you get it going, your close to the finish line
"EDIT: I have the information I need to make this phone work, but I am doing something wrong. Gonna make a new post in a non-legacy forum in hopes that I get some much needed help."
theres no need for that, i told you what you need to do to fix it, whether you take my advice or not is now your problem. if you dont have your msid(min) whatever you want to call it, call metro and tell them you need that info, and they should give it to you.
I have tried and failed at entering the MIN. I have tried in CDMA tools, QPST and DFS CDMA and the phone itself. No matter what number I put in leads to the phone not working. I am at a loss of anything else I can think of to try.
What I think I might need is someone with a lot of CDMA experience... but then again I have been wrong before or I wouldn't be where I am now.
Thanks
Edit 2 to add that this cant be done. When the phone was originally flashed the guy didnt use my phones MEID for whatever reason.. therefore the phone is not in the MetroPCS system. I tried to get the info from MetroPCS but no dice.
I will not go back to the same place to get it fixed.
good luck and if you figure it out please share with us how you did it
Hi,
Have an Incredible. Rooted with s-of and MIUI 2.97 and Android 2.3.2. I am trying to manual program it to get in and change MDN/MIN numbers. I have tried ##778 and ##778#, but all that happens when I do this is I get the Verizon recorded message that they can't complete my call. No programing menu, etc.
Any suggestions?
BM
bartman99 said:
Hi,
Have an Incredible. Rooted with s-of and MIUI 2.97 and Android 2.3.2. I am trying to manual program it to get in and change MDN/MIN numbers. I have tried ##778 and ##778#, but all that happens when I do this is I get the Verizon recorded message that they can't complete my call. No programing menu, etc.
Any suggestions?
BM
Click to expand...
Click to collapse
You must be on a sense rom to use ##778# (epst). You will need to do a backup, flash a sense rom, change the settings, and then restore back to MIUI. As long as you dont do a factory reset in between, the settings will stick and you wont have to reactivate. What are you trying to do?
bartman99 said:
Hi,
Have an Incredible. Rooted with s-of and MIUI 2.97 and Android 2.3.2. I am trying to manual program it to get in and change MDN/MIN numbers. I have tried ##778 and ##778#, but all that happens when I do this is I get the Verizon recorded message that they can't complete my call. No programing menu, etc.
Any suggestions?
BM
Click to expand...
Click to collapse
Try *228 from miui
Sent from my ADR6300 using Xparent Red Tapatalk 2
cmlusco said:
You must be on a sense rom to use ##778# (epst). You will need to do a backup, flash a sense rom, change the settings, and then restore back to MIUI. As long as you dont do a factory reset in between, the settings will stick and you wont have to reactivate. What are you trying to do?
Click to expand...
Click to collapse
Bummer. I was hoping that wouldn't be the case.
I bought a used Incredible, modified it to use MIUI just the way I wanted and then activated it on PagePlus (and activated it using *22890, *228, *22899). The ESN is good and it activated fine. Only thing is, the phone still "thought" its phone number was the old one, not mine. I could call out fine, but incoming calls to my number didn't come though (I never tired to call the old number from the previous owner). I contacted Pageplus again and they everything is fine on their end and I would have to manually program it. Well since the Incredible is not supported by P+ (and certainly one that is rooted with a custom ROM), I figured I'd do it myself. I need to get into the manual programming menu to change the MDS and MIN (and whatever else has the old phone number and change it to my number).
I hope this was clear.
Thanks in advance... BM
You may be able to use a pc program called qpst to change the settings. Im not sure if qpst is reliant on epst being on the phone or not.
bartman99 said:
Bummer. I was hoping that wouldn't be the case.
I bought a used Incredible, modified it to use MIUI just the way I wanted and then activated it on PagePlus (and activated it using *22890, *228, *22899). The ESN is good and it activated fine. Only thing is, the phone still "thought" its phone number was the old one, not mine. I could call out fine, but incoming calls to my number didn't come though (I never tired to call the old number from the previous owner). I contacted Pageplus again and they everything is fine on their end and I would have to manually program it. Well since the Incredible is not supported by P+ (and certainly one that is rooted with a custom ROM), I figured I'd do it myself. I need to get into the manual programming menu to change the MDS and MIN (and whatever else has the old phone number and change it to my number).
I hope this was clear.
Thanks in advance... BM
Click to expand...
Click to collapse
Is this a phone number you've had for a while, or a new one? If it's a new number, make sure you're calling the MDN (aka My Phone Number) and not the MIN (Mobile Identification Number). Page Plus phones will have two different numbers here, it's easy to get confused and call the MIN instead of the MDN.
musical_chairs said:
Is this a phone number you've had for a while, or a new one? If it's a new number, make sure you're calling the MDN (aka My Phone Number) and not the MIN (Mobile Identification Number). Page Plus phones will have two different numbers here, it's easy to get confused and call the MIN instead of the MDN.
Click to expand...
Click to collapse
No, my phone number is an old one that I have used for many years with P+. The one on the phone (MDN) was never mine, was likely from the previous owner and was never on the P+ list.
Anyway, I tried flashing a couple of mostly stock Sense ROMs with no luck (Stock +, Touch of Blue). I can get into the PRL editing mode (##775, I think), but ##778 does nothing. I have yet to try to return it to unrooted stock with s-on, but that is my next step:crying:
BM
bartman99 said:
No, my phone number is an old one that I have used for many years with P+. The one on the phone (MDN) was never mine, was likely from the previous owner and was never on the P+ list.
Anyway, I tried flashing a couple of mostly stock Sense ROMs with no luck (Stock +, Touch of Blue). I can get into the PRL editing mode (##775, I think), but ##778 does nothing. I have yet to try to return it to unrooted stock with s-on, but that is my next step:crying:
BM
Click to expand...
Click to collapse
I always find it strange that some people have issues accessing epst. I have tried many stock based roms including stock+ and TOB, and have always been able to access the menu.
I would not go s-on for any reason. It makes it way harder to reroot, and i doubt it would make a bit of difference with your issue.
I would just stay s-off and do the latest ruu. Or as i sugested earlier check out qpst.