Related
Hello,
I've been having a problem with a few of the custom builds (Timor, AthineOS, CellPro Evo), and one problem I've noticed with each of the ones I've used is that when I get a text it doesn't notify until I wake the screen back up. Once I do that it vibrates and rings, but its up 30min after I got the text. Is this a known problem with a fix or am I better off sticking with a stock ROM?
Thank You
Funny you mention this, because I'm having the same problem. I thought it may have been a tweak I'd done and was going to do a hard reset today.
The only cab I've installed is Microsoft MyPhone. And had to edit the reg to allow the changing of the notification light timing in the Sounds & Notifications settings.
Do you know if this happens before you've made any changes to settings or installed any software on the phone? I don't recall having any problems like that myself with Timor installed, but I'm also not sure I received a text in that time. I haven't tried the other ROMs you listed.
It seemed to happen after I edited the reg settings.
Doesn't seem to be a constant occurance though. I happened to me 12 hours ago, even after a soft reset. But now I just sent a test message to myself, and all is ok... weird
Well I've regularly installed My Phone, Marketplace, Bing, Groovefish, and MP3 Trimmer, but I'd rather not delete and hard reset everything to do a test if someone knows a fix
I haven't had this issue...I am using the Valkrie Firestorm 5 and even when my phone is sleeping my phone vibrates as I get SMS messages and emails...
Well I have hard reset and held off installing using the My Phone. Everything seems well with recieving on time...but now the screen turns on everytime i get a message. It didn't used to do that and I find it quite annoying..I looked around my settings and Advanced Config and couldn't find anything.
It happens in the stock HTC rom too.
It normally doesn't happen if you come out of the text messages and go back to the home screen after you reply to someone. It's a really annoying bug
Me too...
I thought it was the result of all the hacking, tweaking and breaking I've been doing on this flash since I've been using it as a "scratch pad" but the problem you are all describing sounds identical.
I will also second the Home screen suggestion. Hit 'End' after you are done messing with the phone to go back to the Home screen. There is definitely a notification bug related to not alarming/vibrating when not on Home screen.
Though I have observed this issue, this does not completely explain my problems. Sometimes I don't actually even receive the SMS or MMS until the next day or after rebooting my phone! Most of the time it's fine though. I'm going to do a clean flash and see if that gets rid of that issue.
Same Here
I have run across the same problem with a number of the cooked ROMs. I never really noticed the problem with the stock ROM though. In my experience some of the cooked ROMs are having a problem handling the text messaging. I have over 3000 text msgs in my backup and as soon as I try to view an older text, the systems tend to lag and freeze up to the point that I need to soft-reset. Im using Athine right now and so far it has handled the text msging just fine without freeze or lag, but it also seems to have the same notification delay bug that the other ROMs have.
dwarf said:
It happens in the stock HTC rom too.
It normally doesn't happen if you come out of the text messages and go back to the home screen after you reply to someone. It's a really annoying bug
Click to expand...
Click to collapse
Yeah I'm familiar with that bug. But I go back to the home screen 99% of the time then shut the screen. I'll get a message and the LED will start blinking, but only when I turn the screen back on will it ring and vibrate.
Same problem here with the cell pro rom
ftmoe said:
Hello,
I've been having a problem with a few of the custom builds (Timor, AthineOS, CellPro Evo), and one problem I've noticed with each of the ones I've used is that when I get a text it doesn't notify until I wake the screen back up. Once I do that it vibrates and rings, but its up 30min after I got the text. Is this a known problem with a fix or am I better off sticking with a stock ROM?
Thank You
Click to expand...
Click to collapse
I have the problem with almost all of the ROM. Does anyone know if it could be a result of not using the right radio?
I could be wrong.. but I don't think it has anything to do with the radio. There doesn't seem to be any problem is receiving the message from the carrier, it's more-so the OS not notifying. This has only happened to me since trying the new WM 6.5.5 builds with Sense 2.5. Previous to these builds I have never had any issues, and only used EnergyROM with a COM2 build, and Sense 2.1
nackas said:
I could be wrong.. but I don't think it has anything to do with the radio. There doesn't seem to be any problem is receiving the message from the carrier, it's more-so the OS not notifying. This has only happened to me since trying the new WM 6.5.5 builds with Sense 2.5. Previous to these builds I have never had any issues, and only used EnergyROM with a COM2 build, and Sense 2.1
Click to expand...
Click to collapse
Im not sure about all the technical stuff your talking about...I just know that on almost every ROM I flash, when the phone goes to sleep, they seem to not do anything. Its only when I wake it up do I receive text messages, notifications and the weather doesnt update on its own in the prescribed time its supposed to according to the settings I have selected.
The radio version may affect the quality of your reception. So if you have no reception then that will obviously delay texts getting through, and stop you being able to get to the weather servers. But I can't see why it should have anything to do with delayed notification of texts that are already on your phone.
I realise this might not help you much, but on my EnergyROM (see my signature for full details), my phone gets texts fine when it's asleep.
The weather isn't designed to get automatically updated when your phone is asleep though. There was a recent thread on how to change the registry to make it do so, if you haven't done that then your weather stuff may well be acting correctly.
steviewevie said:
The radio version may affect the quality of your reception. So if you have no reception then that will obviously delay texts getting through, and stop you being able to get to the weather servers. But I can't see why it should have anything to do with delayed notification of texts that are already on your phone.
I realise this might not help you much, but on my EnergyROM (see my signature for full details), my phone gets texts fine when it's asleep.
The weather isn't designed to get automatically updated when your phone is asleep though. There was a recent thread on how to change the registry to make it do so, if you haven't done that then your weather stuff may well be acting correctly.
Click to expand...
Click to collapse
Awesome...thank you so much for the information and help
This is the thread about getting weather to update automatically - http://forum.xda-developers.com/showthread.php?t=585373
WHY DONT YOU JUST USE A ENERGYROM????? I dont have any issues with those roms and i just updated to the .88 radio. no issues as of yet.
Logcat
Randomly I get to the point where i can't answer calls. I just am unable to slide the answer or reject sliders. I know the screens working during this time cause if I hit the home button I still get the haptic feedback. Finally got a log cat of the event. Happens with increasing frequency. After I reboot it starts working again. Please if anyone has an Idea please let me know.
CM 5.0.4.1
are you using the arctu 7 screen auto rotating launcher? I started noticing similar behavior when using this launcher and having pandora running when call comes in. I cant answer it either.
Gr8gorilla said:
are you using the arctu 7 screen auto rotating launcher? I started noticing similar behavior when using this launcher and having pandora running when call comes in. I cant answer it either.
Click to expand...
Click to collapse
Nope. Not a big fan of auto rotation.
Same issue with stock, and CyanogenMod Opt3.
Once happened 3 times in a row to me. Have to reboot to fix it.
Lock/Unlock does not help.
Thank you so much thought I was alone. Nice to know someone else is having the same problem. If we could just consistently reproduce it I'm sure we can get this fixed.
Next time it happens get a logcat and post it to Cyans paste bin, however if you are not using his rom i.e. you are using optimized or baked goods or something that has been altered from his original build he will tell you to contact whoever altered it.
This just started happening to me, too.
I can reboot to solve the problem, and after a random amount of time i will be unable to answer any calls until i reboot the phone. Im thinking a service is crashing?
after the call has missed, i am able to slide to unlock and use the phone like normal.
Cyanogen 5.0.5.3-N1
Does anybody know why my hero might be a bit slow at dialing? When I touch a number in my contacts, it takes up to 30 seconds before it starts connecting the call. Sometimes its instant, sometimes its a long time. If I press it twice, it'll try to three way call the person later.
What causes this, and how do I fix it?
I have this problem too as does my hubby's phone.
We have tried damagecontrol and fresh roms and it happens on both of them.
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
would LOVE an answer to how to fix this!
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
gapoochi said:
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
Click to expand...
Click to collapse
I get the same problem as well. Usually its fixed by turning wifi on then off, or turning gps off then on respectively.
danaff37 said:
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
Click to expand...
Click to collapse
I get this problem without even using the dialer though. E.g. going into people, touching a contact, then touching the phone number to call it. The phone just does nothing for a little bit then suddenly it initiates the call. Would changing the dialer still fix this problem?
not entirely sure... possibly, I think it still has to load the dialer app when you do that. Best I could say is just try it. If it doesn't, and you want the old dialer, just pull it from the original zip you flashed and adb push to system/app to replace the one I posted. But that dialer works much better, in my opinion
Mine does this too and has on the stock ROM as well as every version of damagecontrol since 2.06. Sometimes it will dial right away and other times it will wait 10-20 seconds, then turn the screen off and immdiately back on and then dial and other times it just waits however long it wants to start dialing.
I know when I was still on stock and not rooted it would sometimes go into a state where it wouldn't respond to any commands that would make it dial but every other function seemed to be fine. I don't believe that's happened since I rooted and ROM'd it though.
I've used the stock dialer and well as SuperDial and Dialer One and all have had the problem. I've had this problem with haptic turned off/removed and still on. Sometimes waiting a few seconds after unlocking will help but not always.
So far for me, 100% fix has been the slide rom or darch droid (which finally booted for me today!). Both those, not one issue.
-------------------------------------
Sent via the XDA Tapatalk App
I noticed that with most roms that it takes 3 rings before my phone actually rings. I also noticed if I disconnect data it will ring much faster. I noticed the force 2g option but it does not seem to be working on warm donut. How can I keep the phone on 2g (is that 1x?) mode so that it still has some data but doesn't take so long for the phone to ring. Also maybe it would be possible to have the phone only go to 3g when it notices that it has been using a lot of data for a period of time then automatically drop back to 2g when the data usage falls that would be great. Thanks for everything.
have you tried running the phone prioritizer script? I used it on a few older builds and it made the phone respond much faster.. Some apps took a bit longer to respond, but you can tweak the priorities of different processes to get it running to your liking..
If you don't know where to find it, let me know and I'll throw up the APK. I know Incubus included it with a few of his recent Eclair builds.
_CriMson said:
have you tried running the phone prioritizer script? I used it on a few older builds and it made the phone respond much faster.. Some apps took a bit longer to respond, but you can tweak the priorities of different processes to get it running to your liking..
If you don't know where to find it, let me know and I'll throw up the APK. I know Incubus included it with a few of his recent Eclair builds.
Click to expand...
Click to collapse
You know if it works on Froyo?
If so, please upload it!
Thanks!
not sure, froyo is the only build I haven't tried it out on. Give it a whirl and let us know if it helps. Worst case, you can just uninstall it. I'm sure it will work though, it worked on every Eclair build I tried
Seems to install ok, haven't tested calls yet!
I was reading and I guess that I remembered it incorrectly. 1x does not allow calls to come through at all although it does save battery life. So I will try the script posted above and see if it helps on froyo. Thanks again.
bcti said:
I was reading and I guess that I remembered it incorrectly. 1x does not allow calls to come through at all although it does save battery life. So I will try the script posted above and see if it helps on froyo. Thanks again.
Click to expand...
Click to collapse
i always thought on cdma all of your calls come in on 1x, i know in windows mobile every time i got a text or call it would display 1x then after it go back to 3g
How do we use this? just install the apk?
xport said:
How do we use this? just install the apk?
Click to expand...
Click to collapse
install the apk and put the folder in the root of your sd card.
aa
nope.. no difference at all. am using myn's warm donut.
how about switching places between the vibrate and ringtone starting guys? would that be possible? because i have noticed that the vibrate starts up from the very first ring, though the ringtone starts around/after the 3rd ring only.
aa
thoughtlesskyle said:
i always thought on cdma all of your calls come in on 1x, i know in windows mobile every time i got a text or call it would display 1x then after it go back to 3g
Click to expand...
Click to collapse
When you are not on 3g mode and in 1x mode and you are using data your phone will ring busy. So it is good for battery life but unless you had a script that killed all data most of the time you would not be able to receive a call.
Hello!
I was pretty eager to install an NAND Android on my beatiful HD2, because WinMo really started to bug me, and I am still happy with my NexusHD2 Gingerbread ROM by tytung.
For homescreen customization I bought ADW.Launcher EX and ADW.Notifier out of the Market. Everything works mostly fine, my one problem right now is that:
When I receave a incomming text or mail ADW shows that little (ugly) red circle. Alongside of that, my Hardwarebuttons begins to pulse/flash. (Together with the green LED) that would be okay, If they would stop - but they don't even when i read a mail/text they keep pulsing and it seems that it stayes that way until I reboot.
As far as i can see that only happens when the phone is locked (and the screen is off), but I am not sure.
Any idea what could cause that? Do you need more information?
Anyway, thanks for your help,
laerador
It's a known issue with Gingerbread builds.
You need to make a phone call to stop it. You can ring a fake number (I used to just dial 0 when I was using Gingerbread), and just hang up, but that stops it... till the next time!
johncmolyneux said:
It's a known issue with Gingerbread builds.
You need to make a phone call to stop it. You can ring a fake number (I used to just dial 0 when I was using Gingerbread), and just hang up, but that stops it... till the next time!
Click to expand...
Click to collapse
Thank you! Just checked it, and it worked!
laerador
laerador said:
Thank you! Just checked it, and it worked!
laerador
Click to expand...
Click to collapse
Glad to help mate