So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
Related
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Hmm...if it were me I'd definitely start with uninstalling that video driver and see if that changes the behavior.
Also, are you using the stock lockscreen or do you have CHT lockscreen enabled via CHTE? If you do have CHT's enabled, then next you might want to switch it off and see if it helps.
I don't know for sure that either of those will resolve that, but that's where I'd start troubleshooting.
After your new rom finished flashing, did you perform a manual hard reset (as recommended by most chefs)?
I've found that there is more chance of the rom being unstable if you dont.
(flashes dont always take first time, no clue why, but i'd estimate about 1 in 10 flashes just isn't stable, yet the next flash with the same rom is stable, , , I've also noted similar results when installing an OS on my PC, , , sometimes it just doesnt wanna take properly.)
theidealone said:
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Click to expand...
Click to collapse
I read somewhere that the "unleaked official ROM" caused more problems than it was worth. I got the 2.13 ROM on the leaked version before it was made official and it has been working great since. I read that they made more changes and then made it official and that it was causing phones to be bricked and most phones ended up worse than they where before the the upgrade. The only "negative" thing i experienced was the screen sensitivity but it appears that the cab featured in the sticky at the top of the post fixed that!? Kinda strange If all else fails Factory Reset and try again. I always like to take a baseline reading. When my phone began acting screwy I would restore and run it stock for a few days to see if problems persisted...then after about three or four days slowly begin installing things...
Thanks for the responses! I will start with sirphunkee's suggestions. As I was typing, I started thinking the Driver Patch was a good possibility. Also, I have noticed that the phone doesnt just "sleep" the screen when I put the phone to my face, it locks. Im assuming this is something to do with CHTE's lock, because as sirphunkee mentioned, I am using the CHTE lock, instead of the stock.
Im going to start there, and see what happens.
Also, I did NOT do a manual hard reset. How would I go about doing so (yes, Im a HUGE noob. More of a car guy)? Im hoping I wont need to do this, as Im assuming I will need to restore all of my contacts, reorganize them, and reset everything else, as if the phone were new out of the box... Correct? But in case that is necessary, how do I do so?
As far as the leaked or official version... I couldnt find it on T-Mobile's site. I read a thread here, where it had been there then removed, due to people having issues with the download. I then was searching Swype or something, same forum, and found another thread, where someone had a link to the download through T-Mobile. Kinda hard to explain, but I will see if I can find the link, and the thread.
Thanks again guys! I really appreciate it. And thanks for taking it easy on me.
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
theidealone said:
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
Click to expand...
Click to collapse
Thanks for the effort though, you'll be able to put up links after just a few more posts (it's listed in the forum rules...hint, hint). Also, toreone already threw up a new thread in this section with that link for everybody, so don't sweat that
EDIT: oops, missed the rest of your questions there. The hard-reset is exactly what you said...resets the phone to factory-fresh condition. Yes, contacts will have to be reapplied, but sorting really shouldn't be an issue depending on your method of backing up and restoring them. I highly recommend using the built-in Microsoft Myphone utility for that (and it's wise to let it back them up regularly too, just in case, I just have mine set to do it each night while it's charging).
You can perform a hard-reset a couple of ways:
1. on your settings tab, hit "menu", then "all settings", then "system". You'll find an icon in there titled "clear storage". Run that, use 1234 as the code, and it will do its deed.
2. with the phone powered off, hold both the vol up and down buttons at the same time, and then press the end/power button to turn it back on, then it will take you into the same hard-reset process as the first method.
Hi everyone. I wanna tell you about something weird happening to my HD2 lately that’s really pissing me off. Every once in a while, when I wake up my device from standby or for instance after receiving a text, I’m not able to unlock my phone!! I try to move the slider all the way to the left or right, but the screen is totally unresponsive. It’s like my fingers aren’t touching the display at all.
I therefore turn the screen off and on again several times and eventually I happen to “resume” the screen sensitivity and reach the homepage. The phone is not frozen since it works fine when unlocked, just the screen.
Even more weird is the fact that if I remove the battery and restart the device, when I get to the PIN Code screen I’m still not able to enter any digit since the screen is still unresponsive and I have to do the whole display off/on routine several other times till it gets sensitive again. This problem is starting to happen more and more frequently and with several ROMs.
At first I thought it was rom related so I switched from “Miri v17.4” to “Energy June,11” and then to “HyperROM Ultimate v12”. Nothing, nada, zip. The problem still remains. Then I tried running Miri v17.5 with no extra apps installed, like BSB or CHT or whatever because I know sometimes programs can have incompatibilities with roms so I tried to keep it as stock as possible, but that didn’t solve the situation either.
I performed a “task 29 by doloop” between each flashing and tried many radios as well (2.10.50.28_2, 2.10.50.26, 2.11.50.20 and now I’m on 2.12.50.02_2).
I’m really desperate because I don’t know what’s causing this. Any help/advice is greatly appreciated!
Sorry for the long post, I tried to describe this issue as accurately as possible.
Thanks.
Many people are having this problem. Many topics about it too, but no final solution.
In my case two things seemed to help: adjusting light settings (turn off automatic adjustment) and taking out SD card and putting it back in, and/or change the SD card to a faster one.
I even reflashed my phone and the problem persisted until I was finally able to put back a stable backup.
First off thanks for your reply. I just checked and automatic backlight adjustment is on. Are you saying this problem might however be ROM related? Some time ago when I was using MIRI v16 this problem occurred just a couple of times and I didn't give it too much attention. I was wondering if the touchscreen might be faulty and therefore in need of assistance..
I don't think it's ROM related, well at least not in my case. I didn't have any problems using stock ROM and an 8 GB card, until I bought a 16 GB card (the exact same day the problem occured for the first time, I just didn't realize it could have something to do with the card, until I read this forum and found my own post about the screen not being responsive dated May 3rd, the day I started using the card ).
I installed Cookie's Home Tab 1.8.5 (on my card) and the screen became unresponsive again and I had a lot of problems uninstalling it, because of that screen problem. So I did a hard reset and the problem still persisted, couldn't even use the wizard because the screen wouldn't respond.
I think it's a combination of hardware and software problems. Hardware meaning SD card and software meaning power settings (automatic light adjustment), maybe the way the software is written to the SD card, I don't know.
I've got it working now, but I'm a little afraid to do any more tweaks and I would very much like to use the light adjustment settings.
So I'm still testing and maybe some day I'll buy a new SD card class > 4. The 4GB card, class 6 seemed to help the last time I hard reset my phone.
Yeah I get your point but still I wonder why has this issue just happened to show recently. With the older ROMs everything was working fine and none of the above ever occurred.
That leads me to 2 conclusions:
1. Newer ROMs (mixed updated packages from different sources) are less compatible with the phone and thus create a new series of problems, mine included (just take a look at some of the latest rom changelogs to see for yourself what I mean). All of this not to mention the extra complications that programs such as CHT have caused..
2. The screen has became faulty. Maybe in the earlier phases the problem just happens occasionally and becomes more and more existent as the touchscreen module “degrades” (or something like that..)
Just yesterday I turned my phone on and the screen was unresponsive (I’m running miri v17.5). I tried removing the SD Card and disabling the auto backlight adjustment but none of these helped.
Anyway, here’s what I’m gonna do in the next days:
I’ll flash MIRI v16 which is a ROM I don’t remember having this particular problem with and I’ll see how it goes. Should the unresponsiveness occur again, I’ll go with a stock ROM (the one the phone came with).
If both of these tests fail then I’ll send it in for repair.
It goes without saying that I’m all ears for any advice/help you guys can give.
Thanks.
http://www.youtube.com/watch?v=VHy_t-DHqq8&feature=related
I did... It's working now...
I am not sure if this has to do with using Android or not, but sometimes my HD2 decides to reboot itself unexpectedly, on WM as well as on Android and I can't really find what's causing it.
But what happens is, after switching itself off, it switches itself on again and hangs on the HTC logo, sometimes with or without the following info:
R 2.10.50.28_2
G 15.40.50.07U
D 1.66.76641
I am using stock ROM that came with it, i assumed it will be stable by itself but it reboots itself randomly sometimes just like on Android.
Does it have to do with the Radio version (i changed it from 2.07.xx). I tried 2.12.xx before and had same problems.
I should note that the only way for it to run again is to remove the battery for a while and then put it back. If i remove it and put it back briefly it will still hang.
Anyone is familiar with this strange behavior?
Thanks
ME too
I have the EXACT same problem. It only started for me after using android. now whenever i run Android it will unexpectedly reboot and sometimes hang like yours. It also does it in WM though not as often. I was able to notice it might have something to do with data connections bc if i run android but only use wifi it seems to be fine. I tried changing Radios WM ROMs and Android builds i even hardspled my phone again but nothing solved it. The problem needs to be talked about more. it got so bad for me I bought a Desire and gave up on my HD2 for the moment. Keep this thread up.
sounds like i have to follow
I hope not!
I notice if i do heavy download on wm or android i get it. But it could be that the phone is too hot? But it's not alarmingly hot tbh.
I hope more people can shed light on this.
Thanks for your input.
Yeah this is what seems to happen to me too, i start a downlogsd it gets a bit warm then freezes or reboots and gets stuck. However it doesnt even have to be a large download for me, a simple cab file or youtube video sometimes. And as far as heat, this never used to be a problem and i know for a fact my phone used to heat up way more before without a problem.
Maybe the qualcomm chipset go in "safe mode"..i remember that for first start tickle the orange led and after the device freeze or restart..maybe your device overheat. Try to touch cover's device or install a battery status monitor software. If you have changed radio, return on the original status. In case the restart happen always, make a backup using Pimbackup, and do an Hard Reset. For first try to use the telephone without the memory card and test the stabilty. If is all ok, you have to provide to format your SD card in Fat32. Try also to change the HSPL with the original SPL.
What happened to this thread? Suddenly 3 recent posts have disappeared?
relic said:
What happened to this thread? Suddenly 3 recent posts have disappeared?
Click to expand...
Click to collapse
Forums Restored from Backups - LOST DATA - PLEASE READ
As many of you may have heard, we underwent routine maintenance on our Database Server. Upon rebooting the Database Server, it refused to boot and all indications are that the RAID 10 (what is RAID? http://en.wikipedia.org/wiki/RAID) array failed.
We have restored the Forums from a 24 hour old backup. We know this is not ideal, but at this point, the chances of recovering the failed array are slim.
We sincerely apologize for this. In fact, this maintenance was intended to boost the redundancy of our database setup and lightening strike.
http://forum.xda-developers.com/showthread.php?t=792013
__________________
svetius
-----
User Experience Admin
xda-developers
http://forum.xda-developers.com/announcement.php?f=743
Thabks. Back to the subject, today i tried downloading on wifi a 150mb file on android and it rebooted byitself.
Then i tried to play a wmv video file on WM stock ROM and after 6 min it rebooted.
So its starting to look more and more like cpu/heat problem, anyone having these issues?
So does anyone think this might have something to do with all the overclocking in those android builds we've been using?
After 45 mins of install HD2 still hanging?
Hi, I just installed FroyoSense by darkstone
Release date: 07.AUG.2010
I don't know if this is the latest (probably not) but after 45 minutes of install the screen has in the top left hand corner tiny small text (excuse my lack of knowledge here) but no scrolling text as I expected, its now like 50 minutes, how long should it take?
Any help please would be appreciated, thanks
John
New to the HD2
So, I just bought a used HD2 a week ago. It was having similar problems in WM. I took it to a local store, and they said that is just how WM phones are. I've flashed HSPL and different radios and ROMs, installed Android, but still have trouble with freezing and rebooting on it's own no matter what I do. IT happens the same in WM or Android. Is there any way to find out if these might be due to hardware problems caused by the previous owner?
I got the same problem, when I do a lot of things on the same time on the HD2 it hangs or reboot. During de restart of the phone it hangs on the White screen with HTC on it. I have te take the battery out of it en than reboot again.
When I listen music and Internet the same time it almost always happends.
It happends on WM but also on Android, I tryed different ROM's and Radio Version's but nothing worked. Also tryed to work without SD-card, but still the same problem.
So I have no idea how to solve the problem...
I hope someone now's how to solve it...
Sorry for my bad English but I hope it's clear
FroyoStone with HTC Sense V2
Polar bear said:
Hi, I just installed FroyoSense by darkstone
Release date: 07.AUG.2010
I don't know if this is the latest (probably not) but after 45 minutes of install the screen has in the top left hand corner tiny small text (excuse my lack of knowledge here) but no scrolling text as I expected, its now like 50 minutes, how long should it take?
Any help please would be appreciated, thanks
John
Click to expand...
Click to collapse
Ok having waited for 2 hrs, I shutdown and installed FroyoStone v2, this time the tiny text appeared and faded after about 5 -10 seconds and the screen has gone blank, is this normal? No scrolling text, nothing, I going tpo re-boot and will keep you updated. Thx
If you read the previous posts you would know this thread has nothing to do with the problem youre describing. I understand the confusion of the title but pls read the thread first.
Polar bear said:
Ok having waited for 2 hrs, I shutdown and installed FroyoStone v2, this time the tiny text appeared and faded after about 5 -10 seconds and the screen has gone blank, is this normal? No scrolling text, nothing, I going tpo re-boot and will keep you updated. Thx
Click to expand...
Click to collapse
Your problem is unrelated to this thread.
So far we have more and more people having the related issue on WM and Android. We need some expert to help us pinpoint the problem.
jasperbleumink said:
I got the same problem, when I do a lot of things on the same time on the HD2 it hangs or reboot. During de restart of the phone it hangs on the White screen with HTC on it. I have te take the battery out of it en than reboot again.
When I listen music and Internet the same time it almost always happends.
It happends on WM but also on Android, I tryed different ROM's and Radio Version's but nothing worked. Also tryed to work without SD-card, but still the same problem.
So I have no idea how to solve the problem...
I hope someone now's how to solve it...
Sorry for my bad English but I hope it's clear
Click to expand...
Click to collapse
i have the same issues.
I can add also playing videos for longerthan 5-10min would make the phone reboot too weither its WM or android.
Today I was in the Store where I bought mine HTC HD2, because I was sick off it. They told me that is was a familiar problem with the HTC HD2. They also would repair it free for me. I didn't do it yet because first I have to delete my HSPL etc.
I asked them also what the would repair to solve te problem, he told me: the will do a complete bodyswap. So everything will be renewed, exept the tochscreen and front.
So I guess it is a real and serious hardware problem....
Why we dont hear people conplaining about it if its comon?
I find that very odd.
Someone could try PMing one of the devs in the forum and linking them to this thread to see if they could shed some insight or at least bring more attention to the issue.
Well I live in the Netherlands and on the Dutch HTC HD2 forum, I heard some people complaining about it. But the salesman of the store said that it is a familiar problem, so that sounds to me like a regular problem. But indeed it's weird we doesn't hear more people complaining.
Maybe the most of the people think is normal with WM, but I am really sick of it...
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.
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Okay, An update
This is happening when I reboot the device.
Is there something in settings that I am missing, or is there a registry setting I can change?
do you have your "date & time" settings set automatically?
Yes
bleui said:
do you have your "date & time" settings set automatically?
Click to expand...
Click to collapse
Yes time setting is automatic, even tried setting it in the registry.
It got that bad yesterday my phone reset itself to Jan 1980.
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
h0ng said:
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
Click to expand...
Click to collapse
Truth is no matter what is causing this... TWO big issues for me when choosing a phone software set up.
The phone knows what freakin time and date itis
The phone nor the software on should destroy batteries
but thanks guys it really was fun to play with.
Don't use automatic, mine does the same if I set to automatic.
I thought it was something with Giffgaff as I would set automatic and the time would be right but later on during the day it would be some crazy time and date.
Set to manual and your clock will be fine
dunno about any of that but, i do know that if i boot in to MAGLDR is gets buggered up, doesnt matter if the time is manually set or auto set, it always buggers up, dont boot to it and all is good
, at least for me anyway
I'm having the same issues. Time and sometimes dates getting screwed up. Only started happening to me about a couple of weeks ago now. But it's frustrating at the least. I've switched mine to manual setting at the moment. Gonna see how it goes over the next week.
One thing though, it isn't happening to my wife's HD2. She is using the older version of WP7, I'm currently on Yuki's more recent NODO version...
as per my post above yours if you use magldr or even the bootloader it gets messed up, so dual booting droid may be a reason, or using bootloader / magldr to charge, other than that i dont have this issue
Not got dual-boot on my phone, neither do U boot to magldr to charge... But it's happening to my phone every few days so far. Today it was out by 28mins. I want to see if having it on manual time/date does any better...
i also have a problem with my hd2,
9 times out of 10 when i reboot the phone the time and date will be wrong with no pattern i can spot (started to do this out of the blue- no updates or new roms).
im currently running with a cooked win mo image and android on the sd card.
battery still has a respectable life although seems to run out quicker than it once did so i may purchase a new one. (the old one is just over 12 months old)
also my phone has started to freeze on pin request after receiving a text so im gonna try a new image too
if anyone else has seen problems like these and solved them drop a noobie a helping hand pleeeeaaasseeee....
It's not HD2 related
The same issue happens to me (phone jump approximately 36 hours foward randomly)
The phone was a LG Optimus 7 on official rom but never managed to fix this issue (automatic date or not)
ForgetfulGuru said:
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Click to expand...
Click to collapse
I have the same issue! It happened some months after flashing xboxmods v. 1.11 Rom. It can't be a battery problem because I use 3 different batterys ^^