Dialpad not responding to touch - G1 General

Hey all,
I just upgraded recently to JF V1.5 and I noticed that the onscreen dialpad does not respond to touch when a call is in process. I have to open the keyboard to input. Its annoying as hell.
I looked all through the settings to see if there was some option to enable/disable the screen during a call but I didnt see anything.
Is anyone else having this problem? Is it a known issue?

I too have had this problem. A reboot will generally fix it. Have you had any issues with calls coming in and Android core locking up?
In any case, I think that in at least in my case, the program "Owner" might be suspect. What do you have installed on yours? Perhaps we can compare and get this narrowed down.

Well the problem went away even without a reboot. It hasnt been consistent.
I havent had any lockups during calls though. The only apps I have installed are:
wifi tether
twidroid
last.fm
skype
where
pixelpipe
movie finder
jf updater
bank of america
beetag
thats pretty much it.

I'm getting the same issue. Of all those apps the only 2 I have are JF and Pixelpipe. I'll uninstall them and see.
It isn't consistently happening for me either but it is damn annoying when it does. I hope Magic users don't get it, without the keyboard you'd be stuffed.

Related

Can't pick up the phone! Anyone else?

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.

[CUPCAKE] Laggy Dialer and Other Issues

I installed ADP Cupcake around two weeks ago, and ever since that I've been noticing lag and unresponsiveness in the dialer. For example, if I'm at the Home screen and I type in "Travis" to call my friend Travis, it'll think I typed in "rvis" or something other than what I typed. This is very annoying and I'm wondering if there's any secondary app I could look to that is much faster and more responsive than the original dialer..?
Another problem I'm having is when I'm in Phone mode (calling someone), I'll often see a Force Close error. I think it mostly occurs when I press Hang Up. I don't know what the problem is exactly but is there any way to fix it?
I'm on JF ADP 1.51 with the Extra Volume hack and Apps on SD. Hopefully someone can tell me how to fix these problems :/

Anyone Notice these 2 Issues? - Sound + Market

It seems the system volume, which I always set to mute keeps going up by it self. I am not sure as to what is causing this.
Also, I don't know why they programmed it that way, or if it is a bug but in the market, if I rotate my screen, the list seems to go back to the top automatically. I would find my self way down in the list only to have to go back down again. I know I can turn off rotation but I like mine on. Good thing 2.2 has the option in the taskbar.
Hmm, either this is a very rare incident for a lot of you or maybe just maybe you guys are too zoned in on Froyo But yes, this problem irks me quite a bit.
My market has the same issue when switching between landscape and portrait. Never noticed it until now. I usually don't switch between views, so not much of an issue for me.
the market has always done that... always.. ever since day one... i hated it even back in 1.0

System Update 1.84.708.1 CL322105

First things first, HTC Desire Z, I am in New Zealand on the Vodafone network in case that makes a difference and running bog standard Sense UI with no mods or ROMs or anything like that.
I have done a search and can't find anything similar anywhere except some asian sites, and I suspect (but hope it isn't) because the phone came from Hong Kong.
Ok, last night an update came through to my phone with the above code, I have lodged a query with HTC but no response as yet and figured you guys may have a better/quicker fix.
Essentially since the update came through the phone has been very slow and glitchy... stalls on background screen before loading app buttons, widgets, menus everything.
So I guess I want to know A: is this a legit update or is it some sort of hack?
and B: can I revert somehow to the last/correct version or am I going to need to install a ROM and start from scratch?
I appreciate your help and if you need any more info just ask.
cheers
Tis legit. HTC seem to be rolling the update worldwide, but very slowly. My dad got it in the UK last Tuesday, I'm still waiting.
His phone seems to be ok. If you're still having problems, try hard reset?
Cheers dude, ok at least that is one less thing to worry about
might give a hard reset a go
I've heard that once you do a update its always good to do a factory reset its like a pc you'll need to give it a good cleaning some time LOL try that
Sent from my Desire HD using Tapatalk
Why does the Desire-Z keep getting updates and the G2 has only gotten 1 update?
hogg2500 said:
Why does the Desire-Z keep getting updates and the G2 has only gotten 1 update?
Click to expand...
Click to collapse
The canadian desire z is still at 1.34, afaik it hasn't had any updates at all
Sent from my HTC Vision using XDA Premium App
hogg2500 said:
Why does the Desire-Z keep getting updates and the G2 has only gotten 1 update?
Click to expand...
Click to collapse
You'll find that if its provided through a carrier, they'll handle the software updates after HTC issues them to ensure their "value added software" or "crap" is loaded on it.
Saying that, mine is a UK SIM free from HTC and I still haven't got the 1.8x.xxx.x update, I'm at 1.72
Heya, I also have the Desire Z, bought from Hong Kong, use on Vodafone, live in Wellington NZ, and also did the update this morning.
Haven't noticed my phone running any slower yet but keen to see the improvements touted though. So far just seen little UI cosmetic changes.
Be sure to go into accounts and redo your sync settings, it put stocks and weather back to real time sync on mine...turned them off straight away.
AHHHHH that could have something to do with the hanging issue. I did a hard reset and initially it seemed better but then once I had re-instated my backed up data, contacts etc, (especially after I shut off the HTC messaging app, and re-synched my google accounts for some reason) it started hanging again.
Maybe the stocks (which I have banished) is trying to sync in the background somewhere? *wanders off to see*
It is a good sign that it is working on other DZ's, main issue seems to be on keyboard open/close events... so might just be incompatiblility with an app I'm running... god I hope it isn't Handcent
Ok, update time, redone the sync settings, removed anything that has been added in the last week or so in case I just didn't notice (unlikely but ???) the hanging problem.
oefox are you using Handcent for your messaging or the standard messaging app? i have removed it and that seems to have made a slight improvement although only very slight... this is driving me mad... may have to try another hard reset tonight and rebuild the data only and start again with apps.
Fake edit: HTC got back to me "try soft reset, hard reset... sorry can't help as phone is HK build, we have passed your query to them... they will be in touch" We shall see?
Actual Edit: Also seems to be destroying battery life all of a sudden, and it seems to think it has been off the charger for 22 minutes... which is odd as it came off the car charger 5 hours ago... hmmm.. definite issues here... looks like an actual rebuild may have to happen :/
You could try an app like Watchdog Lite from the Android Market to see if there is a process gobbling up your CPU cycles? It may be the cause of what's slowing the phone and draining your battery...
Sent from my HTC Vision using XDA Premium App
Thanks for that, I have installed Watchdog Lite, removed a couple of apps that I thought might be a little bit problematic and I will stop playing with it for the day and how the battery reacts to "normal" use i.e. not constantly setting/resetting loading/unloading/deleting/syncing/unsyncing stuff lol... still seems to hang and whatnot though but we shall see.
If that doesn't help I will try a fresh hard reset and build from scratch (not from backup) and see if that helps :/
Call me uninspiring but I really like the default email and messaging. I have found after playing with it for a couple of days now that it will sometimes hang for a couple of seconds when returning to the home screen, shows the background but no icons for a few seconds.
On the plus side my wifi seems to have improved stability somewhat.
oefox said:
Call me uninspiring but I really like the default email and messaging. I have found after playing with it for a couple of days now that it will sometimes hang for a couple of seconds when returning to the home screen, shows the background but no icons for a few seconds.
On the plus side my wifi seems to have improved stability somewhat.
Click to expand...
Click to collapse
I did upgrade the firmware, but I didnt notice any improvement.
I mean everything is just fine
I thought that it would upgrade it to Gingerbread and Sense 3.0
I would be nice to have that version
Cheers
I have an HK Desire Z as well, and have experienced the exact same problem since the system update. I have not tried a hard reset because I'd rather not spend the time, but the home screen "blank and reload" issue is quite aggravating. I may have no other choice but to reset.
I will try waiting a couple days to see if somebody posts an easier fix.
Aha if you have a G2 wait till T-mobile gives it to us... we will be getting gingerbread
Sent from my HTC Vision using XDA Premium App
Ok, good to see it isn't just me, it is definitely an issue and the reset doesn't seem to help much so if you havn't already done it don't bother localhost21. however I think I have found the main culprit and it seems to be the Google Maps updates that are causing the majority of the hanging etc.
if you remove the updates, i.e. go back to the standard version that came on the phone and it seems to make quite a difference so try that.
Unfortunately as i use the navigation function on maps quite a bit I kinda need to keep it so a bit of a catch 22. If you don't really need it though that should solve most of the problem... if any other fixes arrive let me know
Hopefully vodafone NZ give us the Gingerbread upgrade, or google brings navigation out of beta because it really is very good.
Edit: Still hangs, I have become a habitual killer of tasks which is nearly as annoying as the hanging, esp. if you have to open the task manager after it has hung, and it seems the processes causing the hang won't stay dead (auto-killed etc) *goes hunting for basic, stable, rom*
I encountered a new problem in that my notification sounds seem to randomly choose what to play when I recieve sms/calls so I did a hard reset but I still have that issue.
It also still hangs on the home screen if the k/b is open so hard reset doesn't fix this problem so I want to try a new rom
Has anyone done a root/flash yet with a HK Z?
I have a HTC Desire Z on the 2Degrees Network. I'm running Android version 2.2.1 Build numner is 1.84.708.1 CL322105 can I get an upgrade? Vheers.
oefox said:
I encountered a new problem in that my notification sounds seem to randomly choose what to play when I recieve sms/calls so I did a hard reset but I still have that issue.
It also still hangs on the home screen if the k/b is open so hard reset doesn't fix this problem so I want to try a new rom
Has anyone done a root/flash yet with a HK Z?
Click to expand...
Click to collapse
What do you mean? I have HK DZ.
I rooted it. But I had to downgrade it to ROM 1.34.xx.
As I understand, there is no way atm to root from ROM 1.84.xx

Gingerbread issues

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.

Categories

Resources