Guys,
This foxed me for a few days and is worth keeping an eye out for.
Following I'll explain the issue, then show you how to test if you have this 'bug'. It's worth checking if you're an avid tweaker!
Explanation
There are several hacks/tweaks that move DLL's to the SD to give u some ROM space. The Opera cache hack is the one that floored me. They typically involve editing the registry so that the EXE and DLL search path is appended to include the SD card (usually \storage card\DLLs).
The issue
With these hacks, you may (ie I definitely did, and I definitely solved it by correcting this) find a 5 to 10 second delay 10% of the time that you turn on your device. This manifests as a real issue in several ways:
When you turn on, screen stays blank so you press power key again and screen flashes on then off, so you press again and finally you're in. Particuarly evident if you run WisBarAdvanced2 which is clearly looking around for DLLs
When you call up the dial pad, your keypresses take several seconds to respond
When receiving a call there is a long delay before your phone starts to ring. Even tho you answer ont he first ring calling party says "where you on the jazz or something?"
When making a call you get "dialing..." and the other party is actually connected and listening to you swearing about what a piece of sh1t your JasJar is cos it won't connect (actually, this may be a problem over and above the issue covered here - anyone else experienced this?)
Testing whether you have this issue
Go to phone app
Turn off JJ for 1 full second
Turn on and immediately press a number key
Did it take 10 seconds to respond?
Repeat 10 times, problem will hit me at least 8x within 10
If you find a delay, repeat whole test without SD card. Here I find that I get the problem once, but not thereafter. It's like the JJ needs to find out that the SD card is not there, and then it doesn't do this 10sec checking delay again.
The phone pad is simply a test that can work on all setups, and seems to have an over 50% success (failure?) rate.
Let me know if this helped you. Perhaps I had a unique situaiton such as the Opera cache hack combines with WA2?
Edit: Since fixing this, and one other issue, my JJ performs awesomely! The second issue is trning off UMTS until I need it. HATE that cos in ZA we have awesome 3G coverage, and I don't mind the cost. However, issue is that where there is a weak UMTS signal, JJ latches on and then becomes very unreliable in making/receiving calls (much like the old days of poor GSM coverage). Remember these devices nee to be in UMTS OR GSM mode - they do not run both at the same time.
Ok, this is a real doozy.
This happened on my original Hermes, and now it's happening on my (three day old!) new one too (just tried to Ring Areti Internet to speak to someone on behalf of one of my clients, and the moment I pressed 0 to speak to someone the microphone seems to just cut out).
The root of the problem is: I can ring a number, whatever, and if I get to a menu system, I tap in the appropriate number to navigate through the system. However, the moment I do so, when I do eventually get through to someone they can't hear me. I can hear them fine, but my microphone has totally cut out - and even trying things like hitting mute / unmute makes no difference.
If I don't press a button, and either hang on until the menu system just puts me through to someone, the mic works fine. The worst thing about this problem is that it's unpredictable; it can happen all the time or it can just happen every so often, and there's no visual or audio indicators to say otherwise that the problem is occurring.
My two Hermes models are quite vastly different in model: the old one was an HT634 and this one is a 643, so the question of the problem being a hardware one spread across several models doesn't apply. This is REALLY ANNOYING, not only does it piss off the person on the other end but if you're stuck in a queue waiting to speak to someone for 20+ minutes, finally getting through and finding that you can't be heard is TOTALLY ANNOYING!
What's even more confusing is this: I thought it might be a permanent problem, so I tried ringing my home phone, then getting my friend to make like an interactive menu system and just say "press 1 to test this, press 2 to confirm that this is a really stupid thing I'm having to do for you, press 3 to confirm that you don't mind me hitting you after we're done testing this idea of yours"... You get the idea. I pressed a button (more than one in fact, the second time I tried it), waited the appopriate length of time that it would take in the real world to get connected, and started speaking - and the person on the landline could hear me fine.
The problem was also present (and intermittent) on my first Hermes, but it was unpredictable. I'm not in a great 3G signal area, and as I look at my phone at the moment it's gone back to GPRS. I also noticed on the MoDaCo forums that some people in London were suffering from problems where they couldn't hear callers, but the person at the other end could hear them fine (they suppose, as they weren't hung up on even though they couldn't hear their caller) - they had to force their phone back to 2G to resolve the problem. However, my microphone doesn't cut out during normal phone usage, so it's just really bugging me that I can't figure out why the hell this is happening!
My Hermes is pretty much stock: T-Mobile ROM, nothing cooked or patched, I just have the odd little bunch of harmless utilities installed: a screen cap application, Map24 Mobile, Microsoft Reader, Media Metrics Meter (usage tracker, you get paid £5 a month for submitting your stats to them so it pays for the Web 'n Walk), Opera Mobile, TCPMP, SMSDRFix, Vibra Switch, WM5NewMenu and Total Commander... They're the only significant additions.
This is driving me nuts! I never had this problem on my old Alpine, though granted it was on O2. I've even had this problem when calling the T-Mobile support line! Which as you can imagine is MOST frustrating.
Anybody have even the faintest idea as to how to solve this problem? It SEVERELY hinders my ability to ring any kind of helpline or support / sales line... And until I found an alternative (direct dial) number to get through to T-Mobile Customer Services, I wasn't even able to ring them!
had exactly the same problem with a Vario II. I couldn't set up my voicemail!
Exchanged unit for a new one and now works fine. No problems so far
flashflash said:
had exactly the same problem with a Vario II. I couldn't set up my voicemail!
Exchanged unit for a new one and now works fine. No problems so far
Click to expand...
Click to collapse
Argh... It took me long enough to get this replacement!!! Vario 2s are like golddust at the moment.
What model number is your new unit? Mine is an HT643 (first one was a 634)...
when i check my balance it shows failed and sometimes when a message comes the screen turns on and then after 2-3mins the message is recieved
any ideas if this is a radio problem because on other cell phones this works fine
By other phones do you mean non windows mobile phones.
I ask because they work in a different way when it comes towaking up the phone software for incoming calls and messages.
In simple terms a non wm phone is always on but the screen is off (so it reacts almost instantly). A wm phone cannot run all the time in the background or else the battery would be flat in no time - what with it's larger operating system and running applications. (It therefore has to truly wake up and start all those processes going - this takes time. It also accounts for the screen coming on and then a delay before it starts up the messaging/phone applications before either the phone call or text message can come through.
This delay is a price you pay for a more sophisticated phone wih more processes to run. There is however talk of the WM system being changed to run continuously like a regular phone - because in practice it takes a lot of power to start and stop the process when we put the wm phone in standby. So the benefit of stopping and starting processes may not be as great in saving power as first thought.
Regarding your other issue with the short codes for getting your balance for example. In my case with O2 *#10# should get my balance. I have never got this to work on my unlocked phone - it always fails. Whether this is true of a phone tied to a particular network I'm not sure. Perhaps someone else has an answer.
Mike
yes i was meaning a non wm phone.this doesnt bugs alot but the balance check always annoys me.
before hermes i got a htc touch(elf),it was also unlocked but didnot showed this error so what can i do about this problem?
i think this is concerned with radio version
sometimes calls from same network shows same name although the calling number is different
any ideas how can this be fixed
So i have had my hero for a couple of months now, and ive been noticing i get voicemail notifications without my phone ever even ringing, i was hoping u guys could help me out and to see if you guys have the same problem
so i had my friend sitting right next to me and he called me, it took like 8+ rings on his side before my phone actually began ringing on my side and then after 2 rings that i heard on my side the phone went straight to voicemail.
but it didnt happen all the time, sometimes my phone rang right after we heard 2 rings on his side, which i think is normal
now i use google voice, i was wondering if you guys experience this as well? and if so do u use google voice or normal voicemail.
also i think its worth to mention i changed my phones meid to match my old lg rumor. so it is a cloned phone, but the original donor phone is always off with the battery out.
this problem sucks cuz people call me and in essence i dont pick up their calls because my phone sometimes doesnt ring n people think i ignore them...
I haven't ever had that problem (and I also use GV). But you can change your slot cycle to tell it to poll the tower more often which might help you. Now there is going to be an extra delay because of GV, but it shouldn't take 8 rings. If this doesn't work then there might be something causing a slow down on your phone which is why it takes a while to realize it's ringing, or it might be the MEID swap causing strange things.
##3282# Set slot cycle index to 1. Your phone will poll towers more often and will respond to incoming texts and calls faster.
http://forum.ppcgeeks.com/showthread.php?p=1391130
this was set to 2 so hopefully this works, what about 0?
0 might drain your batt faster then normal
So I went to "##3282#" to make a change and it wouldnt let edit anything because it asks for password, anybody know what could be the password?
The password is actually your phones individual MSL#. It can be obtained by calling Sprints tech support. They might refuse to give it to you, but just tell them what you want it for and they probably will.
had my MSL thankfully since i make notes for all my sprint calls.
thanks for this tip - hope it helps me out too!
I just did this, lets see what happens.
Any updates on this? I am set to 0 for slot cylcle but consistently get more than 2 rings before my phone rings.
Please correct me if I'm wrong, but I think slot 0 is reserved for police and other first responders. You're not supposed to use it without permission.
I believe I read somewhere that changing the slot cycle index on the phone itself will not actually change anything, except that it may drain your battery faster. As I understand it, the tower's setting for that attribute will override end-user devices' settings.
FWIW, I changed it on my Hero, and it made exactly zero difference in the ring delay (timed in seconds). If you watch a timestamped kernel debug log when a call comes in, you can see that it simply takes the phone a long time to get its sh*t together and start ringing. This is common across HTC phones. Piss-poor design for a phone if you ask me.
My phone takes 2-3 rings on the callers end before my phone rings, this would be fine if it didn't go to voice mail after 6 rings. Is there any way to change how many times the phone rings before it goes to VM?
Nanan00 said:
My phone takes 2-3 rings on the callers end before my phone rings, this would be fine if it didn't go to voice mail after 6 rings. Is there any way to change how many times the phone rings before it goes to VM?
Click to expand...
Click to collapse
According to Sprint's latest answer, "no". With past phones, Sprint HAS changed that parameter for me. My previous phone would ring for more than 60 seconds before going to voicemail. Sprint now tells me that is not possible, nor was it ever possible. Obviously, it *was* possible. I didn't just imagine that it would ring for a full minutes.
The ring configuration is actually managed by number of seconds before voicemail, as the number of rings depends completely on what ringtone you use. I forget exactly what number they have it configured for currently (I know its less than 30s), although I do remember that the Hero itself only rings for exactly half of the Sprint-specific time. Sprint did acknowledge that that Hero (and other smartphones) have a problem with the ring time, but they offered no suggestions to fix it.
I was going to use this method to try to reduce my ring delay. When I put in ##DATA# nothing happens on my phone. I know the debug codes work because I can put in *#*#4636#*#* and it brings up a screen. Any ideas why this code doesn't work?
kynetx said:
Please correct me if I'm wrong, but I think slot 0 is reserved for police and other first responders. You're not supposed to use it without permission.
Click to expand...
Click to collapse
Negative, that is the Access Overload Class.
I have my slot index set to 0 and my ACCOLC set to 2. I make it a full day without charging for whatever it is worth.
Trevor said:
SCI - Slot Cycle Index - This determines how often a handset polls thenetwork for coverage and incoming packets. The default value is 2. A"Slot" is 1.28 seconds and doubles with each incremental change from 0to 7 (0=1.28, 1=2.56, 2=5.12 seconds, etc). setting a handset to pollmore often may use noticibly more battery if coverage is thin orlacking.
ACCOLC - Access Overload Class - This code determines your priority tomake and receive calls on the network. Higher the number, lower thepriority. Lower the number, higher the priority. Emergency Servicesreserves 0 + 1 (please do not use these) leaving your choices to 2-9.Years ago we began defaulting this code to the last digit of a usersMIN to help assure equal priority seeding.
Click to expand...
Click to collapse
I found this thread on the EVO forum and decided WTH I'll try it. Worst that can happen is I have to go back to the stock prl cause it doesn't work. However when I tried it, I have significantly less ring delay "lag" and not one call has gone directly to VM. Hope it helps everyone that is having this problem. Please report back with results.
BTW I had no hand in figuring this out I am just passing on my findings. all credit goes to techknowfile.
http://forum.xda-developers.com/showthread.php?t=696073
animal7296 said:
I found this thread on the EVO forum and decided WTH I'll try it. Worst that can happen is I have to go back to the stock prl cause it doesn't work. However when I tried it, I have significantly less ring delay "lag" and not one call has gone directly to VM. Hope it helps everyone that is having this problem. Please report back with results.
BTW I had no hand in figuring this out I am just passing on my findings. all credit goes to techknowfile.
http://forum.xda-developers.com/showthread.php?t=696073
Click to expand...
Click to collapse
I tried this just for the heck of it and not 10 minutes after I rebooted I kept getting "Error 67 Data Call Failure your Sprint PCS Vision user name or password is wrong"
Maybe I did something wrong, but as soon as I put 60065 back on my phone it went away.
For reference I am in Knoxville, TN
Kcarpenter said:
I tried this just for the heck of it and not 10 minutes after I rebooted I kept getting "Error 67 Data Call Failure your Sprint PCS Vision user name or password is wrong"
Maybe I did something wrong, but as soon as I put 60065 back on my phone it went away.
For reference I am in Knoxville, TN
Click to expand...
Click to collapse
I am not getting this error. So maybe this will not fix everyone but it sure has helped me a lot.
Thanks for the reply. Kcarpenter
animal7296 said:
I am not getting this error. So maybe this will not fix everyone but it sure has helped me a lot.
Thanks for the reply. Kcarpenter
Click to expand...
Click to collapse
Luckily the area I live in has excellent sprint coverage (better than big red) Just wish we had 4g...one day...
This problem is the main reason why I will be abandoning my hero soon. I have tried at least a dozen different roms and have yet to find one where the phone function ACTUALLY WORKS............ WTF?? My phone usually rings for 2-7 seconds before going to voicemail in a good coverage area, and normally not at all when I'm at my house (poor coverage). I'm currently using the latest Fresh ROM (2.1.2), have done the slot-cycle mod, and have flashed the overclocked kernel, all to no avail. It may be a fine data device, but is a pretty damn pathetic phone.
Heck, I've even cleared my call history (which at 3 weeks old was long enough to lag the dialer for 4-5 seconds every time it was pulled up), and that hasn't helped. It also doesn't help that the phone app crashes on about 1/3 incoming calls.
I've got some serious issues with my Nexus 4, I've found posts with similar problems but not exactly what I have. I'm at a loss what to do next so any advice would be much appreciated.
I bought a N4 around March this year, direct from Google, and connected it to TPG Mobile here in Australia which uses the Optus network.
It was fine until about the end of May or beginning of June where it started losing signal regularly. First thing I noticed is it would start dropping calls and displaying "No network available", the triangular status bar at the top would go blank (completely black, not grey) for about 30 seconds, then it would return to normal signal and I could make calls again. However it would do this every few minutes, whether I was on a call or not, and each time it would last roughly 30 seconds and then return to normal.
Around the same time I started to receive SMS on either a delay, or they'd arrive on-time, but then keep sending multiple times for about the next hour.
I rang Google, they got me to go through recovery mode, then it worked fine, for about 24 hours, before it started again. They sent me a new device, which did the same thing within hours of activation, so I requested a 3rd device. At the same time I thought it might be the sim card, so I got a new one of those too.
My 3rd device and new sim card worked perfectly for about 3 days then the same problem started. Factory resets etc seem to fix the problem for either minutes or hours, but never permanently.
Then last week I noticed further weird symptoms, I started getting the usual sms to say someone had called and left a voicemail, however my phone never showed any sign of a call (visual, audio or missed call in the call log). I confirmed with several people who tried calling me and they confirmed the phone rang on their end before going to VM. I tried it myself from a landline and it randomly rings or doesn't ring on my end, however I also noticed when I hung up on the landline without answering my Nexus 4, it continued to ring indefinitely, ie. it hadn't registered the caller hung up.
My provider assures me there isn't an issue in my area, my wife uses the same provider (with an iphone) and has not had these issues. I can't swap sim cards with her though as she has a full-size sim. I tried another sim with my phone for a few hours and it worked fine, however my phone with my sim will sometimes go a whole day without issues so it wasn't long enough to truly test it.
I've deleted all apps that might somehow affect it and the hasn't helped either.
Basically I'd like to know is this likely to be a phone issue, and I pursue the issue with Google, or some sort of network/sim issue and I pursue it with my provider?