Related
Hey all,
Recently got the Kaiser. Flashed it with Dutty's latest ROM and added latest version of Slide2Unlock. Only made a couple of calls. The shorter calls seem to be ok, but after I got off of a 8mins call, the screen was off so I pressed the power button to bring it back on and the phone was frozen at the call screen. Couldn't get out of it and had to do a soft reset. Not sure if it was just a one time thing or not.
Anyone else have any issues like this or know what could be causing it? I'm thinking it could be the Slide2Unlock, but my Slide2Unlock comes on after about 30 secs of not touching the phone and like I said the shorter calls worked fine and it would have been in affect during those.
mikeveli20 said:
Hey all,
Recently got the Kaiser. Flashed it with Dutty's latest ROM and added latest version of Slide2Unlock. Only made a couple of calls. The shorter calls seem to be ok, but after I got off of a 8mins call, the screen was off so I pressed the power button to bring it back on and the phone was frozen at the call screen. Couldn't get out of it and had to do a soft reset. Not sure if it was just a one time thing or not.
Anyone else have any issues like this or know what could be causing it? I'm thinking it could be the Slide2Unlock, but my Slide2Unlock comes on after about 30 secs of not touching the phone and like I said the shorter calls worked fine and it would have been in affect during those.
Click to expand...
Click to collapse
With S2U2 installed, I've been on calls ranging from 30 seconds to 20-25 minutes and I have never had any freezing issue. What version of S2U2 are you using? Maybe you could try the latest version posted here: http://forum.xda-developers.com/showthread.php?t=381588
I just got off of a 5:30 mins call and it didn't freeze so it could have just been a one time thing.
I thought I had the latest version but it looks like I don't. If I get another freeze, I'll install this version and see if there's a difference.
Anybody have any other ideas as to why the phone froze?
I really love the phone except i`ve got the same problem as i did with the Diamond 1. When I receive a message the sound doesn`t go and it doesn`t vibrate but the green LED does flash. The second I turn on the screen using the standby-key it vibrates AND I can hear the ringtone. It drives me crazy. I didn`t have this problem the first couple of days I had the phone. I haven`t installed anything on the phone yet. Are there more people that have this problem?
Maybe it's a problem with other software? Does this happen directly after a hard reset? Mine plays a sound upon receiving a message...
have the same problem. but do not know if this started when i changed the melody for the message to one that is on the memory card.
have not tried hard reset yet to see f it helps
Do not store ringtones on the memory card, when the phone goes into standby it turns off the SD card interface to save power. The same goes for any programs that you want to keep running in the background when the phone goes into standby.
i face the same problem.... likely is the ROM problem..
not only that bluetooth also have some problem...
Are you using any call blocking / filtering software? Just a thought as I had the same issue after installing Magicall.
The device is as clean as a whistle
I haven`t installed any 3rd party software of any kind. I believe it is a flaw in the software. Perhaps this will be fixed a the next rom-update.
I also have this problem now. Yesterday I got an important SMS, but did know about it until 30 min later when I clicked the standby-key. The wierd thing is that this does not happen all the time. Usually I get notified within a few minutes of a new message. I do not have my sound files on the storage card. Any ideas how to solve this?
I get this problem too, and its rather annoying.. you could try setting the phone to wake on SMS, however, depending on your lock settings, it will probably wake up unlocked even if it was locked. I like my phone to be locked at all times unless I unlock manually or I get a call ONLY.
The reg key is
HKLM\Drivers\BuiltIn\RIL\DisableSMSWakeUpEvent=0
Craig
Edit: if you go into Sound -> Notifications -> Messenging: New Text Message and ensure "Display Message On Screen" is unticked, it stays locked when a msg is received
i have this problem but with a hardreset solve my problem
Im having the same problem, ive got all the alert tones saved in the phone memory and have tried a hard reset too.
The reset improved things but still getting some messages being received without the alert sound being played, im assuming its a fault as several people are having the same trouble.
I got exactly the same
It seems that the problem only occures when you're not in the home screen. When i'm in the front (home) screen the sound works fine. But if i'm in the contact look (personalized look) its silent.
Can someone confirm this?
The same problem also with vibration....
It must be a softwareflaw, i can`t wait till HTC gives the first rom update...
Does somebody know how long it took before the first rom for the diamond 1 came available after its release?
I've only used Radio 3.44.25.27 from the new HTC Asia ROM for a day so I can't be sure, but the random problem of no audio/vibration alert that I used to face with Radio 3.43.25.19 seems to have gone away.
Having the same problem except mine plays the tone but doesnt vibrate!!!
Any news about this topic?
I had this problem also until I enabled SMS wakeup as per craiglay's post
These things should be fixed by HTC if u ask me. Workaround is great but I;ll wait till a hotfix is released
Whenever I receive a call when I'm already on a call, I never hear a beep or anything to indicate that a call is coming in. When I hang up, I see that I have a missed call. Once when I was looking at the screen, it showed an incoming call (call waiting), but no "beep" or anything...
Any ideas?
Did you ever fix this?
I'm having the same issue. Just wanted to know if you fixed it?
.
Never got it fixed...
same issue
Upgrading cyanogen constantly and finally downgraded for cyanogen3.4 to 3.3.8, cuz my phone was shutting itself off every 6 or so hours.. Now, it is running AMAZING... Just no BEEP for call waiting.. It isn't that big of an issue, but still would like it to work..
I think it is something that needs to be PUSHED into the phone and reseting the phone and taking battery out will not do it..
PLEASE HELP !!
Hate to dreg up a post from two months ago, but I'm having the same issue on my G1. I'm running soullife's Rogers 2.9.2, but have experienced this on other ROMs as well. Wiped, flashed, wiped again... nothing.
I've been scouring the forums to no avail. It's been reported a few times but I can't find a resolution.
Could it be something to do with stripped ringtones or notifications? I'll fiddle with them and see what I can find...
Any tips would be appreciated!
Ryan
Can someone help me how come every so often I place press call after entering a number there can be a delay of 5 to 30 seconds where nothing happens. Or of I push the name of a recent call it has the same delay. If I push it many times sometimes it will continue placing new calls while I'm already called. I'm running Sprint 2.1 official. Thanks
you probably don't have very good service where you are, unless you deny that statement.
Only hit it once and you'll only make one call.
Sprint's rom is ridiculously slow and laggy.
More peopel could probably help you out with specific problems with sprint's rom on sprintforums.com or somewhere like that. NOT that we don't want to help, but problems often have different levels of depth, if you know what I mean. Or root and get ever CRAZIER problems and then stick around here!
EDIT: that is, http://www.sprintusers.com/
rt1oo said:
you probably don't have very good service where you are, unless you deny that statement.
Only hit it once and you'll only make one call.
Sprint's rom is ridiculously slow and laggy.
More peopel could probably help you out with specific problems with sprint's rom on sprintforums.com or somewhere like that. NOT that we don't want to help, but problems often have different levels of depth, if you know what I mean. Or root and get ever CRAZIER problems and then stick around here!
EDIT: that is, http://www.sprintusers.com/
Click to expand...
Click to collapse
thanks, but i think its the phone, because now when I click the green button the phone comes up immediately but nothing on the screen works. Its almost like clicking an image no beeps nothing.
Below is more detail of my problem
Can someone help me. How come every so often I try to place a call their is a long delay.
For example I will push the green call button to bring up the phone. Then I will click on a name from my recently used numbers and I will click the number I want to call and it will highlight then nothing. After 10 to 15 seconds does it vibrate and place the call and go to the screen with the timer and the end button. If I get impatient and keep pressing the number (selection goes green for a second) nothing happens for 10 to 15 seconds then the call is placed and it will continue dialing, holding, and conference call as I try to talk to that person.
This delay also happens when I dial a number, and the number keypad is slightly sluggish when dialing.
Please note I a running Sprint Official OS2.1 and even though the Phone Application is sluggish outside phone mode the device seems to run when when using other internet. I am also getting strong bars and EV.
I would really appreciate your help; I just got this phone 2 days ago and really like it, but this one fault is killing it for me.
Please Help me.
Thanks
please somebody help me other than that i really like this phone.
integra144 said:
thanks, but i think its the phone, because now when I click the green button the phone comes up immediately but nothing on the screen works. Its almost like clicking an image no beeps nothing.
Below is more detail of my problem
Can someone help me. How come every so often I try to place a call their is a long delay.
For example I will push the green call button to bring up the phone. Then I will click on a name from my recently used numbers and I will click the number I want to call and it will highlight then nothing. After 10 to 15 seconds does it vibrate and place the call and go to the screen with the timer and the end button. If I get impatient and keep pressing the number (selection goes green for a second) nothing happens for 10 to 15 seconds then the call is placed and it will continue dialing, holding, and conference call as I try to talk to that person.
This delay also happens when I dial a number, and the number keypad is slightly sluggish when dialing.
Please note I a running Sprint Official OS2.1 and even though the Phone Application is sluggish outside phone mode the device seems to run when when using other internet. I am also getting strong bars and EV.
I would really appreciate your help; I just got this phone 2 days ago and really like it, but this one fault is killing it for me.
Please Help me.
Thanks
please somebody help me other than that i really like this phone.
Click to expand...
Click to collapse
Since you are not rooted and not running a custom ROM, this is probably not the best place to ask for help. You should call Sprint directly or check out the website/forum listed above.....
This lag is common on this particular phone. Just look at all the threads about dialer lag. 2.1 made the dialer lag even worse IMO. A custom ROM may or may not fix it for you.
i'm run Aloysius and Darchdroid I have the lag too. I dont know the problem i just wait.
i run DC and its laggy too... i bet its the dialer app...
that huge delay in actually dialing the number is an issue with all of the ROM's based on the official 2.1 (and the last leak as well I believe). No idea why it happens, but I hope a dev manages to figure out how to fix it soon, because it's the biggest annoyance for me
lag everywhere
i agree, the dialing lag is very annoying. also I have issues when im using the web browser while trying to tap on the url bar or in a search field the phone just hangs and doesn't bring up the keyboard.
while my buddie is already looking at a web page or search results on his very responsive palm pre webos im stuck waiting swearing at my phone lol.
But given all the things you can do to androids compaired to webos ill take the lag.
It was so bad for me that I took my phone into a sprint store and showed them how f'ed up it was. They said that it was happening a lot...evidently they have an internal forum where these issues get posted and the tech I talked to at the store said he saw a ton of posts referencing this same issue. They told me, however, that my phone passed diagnostics and that I could make and receive calls, to which I responded, "sure, I can make calls, but it barely functions as a phone." They sent me on my way, and I figured that was that until I got a text 2 days later saying that my replacement phone was in.
When I went to pick it up, the store rep said, "We'll have to reload the update for you" and I told him not to bother. Whatever issues 1.5 had, they were better than the enourmous issues with 2.1. Of course, as soon as I got it home, I rooted it (the 2.1 root came out the next day) and had 2.1 running quick as a fox anyway.
I have had the same issue, but have discovered one important thing by looking at the logs and just observing... This does not happen when using WiFi. I have a log showing that this problem is related to turning the radio off in order to make the call. For those who do not know, this is unique to CDMA in that it cannot use both data and voice at the same time. For some reason it is taking forever to turn data off in order to make the call. This has been reported to Flipz and he is looking into it, but until then I guess you just have to put up with it or go back to a 1.5 rom.
For those to say that the problem doesn't exist on rooted phones or that he should go somewhere else is not giving any good advise.
I have been rooted for several months and never really had any problems with an extremely long delay until recently. . I know if I am rebooting my phone I have to wait a little bit to do anything, even after Sense has finished loading or i will have the same problem. I'm sure you were not rebooting your phone when this happened.
Here was my experience 2 days ago...
I tried making a call and pressed on the contacts name. It was just sitting there. After 20 seconds it still wasn't calling, so I pressed the name again and after 15 more seconds it began calling the person. And then it started dialing again. I hit End Call and attempted to do it again. I had the same problem. I then rebooted my phone and waited 5 minutes and tried again and had the same results. In between pressing the contact and the phone actually calling it just sat on the contact screen. I have had the same ROM running on my phone for 3 weeks and this was the first problem I had like this.
At first I thought it was with Sprint, but it should have atleast gone to the calling screen and said dialing if it was even attempting to call.
If you have had this problem was it just stuck on the dialer/contact screen or was it on the screen that says dialing/calling?
It gets stuck on the dialer/contact screen. I had this problem slightly with 1.5, but it is far worse in 2.1 including all official 2.1-based roms. The problem is present in all 2.1 based versions of Fresh and Fresh Toast.
I had this problem on every 2.1 ROM. It went away with Fresh Toast and the 710 Kernel. Now the most lagg I get on the dialer is between 1 or 2 seconds. Before it could be 10 seconds before the call placed. I am extremely happy with that overclocked ROM. Try it out if you want.
Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840