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
Related
I've flashed my 8925 twice and hard reset it once, I've tried with and without having allowed the ATT customizations, and still there's a bunch of stupid little crap that is driving me nuts. Please note: these bugs are with no additional software installed.
Can't keep the backlight from timing out. I've always disliked the default of having the screen auto dim: if the screen is on I'm probably *looking* at it, otherwise I'd have turned it off... I've tried everything, setting no backlight time out, leaving it checked but matched to the screen shutoff, it shows the right thing in the control panel and stays on after I leave that screen, but usually within minutes or especially after I've used the phone it'll start dimming at 10 seconds again--even though turn off backlight is still unchecked in the backlight control panel.
Missed calls / call log badly broken: I'll get the missed call notification but when I try to see the caller it shows the log as empty, and when I go into the log manually from the phone app it also shows empty--doesn't even have my outgoing calls.
Voicemail notification got stuck on. I can probably call ATT and have them fix this on their end in minutes but it's bloody annoying that my phone's been notifying me of a long deleted voicemail message for days.
Anybody else having any of these problems?
Anybody know a fix for any of them?
I've already tried advanced_configuration, no great help there.
What's the latest/best cooked ROM? I like that the official has stuff like Voice Command and Sprite Backup, would like to keep them...
I haven't noticed any of those problems. I have however had problems with the phone being really sluggish at times. Still testing with no apps installed. I don't have the backlight problem. I have just used the settings in Kaiser Tweak and everything is working. Not sure that I will keep using it though. I will probably go back to Hyperdragon's newest ROM's. Those always seem to work really well for me.
No issues with the official AT&T ROM either.
wmg76 said:
I have however had problems with the phone being really sluggish at times.
Click to expand...
Click to collapse
Are you using the right SPL?
I did not try the rom. But I heard cleartype w/ landscape problem still exist w/ this rom (like the official HTC 6.1 rom). It could be fix by replacing the ddi.dll but will probably break Opera mini 9.5.
Problems??? Pull up a chair! First I installed the ROM and none of my would work. I couldn't connect to the internet. I downloaded the ROM again and reflashed it. This time icons started disappearing on my phone. I did a soft reset. Nothing. Did a hard reset. Nothing. I reflashed. Loaded my apps, they actually worked. I set up my email, and I could connect to the internet. Great! Finally! One hour later, I got a phone call, but my phone didn't ring. Huh?Anyway, answered it, when the other party spoken it came out the speakerphone. I checked my device and there was no sound: ringtones,music games,alarms. Soft reset...Startup sound played..loaded up and no sound. Call ATT for a help, they decided to send me a replacement. Bad device, I guess. So I redownloaded the ROM and tried a different phone( i know, i know), can't get email to work, can't get MMetrics work. I quit!I will be going to custom ROM! I have a lot of reading to do.
Been using the new AT&T Rom since it was released and not having any issues. The only minor problem I have is that I'm seeing some compatibility issues with the version of S2U2 that I am using. Otherwise, good to go.
I don't get how people are having problems with this. Everything works flawlessly with me.
Except threaded messaging sucks, but with Kaiser Tweak, I turned it off.
I have had only 3 major issues with this rom.
1: Camera works, but doesn't show anything on the screen. I have a black screen, press the capture button, and I get a picture, but I can't tell what I am looking at until I take the picture. Working on this issue now. [Update] I just installed HTC Camera v5.04 b29195.00 http://rapidshare.com/files/99227062/HTC_Camera_v5.04_b29195.00__PPC_.CAB . Works Perfect now!
2. Battery life was HORRID! After 10 minutes I was down to 90%, while it sat on the desk, screen off, nothing running. After switching from 1.65.21.18 to 1.65.21.14, life was peachy. 8 hours with normal usage and only down to 80%.
3. Blue Tooth drops erratically. I connected my bt headset to the phone, made a call, after 10 or 15 minutes, it dropped the headset. BT stayed turn on, but headset couldn't be found. Turned off headset, turned back on, magically found. Haven't figured out what is causing this, but am researching that as well. OK, So I got on HTC's website to see if there was an update. There is no update for BT for the Tilt WM6.1. However, there is a fix for TYTN II WM6.0. http://www.htc.com/europe/SupportDownload.aspx?p_id=13&cat=0&dl_id=60. I decided to try this fix, installed thinking I would get the whole "this program was built for a previous version" garbage, but I didn't get that. Anyway, I am going to try this tomorrow when I make my calls. I will update if I notice it fixes my issues.
Otherwise, it's fast, good signal, good sound quality, etc. Overall I am pretty happy. Will be happier when I finally get the BT to stop dropping, as I travel a lot and it's illegal to talk on the phone w/o a hands free on any military installation.... Sorry if I didn't answer any problems others are having on this actual forum, but maybe someone else will be having the same issue and see my posts for my fixes. Thanks!
zip, zero, nada.......UI is faster, apps are faster, threaded SMS is really nice to have, MSVC works as advertised with my JB2.
Different Alarm Sounds!!
I have a small WAV file that I use as an alarm sound but now can't get the sound listing in the alarm setup. I use to put it in application data/sounds. It now doesn't show up if I put it there or anywhere else (/windows, /my documents/my ringtones). Anyone else have this problem?
eltrebor said:
I have a small WAV file that I use as an alarm sound but now can't get the sound listing in the alarm setup. I use to put it in application data/sounds. It now doesn't show up if I put it there or anywhere else (/windows, /my documents/my ringtones). Anyone else have this problem?
Click to expand...
Click to collapse
All my WAV and MIDI files in the root of Windows show up fine. How small is the file? 600kb is the size limit for sounds on AT&T ROMs unless you modify the registry key that restricts it. 600k may be large for an mp3 file, but that's only mere seconds of a WAV file.
I upgraded as soon as it was available and am seriously considering going back to the old WM6.0 ROM, which worked well. I have had several lockups and had to soft-reset. I have also had problems with calls. Once, it rang and shoed me the call, but wouldn't let me pick it up. Other times I have had echos. GPS lock time is also much longer. Oh, yes, the equalizer in TCPMP creates terrible distortion. It worked great in 6.0. And I am using the recompiled version.
It is great to get results of satisfaction with the new ROM, but I personally would like to know, for those who have been having problems and those, answers to some questions:
1 Which SPL
2 Which radio
3 Activesync or POP for email
4 Bloatware installed or not
5 PIE or other browser
I am sure that there are others, but those are what come to mind for the moment.
No Problems Here
FWIW, I think my Tilt is running much better with the new ROM. I've only had it (the new ROM) for a couple of days, but TT7 and Google Maps seem to run faster, and It seems to detect WIFI networks MUCH faster than with the old ROM. I'm a happy camper, at least for now.
I've noticed that its been alot slower and I don't like having a button devoted to the ringtone volume. The other HTC Tab I was using that was supposed to be an official use had Music allowing me to access Windows Media very easily now I can't. I also noticed my dialing pad is different and not the same as it was. I also don't like the threaded SMS on Windows Mobile it doesn't suit it. It makes it look very confusing and also I've noticed it has problems moving the screen upwards so that I can see what is being written in the space. Another thing I notice is randomly the HTC Home screen cuts itself off cutting off portions of the tab information. Its something to get used to but I don't see it happening cause I can't figure out what happened to some items on the phone like my GPS doesn't work, I am experiencing worse internet problems than before, Wifi dies frequently, and the dialer doesn't seem to work like it used to. Its a disappointment.
NotATreoFan said:
All my WAV and MIDI files in the root of Windows show up fine. How small is the file? 600kb is the size limit for sounds on AT&T ROMs unless you modify the registry key that restricts it. 600k may be large for an mp3 file, but that's only mere seconds of a WAV file.
Click to expand...
Click to collapse
Which key? I have been hunting... and no luck so far.
Backlight timeout linked to lock??
When I re-downloaded the software and re-flashed a *third* time things seemed to work better. The only thing I did differently was skip the 'setup a password' that last time I flashed.
The phone worked pretty well all weekend, and then this morning I finally put in owner info and set a pin password.
And I just noticed the backlight has started dimming after 10 seconds (or less) again. Restart didn't correct it, nor did changing the setting in advanced config so the screen doesn't dim for unlock screen.
For now I turned off lock and went into the backlight tab and it's stopped doing it. BLOODY ANNOYING. I've seen mention of the backlight timeout bug in other forums too...
Even while the phone was working well over the weekend I noticed that fairly often the first attempt to bring it out of standby flashes the screen on then it goes back off, comes on and stays on when I press power the second time.
I ran into the idiotic bug where text is white on white when in landscape mode, know I saw something about that being a cleartype bug or something and there being a fix, but why the hell would it be released like that?
Also, I can NOT get the 'message sent' notification to disable... does 'advanced config' not actually work?
Buggy is an understatement!
Having been unable to bear/ignore the bugs I reverted back to 6.0
Here's what I along with you guys have issues with.
1)Ringtones revert back to it's default tone whenever I open: Settings>Phone
2) Back-light reverts back to 10 seconds at random and often.
3) Google maps will not display letters when searching for places, but it'll invisibly type
4) Typical freezes on pages and things of that nature
5) Bloatware..
SeekerJBP said:
Which key? I have been hunting... and no luck so far.
Click to expand...
Click to collapse
I'll help you out here
Go into HKEY_CurrentUser --> ControlPanel --> Sounds --> FileSizeLimit ( it's a DWORD value)
Just delete the DWORD value, and bam, enjoy .
EDIT : wow, just realized this is my first post. I've been browsing the site since the Tilt came out, but I guess I've never found it necessary to post. haha!
TheCritic said:
Can't keep the backlight from timing out. I've always disliked the default of having the screen auto dim: if the screen is on I'm probably *looking* at it, otherwise I'd have turned it off... I've tried everything, setting no backlight time out, leaving it checked but matched to the screen shutoff, it shows the right thing in the control panel and stays on after I leave that screen, but usually within minutes or especially after I've used the phone it'll start dimming at 10 seconds again--even though turn off backlight is still unchecked in the backlight control panel.
Click to expand...
Click to collapse
I have the exact same problem with my 8925. My work buddy across the hall does not have this problem with his 8925. Running WM6.0 my screen has ALWAYS dimmed at boot, as well as after a call ended; his has never done so. Now, after we've both upgraded to WM6.1, I have all my same problems, as well as the additional 10 second auto dimming that I did not encounter with WM6.0, he still has none.
No matter what settings I change, no matter if connected to power, USB, or none, my screen dims after 10 seconds. I can get it to temporarily revert back to the setting of my choice, by going into the settings and then back out, but if I manually dim the phone, get a call, or pretty much anything, it defaults back to the automatic 10 second dimming. I'm so pissed off about this. S2U2 also automatically kicks in on every screen dim, so I can't use it while the dim prob is going on. Certainly someone within this HUGE base of geniuses has a definitive answer for this.
Lots of little bugs in this release.
Google maps doesn't like it.
Can't get TCPMP to work.
Gets sluggish.
MSVC doesn't notify.
Other things I can't think of now.
Pretty irritating to say the least.
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.
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.
My phone stopped vibrating on notifications and incoming calls for some reason. So did my brothers at the same time. It'll still vibrates on screen unlock and haptic feedback. I have my e-mail set to vibrate only, sometime it'll vibrate, but more often than not, it wont. But never for notifications or calls. And yes i checked all the settings i could. (That i know of)
It first started when we switched to aosp mod from cm 6.1. So I tried flashing back to cm6.1(jaybob version) hoping it would fix, but it didn't. Yes, I did all the full wipes and everything. I really don't wanna RUU to see if its the phone or just the roms. I mean, it happened to my brothers phone at the same time, that can't just be coincidence.
Has anyone else seen this? or know what iI can try before I RUU?
i downloaded an app called sound manager. its free on the market. in there i clicked menu, vibrate settings. i enabled all the vibrate settings. tested it, then deleted the app. that reenabled my vibrations for messages and calls.
MrDowntown12 said:
My phone stopped vibrating on notifications and incoming calls for some reason. So did my brothers at the same time. It'll still vibrates on screen unlock and haptic feedback. I have my e-mail set to vibrate only, sometime it'll vibrate, but more often than not, it wont. But never for notifications or calls. And yes i checked all the settings i could. (That i know of)
It first started when we switched to aosp mod from cm 6.1. So I tried flashing back to cm6.1(jaybob version) hoping it would fix, but it didn't. Yes, I did all the full wipes and everything. I really don't wanna RUU to see if its the phone or just the roms. I mean, it happened to my brothers phone at the same time, that can't just be coincidence.
Has anyone else seen this? or know what iI can try before I RUU?
Click to expand...
Click to collapse
on aospMOD go into sound settings and for vibrate make sure you have it set to something other than never
Tried both of those suggestions and neither worked. Vibrate was set to always already.
I don't understand cause haptic feedback works but the actual vibrating will not.
Sent from my HERO200 using XDA App
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.