Related
Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....
Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.
hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..
screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)
bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?
screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.
Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.
I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.
Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates
Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.
I am about to download and install the new .48 ROM, but what excatly did they fix?
Are people sending and recieving all sms'es and calls now?
Are the buggy volume control fixed?
What about the big waiting time when launching the messenger app with people who have a long sms-history?
As far as i am aware absolutely no issues whatsoever have been "fixed".
This "new" ROM is simply the latest version being shipped in worldwide devices.
The weekly calendar issue seems to be fixed.
kasperknop said:
I am about to download and install the new .48 ROM, but what excatly did they fix?
Are people sending and recieving all sms'es and calls now?
Are the buggy volume control fixed?
What about the big waiting time when launching the messenger app with people who have a long sms-history?
Click to expand...
Click to collapse
I don't know what has been fixed and I can't comment on the problems you listed since I've never experienced them but I can tell you what works better for me:
1) the keyboard is much more accurate. I was reasonably happy with the keyboard on the last ROM but this one is much easier to use.
2) the proximity sensor now works every time I make or receive a call. This was a bit hit or miss for me with the last ROM and would fail more often than it worked.
3) Battery life seems much better. Again, I was pretty happy with this on the last ROM but it just seems to last a lot longer now. I had network issues today (nothing to do with the phone, it must have been a problem with 3 in London today because my 3G dongle was down as well) and was expecting my battery to die relatively quickly. However, despite this and the fact that I was playing with the phone more today (because of the new ROM) my battery is holding about 20% more than I would expect it to hold at this point in the day. I haven't bothered with the patch to turn off the data connection either so my phone should be doing more now.
I can't comment on much more. I experienced the new bug with the inbox and SenseUI but that was dealt with by locking the phone. I also had some trouble connecting to my Exchange server but that was dealt with with a couple of soft resets. Everything is generally going quite well.
kasperknop said:
I am about to download and install the new .48 ROM, but what excatly did they fix?
Are people sending and recieving all sms'es and calls now?
Are the buggy volume control fixed?
What about the big waiting time when launching the messenger app with people who have a long sms-history?
Click to expand...
Click to collapse
I have installed the new 1.48 rom today.
and I don't think they fixed anything. I still got a red blob on my pictures. And I still wait up to 45 seconds for replying sms. When the sms-history is long.!!!
I've installed it today as well (dutch version). A pity that you 've to reinstall all apps. No prob for me, as I'm still try to explore the phone.
Anyway connecting, installing etc everything was flawless, even the link with Exchange.
hmm,.. well,.. no issues so far
I've flashed the .48 over my belgian HD2 yesterday using the goldcard approach, I've got to say that I've yet to see any real improvement or bugfixes,...
The lockscreen acted up for a while but then mended itself automagicly and has been a good boy since.
Opera seems more responsive but that could very well be just me fooling myself.
Same goes for the keyboard, I caught myself noting 'hey, this seems a bit more sturdy than before'. This can all be attributed to perception, though
It works and the itch to be up to date has been scratched.. all in all I'd recommend it.
where do i get this rom, offical site please
Is this an official ROM?
Where can this be downloaded? How do you flash it?
Get the ROM from links in http://forum.xda-developers.com/showthread.php?t=592954
Just installed it and personally think the touch screen is more accurate
Eoinoc said:
Get the ROM from links in http://forum.xda-developers.com/showthread.php?t=592954
Just installed it and personally think the touch screen is more accurate
Click to expand...
Click to collapse
Think or know, is it night & day better mate?
Hi
Can anyone tell me if they have kept all the software that was on 1.43, for example, ms office.
If someone can tell us what they have removed or added, that would be great.
parv1 said:
Hi
Can anyone tell me if they have kept all the software that was on 1.43, for example, ms office.
If someone can tell us what they have removed or added, that would be great.
Click to expand...
Click to collapse
AFAIK they haven't added or removed any applications.
sunking101 said:
Think or know, is it night & day better mate?
Click to expand...
Click to collapse
I installed 1.48 last night and I think its night and day better than then old 1.43 rom.
Screen is less sensitive (which is good) because it makes the keyboard easier to use, less multiple key hits etc.. so you can actually type more accurately. I still get the odd moment where they keyboard appears to spaz out, but I think this is still down to accidentally breathing on the screen or looking at it in a funny way.. man that screen is so sensitive sometimes..
I also found that rotating and typing with both thumbs in landscape mode made for a very compelling typing experience because the keys are slightly larger and further apart which makes hitting multiple keys at the same time even harder to do.
Once you have used the device for a day or so (to build up its dictionary of words that you use alot) its becomes really very quick to rattle off very long texts.
Its still not quite perfect, but its a huge improvement over the previous rom.
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
What is the fix for? I know on my phone sometimes I can't hear anything when making a call.
I run my own Rom and kernel on my phone so can you just supply the fixed files or tell what they are and I will pull from the zip
-------------------------------------
Sent via the XDA Tapatalk App
what audio loss?, I've tried every rom and havn't had this problem yet.. are you talking about the dreaded audio bug? I am famililar with that as im on a refurb now from that. pre root tho.
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
I had that problem big time with Ivan's Official but with JCase's Plain Jane I havent had the problem at all.
I have that issue with the cyanogen roms and ic3rom. But as far as I've noticed the zenEXP and damageR roms do not have this issue. At least for me anyway.
I'd really like to run cyanogenELB, but the loss of audio is a deal breaker.
Renocat said:
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
Click to expand...
Click to collapse
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
LiverpoolsNo9 said:
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
Click to expand...
Click to collapse
When i have had the issue before, going into to settings and resetting the rigntone worked. It would be set on default ringtone, not what I had assigned. I put it back to what i wanted and it would ring again. same thing with notifications
Can't Wait
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Using the rooted version of leak3 and also have the same problem with loss of audio. Reboot only way to resolve it.
-------------------------------------
Sent via the XDA Tapatalk App
Having the audio loss (go to make a call every once in a while and the phone is silent and I have to reboot) on Evil Eris 2.0.1. Also, the alarm sometimes does not go off.
Avalaunchmods said:
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
Click to expand...
Click to collapse
I know you say DO NOT CAUSE AUDIO LOSS, but it seems like a lot of people are letting you know about their audio loss.
Sorry, but I figure I will add to this since others are speaking about Evil Eris.
For me, I get the silent bug (meaning all audio stops working: email notification, text, volume, music, ringtone selector, alarm tone--<when SB happens and I am trying to select a ringtone or alarm tone I get a FC for HTC sound something another>>--)
I have had this with EE 2.0, 2.0.1, and 3.0. My wife however is still on 2.0.1 and has never had the silent bug issue.
Also, for me, I do not get the shutter sound in camera, meaning when you take a picture it makes that camera sound noise. This happens without the silent bug, just don't get sound.
On AF http://androidforums.com/htc-droid-eris/99973-found-what-causes-silence-lag.html this may or may not help you.
This seems to happen to me about every 24-26 hours.
And most importantly, THANK YOU for looking into this and trying to fix it!!!!!!!
edit: I wanted to clear up, I love Evil Eris! I mean no disrespect to this fantastic ROM or to Frame!!!
cabbie12 said:
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Click to expand...
Click to collapse
I'm have the same problem using Ivans official. Not sure but i think the problem starts when I'm using data and then receive a call. When I answer I hear nothing and when I try to call back I hear nothing. I just reboot to fix.
Just wanted to give an update.
I flashed Sushi last night http://forum.xda-developers.com/showthread.php?t=701544 and am still having the silent bug making me a strong believer that I have a hardware issue.
Somewhere I read someone is thinking it has to do with the proxy sensor. Today I had silence twice, that's 2 times in just a few hours, this has never happened before. Also, each time today happened within an hour of using the camera (and I still have no shutter sound with this ROM).
I failed to mention last night that I am on an old Radio 2.40.00.01.22
I am sorry if I sound like a post whore but I just want to give accurate observations.
Camera
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
cabbie12 said:
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
Click to expand...
Click to collapse
Yes, I am now thinking it has something to do with the camera. I just got the silent bug again, 3rd time today, this was after I used the camera this evening to test and see if the silent bug would happen. This time it took 90 minutes when before it seemed to happen within an hour.
I had identified the bug a while back, but no one took any interest.
http://forum.xda-developers.com/showthread.php?t=668693
I'm glad to see that more people are becoming aware of it. Hope someone finds a fix soon. The only ROM that I'm aware of that isn't having this issue is the original 1.5.
just asking
im not sure what this trouble everyone is having but im not having any problems besides mms needing the fix but other wize no other issues sound included
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
cabbie12 said:
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
Click to expand...
Click to collapse
im not sayin it aint happening just didnt know it was a wide spread thing thats all
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
I had that happening to my old phone.... freezing, buzzing, battery pull.
It started happening after I overclocked the phone to 1.5ghz . And then just kept happening even when i stopped overclocking. The phone would be hot on the bottom. And sometimes wouldnt boot till it cooled off. All i can say is hopefully you have insurance bc if its anything like with mine it'll be happening more and more often with time. After 3 months of it, it was happening a couple times a day , till i got a replacement.
Visentinel said:
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
Click to expand...
Click to collapse
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
ph03n!x said:
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
Click to expand...
Click to collapse
None of the above and I don't use Bluetooth.
Guess it ain't a coincidence. I wouldn't of posted if I thought it was part of the no sound bug.
Sent from my Nexus One using Tapatalk
I had a similar issue some time ago: for me the problem was the cpu/governor settings and i fix it with an appropriate SetCPU profile. Using another rom though.
Try to set an "in call" profile as the phone won'to go under 400 Mhz (roughly) and see if it happen again.
mi too
i using miu rom, HD2 NDT GINGER and recovery 3.0.2.4 with this i don have this problem. with any sense rom I have that problem
Sorry my bad english