Related
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?
So, long story short, I had a Nexus One, which I loved EXCEPT for the fact that my coverage was horrible, half my text messages didn't send, the battery life sucked, and the screen was getting burn in and had weird color saturation.
So I got an HD2.
And, coverage is great, in fact it's the only phone on any carrier that I have ever seen maintain a 3G signal in my dads house which is like in the forest lol. No dropped calls or unsent texts. Love the screen, love the music player, love Sense UI, etc. BUT...
No matter what I do, I seem to have the same problems...
1. Applications not opening. This happens most frequently with Opera. I've tried the stock ROM, the new 2.13 stock ROM, and ChuckyRom. And while for a day or two there are no problems, after a little bit I just randomly get error messages opening Opera (and some other programs) saying there isn't enough memory or a file is missing. Sometimes if I close everything in the task manager it will open but sometimes not. It always works again after a reset. It's REALLY frustrating. I don't really want to do crazy stuff with the phone, I just want everything to work. So any ideas how to fix this?
2. HTC Messaging. After a couple days, when I have a few contacts with 100+ messages, there is this AWFUL delay before I can type a response. Same as above, I tried a few different ROMs and after a couple days it's the same thing.
I know these seem like little things, but when I want to go to the browser and literally 2/3 of the times it just won't open without a reset, or when I go to reply to a message and it won't let me type for 30 seconds, it's just really annoying, all the time. So any ideas to fix this, whether it be different ROMs, or registry changes, or anything, please let me know.
Ugh I can't wait til someone ports Android or WP7 to this fantastic hardware lol.
i had the same problem that you were having until i used a custom rom. i figured everyone that was having lag is when using the htc messaging so i found a rom without it. its a pretty basic rom without the htc sense ui on there and that solved my problems. you should just try out different roms to see which one works best for you
Try using kumars latest ROM 2.0 with htc messaging disabled. No lag at all.
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
What is the fix for? I know on my phone sometimes I can't hear anything when making a call.
I run my own Rom and kernel on my phone so can you just supply the fixed files or tell what they are and I will pull from the zip
-------------------------------------
Sent via the XDA Tapatalk App
what audio loss?, I've tried every rom and havn't had this problem yet.. are you talking about the dreaded audio bug? I am famililar with that as im on a refurb now from that. pre root tho.
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
I had that problem big time with Ivan's Official but with JCase's Plain Jane I havent had the problem at all.
I have that issue with the cyanogen roms and ic3rom. But as far as I've noticed the zenEXP and damageR roms do not have this issue. At least for me anyway.
I'd really like to run cyanogenELB, but the loss of audio is a deal breaker.
Renocat said:
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
Click to expand...
Click to collapse
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
LiverpoolsNo9 said:
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
Click to expand...
Click to collapse
When i have had the issue before, going into to settings and resetting the rigntone worked. It would be set on default ringtone, not what I had assigned. I put it back to what i wanted and it would ring again. same thing with notifications
Can't Wait
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Using the rooted version of leak3 and also have the same problem with loss of audio. Reboot only way to resolve it.
-------------------------------------
Sent via the XDA Tapatalk App
Having the audio loss (go to make a call every once in a while and the phone is silent and I have to reboot) on Evil Eris 2.0.1. Also, the alarm sometimes does not go off.
Avalaunchmods said:
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
Click to expand...
Click to collapse
I know you say DO NOT CAUSE AUDIO LOSS, but it seems like a lot of people are letting you know about their audio loss.
Sorry, but I figure I will add to this since others are speaking about Evil Eris.
For me, I get the silent bug (meaning all audio stops working: email notification, text, volume, music, ringtone selector, alarm tone--<when SB happens and I am trying to select a ringtone or alarm tone I get a FC for HTC sound something another>>--)
I have had this with EE 2.0, 2.0.1, and 3.0. My wife however is still on 2.0.1 and has never had the silent bug issue.
Also, for me, I do not get the shutter sound in camera, meaning when you take a picture it makes that camera sound noise. This happens without the silent bug, just don't get sound.
On AF http://androidforums.com/htc-droid-eris/99973-found-what-causes-silence-lag.html this may or may not help you.
This seems to happen to me about every 24-26 hours.
And most importantly, THANK YOU for looking into this and trying to fix it!!!!!!!
edit: I wanted to clear up, I love Evil Eris! I mean no disrespect to this fantastic ROM or to Frame!!!
cabbie12 said:
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Click to expand...
Click to collapse
I'm have the same problem using Ivans official. Not sure but i think the problem starts when I'm using data and then receive a call. When I answer I hear nothing and when I try to call back I hear nothing. I just reboot to fix.
Just wanted to give an update.
I flashed Sushi last night http://forum.xda-developers.com/showthread.php?t=701544 and am still having the silent bug making me a strong believer that I have a hardware issue.
Somewhere I read someone is thinking it has to do with the proxy sensor. Today I had silence twice, that's 2 times in just a few hours, this has never happened before. Also, each time today happened within an hour of using the camera (and I still have no shutter sound with this ROM).
I failed to mention last night that I am on an old Radio 2.40.00.01.22
I am sorry if I sound like a post whore but I just want to give accurate observations.
Camera
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
cabbie12 said:
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
Click to expand...
Click to collapse
Yes, I am now thinking it has something to do with the camera. I just got the silent bug again, 3rd time today, this was after I used the camera this evening to test and see if the silent bug would happen. This time it took 90 minutes when before it seemed to happen within an hour.
I had identified the bug a while back, but no one took any interest.
http://forum.xda-developers.com/showthread.php?t=668693
I'm glad to see that more people are becoming aware of it. Hope someone finds a fix soon. The only ROM that I'm aware of that isn't having this issue is the original 1.5.
just asking
im not sure what this trouble everyone is having but im not having any problems besides mms needing the fix but other wize no other issues sound included
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
cabbie12 said:
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
Click to expand...
Click to collapse
im not sayin it aint happening just didnt know it was a wide spread thing thats all
I'm curious if anybody else had this problem...
I got my DesireZ a couple of weeks ago, with Android 2.2.1 Froyo factory installed. I played with it a lot, seetings-apps-tweaks and the works, but didn't get to the ringtones personalization part. 10-12 days ago, I updated to Android 2.3.3 Gingerbread. After that, I fiddled with it till I got to the soundsets, and I downloaded a few of them, maybe 5 or 6. And then the troubles began. I can't apply any soundset, other than the HTC Default one. I select another (Flute, for instance), I apply it and the phone either uses it for 5-10 minutes then simply reverts to the default one, or it simply lists QuietlyBrilliant.mp3 as the ringtone for every sound (ringtone, alarm, notification for sms and email and so on). Some of the times, it sets as ringtone the files from the chosen soundset, but it doesn't find the sound file, and obviously doesn't play it when needed. Or worse, it sets random files as ringtone for different notification. It's hard to describe it behaviour, since it's so erratic.
Also, I can't positively know if this is a result from updating to Gingerbread, because I didn't change anything sound-wise before the update...
So I ask you: does anybody else have this problem? Is this a known bug, and hence, resolvable? Or does only my handset suffer from this? I searched this forum and browsed the net a bit in pursue of this, but haven't had any success so far.
Hmm i did the manual update and have not had any problems, but then again i did a wipe and restore first then updated.
Hm, didn't think about that. I just updated... I just ordered a Wildfire S for my girlfriend, it should arrive tomorrow or the day after. It comes with built-in Gingerbread... I'm curious how it will behave about this. Small chance to suffer the same bug, though...
I'm running 4.4.4 on a Samsung Verizon S5 paired with a Moto 360 2nd Gen running 6.0.1.
My notifications seem to be very unreliable. The biggest pain is that I can't seem to find any pattern to what happening. Here's what might happen after any notification comes in:
Vibration on the watch, followed with NO notification showing on the watch display.
Vibration on the watch, followed by notification displayed as I would normally expect.
Vibration on the watch, followed by a displayed notification, but the display comes 4-6 seconds AFTER the vibration.
Vibration on the watch, followed by a display of the PREVIOUS notification, which then flips to the current notification after about 4-6 seconds.
As I said, it's really annoying because I just can't seem to pin down exactly what's causing the issue or any sort of pattern for when it works, when it sorta works, or when it fails totally. This happens with all notification types to varying degrees. GMail, Outlook, CloudMagic, Hangouts, SmartThings... to name the programs I regularly get notifications from.
The only non-standard thing I'm running on my watch would be WatchMaker Premium. I don't have any app launchers running on my watch.
I've tried uninstalling outlook (as someone in the Android Forums suggested). I've tried a factory reset on the watch. I've tried uninstalling, reinstalling Android Wear on the phone. I've tried re-syncing apps... Just not having any luck figure out what's going on.
Anyone else experience anything like this? Anyone have any suggestions/thoughts?
100% the same for me on my sw3. Sad that 1.4/6.0 doesn't fix it.
I've sent feedback via the app. There's also a couple threads about it on the official forum.
sirrelevant said:
100% the same for me on my sw3. Sad that 1.4/6.0 doesn't fix it.
I've sent feedback via the app. There's also a couple threads about it on the official forum.
Click to expand...
Click to collapse
I suppose it's comforting to know I'm not the only one experiencing this. What phone/os are you running?
I'm wondering if upgrading to a new version on my phone would help at all. An 'expert' in the official forum said it shouldn't make a difference, but at the same time it shouldn't be acting like it is, so I dunno.
Just really frustrating cause "glancable" notifications is one of the big pluses of a smartwatch and right now it just isn't working.
Another question: Which service are you using? I'm on Verizon. If you aren't that would eliminate service as an issue.
(Yes, I know that service shouldn't be an issue... but maybe whatever programs/radio/whatever Verizon pushes on the phone might somehow screw with things??)
FWIW, I flashed a new 5.0 rom last night. After lots of effort getting things back up and running (mostly), I'm getting proper notifications. Not sure why, but something in the process of flashing got things working again.
RedRamage said:
FWIW, I flashed a new 5.0 rom last night. After lots of effort getting things back up and running (mostly), I'm getting proper notifications. Not sure why, but something in the process of flashing got things working again.
Click to expand...
Click to collapse
Same issues with my Verizon S5 and 360. How did you downgrade the moto 360 from 6.0 to 5.0? I saw the forum about it but it wasn't clear.