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?
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
So, I'm on my second a500, first one seemed "off", bad battery life, random shutdowns, etc.
now, I understand some issues are fixed with the 1.141.07 update. I desparately run the system update check like a teenage girl waiting for a boy to call. But no dice.
Is there any way to legitimately get the update?
Seems like people were being updated last week and then nothing...... (crickets chirping).
I'm still not very impressed with my second unit. screen on/off thing drives me crazy. I dont think the battery should be draining when in standby. etc.
I know that nobody here works for Acer, so dont flame me. But if I can;t get a reliable android tab, I think I may run back and get an Ipad2 instead. I have had an ipad 1 since release, and I guess i'm spoiled to only needing to charge the thing once a week, and I use it heavily.
I really want a android tab though - I'm a big google person and love having all my stuff in sync and connected. But I dont like having to live next to the power outlet, or wonder when my unit is going to randomly restart. I'm sure there are others in the same boat.
My first one runs great, just bought a second one at Costco with the fabulous deal they have. I have no battery run down issues. Auto brightness, Wifi, and gps all on....except when in for sleep mode. I turn on Airplane mode on and off through a downloaded toggle widget.
I've been using it periodically for 3 days and haven't turned it off. Even started a new book with Kindle. Still have 55% battery.
I'd say you are running a bad app which is the culprit. I bet if you go back to stock reset you won't have the issues, other than sleep without airplane mode.
...and no, we are all waiting for the update or 3.1, whichever comes first. I need it for Exchange, everything else is pretty minor.
I guess I should have mentioned. my first unit, I did a factory reset and ran stock for a couple of days, and still had the same issues.
This new unit is pretty much stock, and only thing I have installed is Flash, Kindle, and File manager HD.I have it running in airplane mode, wifi set to turn off when the screen is off, and screen brightness at about 10%.
I charged it all night, I have used it maybe 3 times today (since 6am), just to browse a couple of sites, and @2:30 today the battery was already @ 40%. it has been in standby most of the day.
I find it hard to believe that 2 different units could perform so poorly.
I really want to love this product, but haivng a hard time doing so, lol
The thing you described should be fixed with the 3.1 update...be patient.
Sent from my HTC Desire using XDA App
BadGrim said:
So, I'm on my second a500, first one seemed "off", bad battery life, random shutdowns, etc.
now, I understand some issues are fixed with the 1.141.07 update. I desparately run the system update check like a teenage girl waiting for a boy to call. But no dice.
Is there any way to legitimately get the update?
Seems like people were being updated last week and then nothing...... (crickets chirping).
I'm still not very impressed with my second unit. screen on/off thing drives me crazy. I dont think the battery should be draining when in standby. etc.
I know that nobody here works for Acer, so dont flame me. But if I can;t get a reliable android tab, I think I may run back and get an Ipad2 instead. I have had an ipad 1 since release, and I guess i'm spoiled to only needing to charge the thing once a week, and I use it heavily.
I really want a android tab though - I'm a big google person and love having all my stuff in sync and connected. But I dont like having to live next to the power outlet, or wonder when my unit is going to randomly restart. I'm sure there are others in the same boat.
Click to expand...
Click to collapse
Make sure you register the device via the Acer registration widget in apps. This will get your s/n in the OTA database.....
bonzer2u said:
Make sure you register the device via the Acer registration widget in apps. This will get your s/n in the OTA database.....
Click to expand...
Click to collapse
I too am waiting for the .141.07 update. Seems I read that Acer had pulled the updates. Still check every day. I like my tablet and have not seen battery issues with very little standby drain.
The only issue I have is that the WiFi keeps disconnecting. I have checked the advanced settings and it is set at always connected and I have tried changing the channel on my router (suggested elsewhere) but once or twice an hour I have to bump the WiFi to get it to work.
bonzer2u said:
Make sure you register the device via the Acer registration widget in apps. This will get your s/n in the OTA database.....
Click to expand...
Click to collapse
yup, did that on both units.
so, I made it 12 hours today on a single charge. I only used it 3 times to browse the web for about 5 min (no flash), and I wrote an email and sent it.
Sorry, but that is ridiculous.
http://youtu.be/hE0NfL1C0-s
BadGrim said:
yup, did that on both units.
so, I made it 12 hours today on a single charge. I only used it 3 times to browse the web for about 5 min (no flash), and I wrote an email and sent it.
Sorry, but that is ridiculous.
no need to apologize, that plain suks......
call the support line, perhaps they can push it to your s/n....???
Click to expand...
Click to collapse
Mine has been fine, except for the GPS.
I have a build 1.112.01_EMEA_CUS7. A new tablet and it's registered from today so they probably update them by batches because there are no new updates.
EDIT: But it works brilliantly apart from the crashes when I've installed any app. I've fixed that but it would be nice to be bug free.
bpivk said:
I have a build 1.112.01_EMEA_CUS7. A new tablet and it's registered from today so they probably update them by batches because there are no new updates.
EDIT: But it works brilliantly apart from the crashes when I've installed any app. I've fixed that but it would be nice to be bug free.
Click to expand...
Click to collapse
You are lucky. There is a update from Acer here for your build. It will take you directly to 1.141.01.
You need to unzip it using this post and then move the extracted update.zip from the decoded.zip file to your external sdcard and then do the update key sequence (volume down and power pressed) and you're done
Thanks. I'm updating as I type this.
I just hope that it will update properly and that I won't have any problems with rooting and or bricking my device or any problems that I've already solved.
I come from Desire so I'm used to wiping my phone first so just updating is a new for me. I would also feel better if our bootloader would be unlocked.
EDIT: Updated OK. Root pending.
EDIT2: Rooted and disabled phone.apk
The phone now works perfectly and is updated.
bpivk said:
Thanks. I'm updating as I type this.
I just hope that it will update properly and that I won't have any problems with rooting and or bricking my device or any problems that I've already solved.
I come from Desire so I'm used to wiping my phone first so just updating is a new for me. I would also feel better if our bootloader would be unlocked.
Click to expand...
Click to collapse
This is an official update so it will either update or not if the checksums are wrong or it cannot binary patch a file. So no chance of a brick.
It works OK. The only thing I've noticed is the longer boot time.
The android screen takes a minute longer probably because it's building files.
I'll check logcat when I have the time and patience to mess with it some more.
I didn't know that the update would just fail. I was expecting a brick because I was reading some posts about people bricking their tablets. I guess I was wrong.
Feedback from Acer Support re Updates, Etc.
According to Acer tech support, there is no way to force the new firmware update or Honeycomb update to the Tab. You just have to be patient and wait for the Tab to update itself.
As we know, lots of people are complaining about the screen turning on/off/on/off by itself, resulting in battery drain. These complaints are well-publicized and easily found using search engines.
I first purchased a 16gb Iconia Tab. I called tech support about the flashing screen and reported it as an issue. After speaking with customer support, they emailed me a survey asking about my user experience with the Tab. I completed that survey and again noted the problem with the flashing screen and battery drain.
The new firmware update that was pushed to the device solved the flashing screen issue and improved battery life.
Then I bought a 32 gb Tab and experienced the same flashing screen/battery drain issue. I called tech support (to see if I could obtain the firmware update for the new Tab). Amazingly, tech support told me that they had never heard of this issue. I told them to search their knowledge base but they insisted this was the first time they heard about a problem with the screen.
I know that cannot be true because I called them twice about this very issue, and gave them feedback in their on-line survey.
Anyway, I expect that the screen problem will be resolved when the firmware update gets pushed to the device. Unfortunately, on my first 16gb TAB I got the firmware update the day after I opened the box. I'm still waiting for that update on the 32gb Tab after 10 days.
mandel4026 said:
As we know, lots of people are complaining about the screen turning on/off/on/off by itself, resulting in battery drain. These complaints are well-publicized and easily found using search engines.
Click to expand...
Click to collapse
I had this issue. It's because of the wifi. My screen would turn on and off randomly and it was because my wifi was on my place where it had bad reception. I turned it off and the screen didn't light up anymore.
I didn't test if it also occurs on the new firmware.
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.
My nexus 4 was bought about one month after it was released .
I didn't have this issue in the first three months ,but recently ,about in the past one month ,it occurred kind of frequently and randomly.
Here is the issue:
I lock the screen and leave it there without using .When I am ready to use it ,I cannot awaken the screen even after I press the power button several times, both short and long press ,as if my phone was powered off ,even though I know its power is still 50 percent or so. After a series of random press ,I give it a long press ,then it gets rebooting .
I have been searching on the internet and many Nexus 4 users have this issue ,however, nobody can tell exactly what causes this problem .Some say it is caused by snapdragon batteryguru and some say the battery is not firmly installed .
I don't know whether you guys have ever come across this issue ,what is your analysis about it and how you solve this boring problem...
Glad to see that I can find solutions here...
My nexus is running original android 4.2.2 and is not rooted.
sleep of death. long press (10-20 seconds) powers off/reboots the phone. can be caused by phones software, undervolting and apps.
i haven't got any issues like this, have you installed a rom? if you have try another rom, also remove battery guru as suggested
mlndshh said:
i haven't got any issues like this, have you installed a rom? if you have try another rom, also remove battery guru as suggested
Click to expand...
Click to collapse
mine is running original android 4.2.2 and I never installed other roms...
simms22 said:
sleep of death. long press (10-20 seconds) powers off/reboots the phone. can be caused by phones software, undervolting and apps.
Click to expand...
Click to collapse
Thanks
But it seems difficult to find out a proper solution ...
youngwuno1 said:
Thanks
But it seems difficult to find out a proper solution ...
Click to expand...
Click to collapse
if its an app, figure out which one it is.