Related
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.
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?
Hi. I've had these problems with my htc hd2, I've had the sms probs, but that got fixed after talking to you guys And now when people call me, or I call other people it freezes, im able to stop the conversation (which doesn't actually start), reset the machine (red button on the back or pull-out-battery) and then call back... This is really annoying, it has happened twice today, one time yesterday, and one time every day before.. I don't call people or receive alot of calls, but always the first call "****s up". Then its ok for the next call. Doesn't happen to anything else (yet), only calling. It's not that big of a problem, but my bills are keeping to get longer seeing that I have to call back all the time. :/
Jnygaard
I think the information you are providing is just a bit to little. you have explained your problem but you are not telling what radio and rom you are using.
in general have you tried a hard reset? or is the problem also there with your sd card in the phone? people have problems with phone freezes because of sd cards. especially the larger cards.
Oh yeah, sorry, I'm abit new to this.
Rom: 1.66.409.1 (NOR)
OS: 5.2.21869
Radio: 2.06.51.07
I always use a SD-card which is the standard 2gb which came with the phone, i could go some days without, and see if it works. Unless you have any other ideas?
Haven't tried a hard reset, doesn't that mean I'd have to upgrade it again?
I suffered from this last week & almost tested the bounciness of the phone I got so annoyed with it. As you'll see from my postcount I am an absolute noob but...I removed a couple of custom taskbars I had installed & bizzarrely everything returne to normal. probably a complete coincidence which I'm sure the experts here will confirm
Clever.. But "Custom taskbars" what did you mean by that, I'm more of a noob than you ;b
Hi, the taskbar is the info' strip display at the top of the phone. The standard one is a "clunky" black & white design. I installed some fancy, coloured ones which I now know should only be installed on HD2s with winmo6.5."whatever number it's at now" installed. Mine is a stock 1.66 ROM with winmo 6.5 device. Like I said the two may be completely unconnected but - touch wood(Ooh err missus), I've not had a call freeze since uninstalling them. I can't believe I've been outnoobed either lol! Best of luck...
Oh, yeah I've got the stock "black 'n white chunky" one :/ so there must be something else
I'll keep an eye on this thread for updates, of course I tempted sodding fate & the bloody thing locked up on me about half an hour after posting my reply. Cover off & soft reset & we're off again but this is soooooooooooo annoying when it does happen. best of luck to you.
Dunno if this is alowed, but Bump? (bring up my post )
Jnygaard said:
Oh yeah, sorry, I'm abit new to this.
Rom: 1.66.409.1 (NOR)
OS: 5.2.21869
Radio: 2.06.51.07
I always use a SD-card which is the standard 2gb which came with the phone, i could go some days without, and see if it works. Unless you have any other ideas?
Haven't tried a hard reset, doesn't that mean I'd have to upgrade it again?
Click to expand...
Click to collapse
what upgrades are you talking about? if you've installed any apps or customisations then you'll have to reinstall those after a hard reset, but otherwise it will just blow away all your info and give you a clean slate to start from with whatever ROM/Radio combo you have. definitely worth doing if you haven't done that yet.
otherwise maybe try upgrading the radio? or another ROM if that doesn't work...
Jnygaard said:
Hi. I've had these problems with my htc hd2, I've had the sms probs, but that got fixed after talking to you guys And now when people call me, or I call other people it freezes, im able to stop the conversation (which doesn't actually start), reset the machine (red button on the back or pull-out-battery) and then call back... This is really annoying, it has happened twice today, one time yesterday, and one time every day before.. I don't call people or receive alot of calls, but always the first call "****s up". Then its ok for the next call. Doesn't happen to anything else (yet), only calling. It's not that big of a problem, but my bills are keeping to get longer seeing that I have to call back all the time. :/
Click to expand...
Click to collapse
Try flashing to one of the latest Radios.
I had this problem when I was on a very old Radio 2.04 with the latest custom Roms.
Well, I have the latest rom, and thats the only rom I can get :S and isn't the radio upgraded with the rom ? if not, where do I upgrade the radio ? (radio: 2.06.51.07)
radios are in one of the stickies in the ROM forum
http://forum.xda-developers.com/showthread.php?t=611787
if you want info on how to flash it then read thru the relevant stickies
Finally understood and downloaded/flashed a new radio (2.08), after hours of reading and decrypting "nerd language" (no offence of course). We'll see if it helped tomorrow, if I have no probs tomorrow it *might* have been fixed!
TMOUS user here. Have had the HD2 for a total of 5 days. Making phone calls, it freezes repeatedly. I will receive a phone call(feel it vibrate, try to answer, and it just locks. Can still hit the Home button and hit HD2SoftReset, but this really sucks.
R:2.08.50.08?2
G 15.34.50.07U
D 2.10.82076 8G
Hopefully that's the radio info you need. It is a stock TMOUS rom. Installed a handful of Apps, and loaded up some music on my microSD card. Any suggestions?
This may be an interesting symptom... It came of my in-car radioset's broken. I have to listen to traffic news while driving using my HD2's FMRadio. I found exactly everytime after I got off my car, the very first incoming call or dialing call will result in no sound from the phone following by a crash of the system, and I have to soft-reset to get it back to work.
After several weeks of testing I think I have found this Must-Crash-Steps for HD2. The key point is that everytime before I got off my car, I pull out the earphone without manually exiting the FMRadio.
Firstly, I made these tests all under the latest official ROMs, which include:
RUU_Leo_hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
RUU_Leo_hTC_Asia_TW_1.66.709.3_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
RUU_Leo_HKCSL_CHT_1.72.832.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
and, all tests were made right after a Hard-Reset, no default settings were changed and no 3rd-party apps were installed.
Here comes the Must-Crash-Steps: (in number order)
1, plug in the earphone, run FMRadio, when there's a radio-station broadcasting, switch the sound to device loudspeaker by pressing the "device-soundwave" icon on the screen.
2, leave the device alone until screen turn off automatically (yes, screen off, not just dim out. So far, the radio broadcast still can be heard from device loudspeaker), then, without pressing any button or touching the screen, pull the earphone out, the radio broadcast will shut off immediately.
3, as before, leave the device alone for about 1 minute, don't do anything, just wait.
4, now the Judgement-Time comes, pick up your phone, turn on the screen, unlock, make a call to anybody (toll-free number is recommended, when line connection establish, no sound can be heard. By now, the phone screen seems hangs, even if you press End Call, the calling icon on the top-bar is still on.
(notice: you can replace this 4th step by calling your HD2 from another phone)
5, Press the Home button, you may be able to toggle to Manila home page, but at this time, (1)you can't go back to Phone page (2)after some operations on Manilla screen (play music, for example), the whole system halts: no response neither touching the screen nor pressing the buttons.
Anybody interested can give it a test and please post your test result here along with what ROM you're using.
Finally, forgive my half-cooked English......
Very insteresting.
A lot of people has said that FM Radio was related to some freezes and slowliness of the HD2.
Maybe thos guys from HTC that wander around here from time to time can see your thread and do something about it.
You should email HTC support detailing the steps you have taken and ask them to officially investigate it...
Your English seems pretty good to me. I haven't tested this anomaly, but it doesn't surprise me. I've tried several "official" and cooked roms and all have their limitation/crashes, but this seems particularly strange.
Yes, I already did that and got below useless reply:
Dear huangyz，
Thank you for contacting HTC International.
We appreciate that you could report the information to us. We will help to forward to relvant department.
Thank you for your continuous support of our products and services. Should you require further assistance, please do not hesitate to contact us again.
We look forward to be of service to you again.
HTC
Hotline: 1800 238 7788
Service Hours: 8 am - 8 pm, Monday - Saturday (except Public Holidays)
customer name: huangyz
email: ......
country: China
inquiry:
I've found a bug in HD2 with the latest ROM version. Please see below link for more:
http://forum.xda-developers.com/showthread.php?t=650886
submit time: 2010/03/23 15:42
Ok, tried to make a phone call and indeed you cant hear anything, but it never froze.
I've been having trouble with the no ring in incoming call.
And I do pull out my headphones without closing FMRadio.
So is this the problem , how can I fix it ?
I did try it when I saw one similar post on a Chinese website. Luckily my mobile didn't freeze as expected. But HD2 does often crash, freeze unexpectedly. For me especially it freezes quite possible on two occasions: one is when you start you opera browser, the other is when you pick up to answer a coming call. But so far I haven't figured out what the root causes are. It is really annoying.
lepszy said:
Ok, tried to make a phone call and indeed you cant hear anything, but it never froze.
Click to expand...
Click to collapse
No frozen? How about pressing the Home button followed by pressing the Dial button, could you re-enter the Phone screen? Or, slide to Music Tab, try playing a song, see whether the screen freeze...
niulj said:
I did try it when I saw one similar post on a Chinese website. Luckily my mobile didn't freeze as expected. But HD2 does often crash, freeze unexpectedly. For me especially it freezes quite possible on two occasions: one is when you start you opera browser, the other is when you pick up to answer a coming call. But so far I haven't figured out what the root causes are. It is really annoying.
Click to expand...
Click to collapse
the similar post might be post by a similar human as me...
anyway, could you tell your ROM version please? or where can I download it for test.
Meiyo said:
I've been having trouble with the no ring in incoming call.
And I do pull out my headphones without closing FMRadio.
So is this the problem , how can I fix it ?
Click to expand...
Click to collapse
In my case, you can still have the phone ring when there is an incoming call, but right after you pick up the phone and slide to "Answer", silent at all.
Since it is under an official rom environment, the simple way to "fix it" is: everytime after you finish listening FMRadio, EXIT the app before you pull out the earphone )
huangyz said:
the similar post might be post by a similar human as me...
anyway, could you tell your ROM version please? or where can I download it for test.
Click to expand...
Click to collapse
yes I guess you are the one who posted the same problem in different forums.
My device information is:
OS version
5.2.21864(21864.5.0.81)
manila version
2.5.19202525.0
Rom version
1.43.405.1(70124) wwe
rom date
10/26/09
radio version
2.04.50.22_2
sorry i don't know where to download it, but i think you can find it very easily since it is an old rom version ( i got it last november and it could be the first batch of HD2s and i didn't flash any other roms.).
huangyz said:
This may be an interesting symptom... It came of my in-car radioset's broken. I have to listen to traffic news while driving using my HD2's FMRadio. I found exactly everytime after I got off my car, the very first incoming call or dialing call will result in no sound from the phone following by a crash of the system, and I have to soft-reset to get it back to work.
After several weeks of testing I think I have found this Must-Crash-Steps for HD2. The key point is that everytime before I got off my car, I pull out the earphone without manually exiting the FMRadio.
Firstly, I made these tests all under the latest official ROMs, which include:
RUU_Leo_hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
RUU_Leo_hTC_Asia_TW_1.66.709.3_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
RUU_Leo_HKCSL_CHT_1.72.832.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
and, all tests were made right after a Hard-Reset, no default settings were changed and no 3rd-party apps were installed.
Here comes the Must-Crash-Steps: (in number order)
1, plug in the earphone, run FMRadio, when there's a radio-station broadcasting, switch the sound to device loudspeaker by pressing the "device-soundwave" icon on the screen.
2, leave the device alone until screen turn off automatically (so far, the radio broadcast still can be heard from device loudspeaker), then, without pressing any button or touching the screen, pull the earphone out, the radio broadcast will shut off immediately.
3, as before, leave the device alone for about 1 minute, don't do anything, just wait.
4, now the Judgement-Time comes, pick up your phone, turn on the screen, unlock, make a call to anybody (toll-free number is recommended, when line connection establish, no sound can be heard. By now, the phone screen seems hangs, even if you press End Call, the calling icon on the top-bar is still on.
(notice: you can replace this 4th step by calling your HD2 from another phone)
5, Press the Home button, you may be able to toggle to Manila home page, but at this time, (1)you can't go back to Phone page (2)after some operations on Manilla screen (play music, for example), the whole system halts: no response neither touching the screen nor pressing the buttons.
Anybody interested can give it a test and please post your test result here along with what ROM you're using.
Finally, forgive my half-cooked English......
Click to expand...
Click to collapse
Wow, China Mobile. LOL
on to something not so completely different... I do have some problems that seem to appear when you take out the jack before closing the relevant app.
I use mortplayer in the car, and if I close the app before getting out of the car, and AFTER that I take out the jack, everything goes fine.
If instead I first take out the jack, as soon as I unlock the device to close mortplayer, all I see is windows media player opened for some weird reason on the playlist dialogue. I need to close that and access mortplayer to close it.
niulj said:
yes I guess you are the one who posted the same problem in different forums.
My device information is:
OS version
5.2.21864(21864.5.0.81)
manila version
2.5.19202525.0
Rom version
1.43.405.1(70124) wwe
rom date
10/26/09
radio version
2.04.50.22_2
sorry i don't know where to download it, but i think you can find it very easily since it is an old rom version ( i got it last november and it could be the first batch of HD2s and i didn't flash any other roms.).
Click to expand...
Click to collapse
Thanks a lot!
I find that ROM in this forum. I'll download it and give it a try...
ljwnow said:
Wow, China Mobile. LOL
Click to expand...
Click to collapse
are we the same?
ephestione said:
on to something not so completely different... I do have some problems that seem to appear when you take out the jack before closing the relevant app.
I use mortplayer in the car, and if I close the app before getting out of the car, and AFTER that I take out the jack, everything goes fine.
If instead I first take out the jack, as soon as I unlock the device to close mortplayer, all I see is windows media player opened for some weird reason on the playlist dialogue. I need to close that and access mortplayer to close it.
Click to expand...
Click to collapse
"quietly expensive", LOL
I think your (device's) symptom can explain something that the Jack I/O driver does mess up with other system resources as in my case.
huangyz said:
Thanks a lot!
I find that ROM in this forum. I'll download it and give it a try...
Click to expand...
Click to collapse
downloaded and flash the following rom:
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship.exe
go through all the steps EXACTLY, it comes out the same result: CRASH.
the only tiny difference is, while call is made and no sound, press "End Call", the phone screen will close and go back to Manila Home automatically. (notice that under 1.66 and other ROM, I can't even End a Call)
This looks fine but the system actually goes nuts: first, you can't go back to phone screen again; secondly, you can't play music in Manila's Music tab; and finally, no response of the whole system.
huangyz said:
downloaded and flash the following rom:
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship.exe
go through all the steps EXACTLY, it comes out the same result: CRASH.
the only tiny difference is, while call is made and no sound, press "End Call", the phone screen will close and go back to Manila Home automatically. (notice that under 1.66 and other ROM, I can't even End a Call)
This looks fine but the system actually goes nuts: first, you can't go back to phone screen again; secondly, you can't play music in Manila's Music tab; and finally, no response of the whole system.
Click to expand...
Click to collapse
Confirmed. I am not an exception. Following your must-crash technique, my mobile also died immediately. That it didn't happen in my previous test could be because I didn't follow your procedure right.
It is really interesting. Should let HTC know about this.
niulj said:
Confirmed. I am not an exception. Following your must-crash technique, my mobile also died immediately. That it didn't happen in my previous test could be because I didn't follow your procedure right.
It is really interesting. Should let HTC know about this.
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I did report this to HTC.
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.