[Q] Weird entry in call log. - Hero CDMA Q&A, Help & Troubleshooting

I was calling someone back earlier by going to the call log and when I was in the call log, I noticed something weird. There was an outgoing call to *0000000 as my last call which had lasted for 15 seconds. I know I wasn't touching my phone when the call was made because I was still hitting some golf balls at the range. I don't have the menu menu unlock enabled so it can't be butt dialing either. Anyone have any idea what this may be or what could have caused it?
I'm currently running herodeck 1.2t with minimal apps.

Ummm update your rom perhaps to 2.2 or 2.3? Didn't think anyone uses old roms anymore
®patience is a virtue©

herodeck is GB 2.3.4.
1.2u is out so I'll be upgrading to that when I have time as you need to do full wipes to update that particular ROM.

Hmmmm I'm not to sure then. Hopefully the upgrade will help you out then
®patience is a virtue©

Related

Delayed Notifications in Cooked ROMS..

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.

Lag on incoming calls

I got a little problem with my g1.
When my phone is in standby and i get an incoming call it lags like hell.
After a delay of about 5 sec. the screen wakes...
I experienced this problem a long time, but always thought it's a ROM problem. After i tried various ROMs, i realized i still have this bug.
i don't no exactly when this problem started, but I think it came with the first donut ROMs.
I also think that it's no spl problem since i got this delay with the stock spl and the danger spl.
Does anyone have the same problem or even know a fix?
Can confirm this. I have a delay of a few seconds between the first vibration, the ringtone and the screen turning on and displaying the incoming call screen.
Zappza said:
Can confirm this. I have a delay of a few seconds between the first vibration, the ringtone and the screen turning on and displaying the incoming call screen.
Click to expand...
Click to collapse
i have the same problem
I have 2 G1s and this happens to me occationaly. I only have a few apps on my phone but my wife has lots of icons and apps on hers. i notice i only get a delay once in a while but she has a delay all the time. last night i updated both a Eclair 2.1-V1.5 from CYM 4.2.13 so far 2.1 seems to be a little faster so we will see...
used to get this a lot
on CM. admittedly i had never done a full wipe from 4.1.99 onwards so it was getting pretty laggy by 4.2.12. i've noticed a huge improvement when running dwang 1.17 and even more so on super d 1.6.
this bug really sucks...i get it on every rom...sometimes i cant even answer the phone...
Does nobody know a soloution?
Flashed latest xROM Eclair by JAC. Under idle, the phone almost always rings after the caller hears the 1st "do do" and before the 2nd.
If the phone is being used, especially with heavy apps (e.g. browser), then it's another matter...

Slow to start dialing

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

Incoming call screen disappears - can't answer call!

Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant
Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?
Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>
hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...
well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)

HELP. all incoming calls go to speakerphone in CM7

i'm not completely sure, but i remember seeing an option on CM7 somewhere that said incoming calls to speakerphone. i turned it on, then i updated to 7.02, now i can't find that option anywhere, but it's still turned on. and ALL my incoming calls turn the speakerphone on without any way to stop it.
i've spent hours going through all 120 apps in my phone and in every single setting trying to find something to turn it off. I've even used titanium backup to try and wipe the settings and CM settings with no luck.
I don't mind this being a toggle on/off like the carmode app, but i can't have it always on. I have to ignore important calls now just because it takes 10 seconds for the phone to actually let me turn off the speaker.
so please, if anyone can help me here. i'm about ready to wipe the phone but i seriously don't want to waste and entire day doing that so someone please help.
I font remember ever seeing this option in my cyan 7. Interesting.
RogerPodacter said:
I font remember ever seeing this option in my cyan 7. Interesting.
Click to expand...
Click to collapse
Yeah I don't recall that settings.
maybe it wasn't and i'm just crazy, but i'm still having this issue, and i'm about to wipe my phone to fix it, so if anyone knows any other way i'd seriously appreciate it.
Maybe try to wipe Cyanogenmod Settings using Titanium Backup? If all else fails...instead of doing a full wipe...try the /system only wipe that tamasek has in the nightly forum somewhere...that way...your data and apps are still in tact...and can just flash a new nightly...then if it still doesn't work...I guess you already know what to do.
I can't believe it but this actually happened to me today. I hung up and had the caller call back and it went back to normal.
Did you ever get it fixed? I put the newest stable version on my EVO and I have the same issue all outgoing calls go right to speakerphone and all incoming go right to speakerphone..
Also I notice carmode starts up on it's own as well.. but turning it off incoming/outgoing calls will still right to the speakerphone

Categories

Resources