So, when i lock my phone, and when i try to wake up to unlock, it is really really slow sometimes (up to 10-15 seconds even)..
Is there any way to prevent this ( to decrease that wake up time ) ?
p.s. My phone wm and android roms, radio and kernel is shown in my signature
Cheers ppl and thanks in advance,
Laynee
The 'smartass' scaling defaults to 245mhz when the screens off.... Disable the smartass, then bump the frequency up when the screens off !
Ok, first of all thanks for swift and fast response..
Second, from your reply, it seems like i have to install setCpu, and do that in it? What freq to put when screen is off? Because last time i got those profiles set up in setCpu ( before i uninstalled it), they didnt work..
And last, will it affect my battery drainage alot ?
p.s. One more question ( i know im annoying ) : I got really slow download speed when downloading from Market.. any cure ?
Huh, nor smartass nor underclocking in standby is respondible for slow wake up (well, maybe for a split second but definitely not the 10-15 seconds OP is talking about).
I haven't found any solution for this yet, but actually once you learn to only lock your phone when you know you won't be needing it the next 30 seconds, your problems are gone. (Unless you're using an old build/kernel, in that case you should just upgrade. New builds only lockup if you unlock shortly after locking.)
Slow market downloads is due to your sd card apparently. Either try with another one, or unmount SD card before starting the download.
i always find using the 'pick up' key wakes the phone in less then 3 secs everytime for me
I'm my experience wake lag is caused by corruption of the SD card. It happens more often when I try to use higher class cards than the stock one. What always fixes it for me is running checkdisk in windows. It usually finds errors and after it fixes them and I reboot I get no wake lag for a while. Errors happen a lot less often for me when I stick to stock sandisk class 2 card. Hope this works for you.
Sent from my HTC Desire using XDA App
I found this recently on Desire HD, it takes 3-5 seconds to wake up (not using setcpu)
I am using cedesmith desire hd2 (beta) rom with 2.14.50_2 radio and energy (13-nov) winmo.
Most desire builds are ok (less than 1 sec )
Hope to fix this ASAP
iDev
The most you can do is try another microSD card, but the reality is that this is device-dependent. You've just been unlucky to get an HD2 that is slow to wake up.
I know this because I had an HD2 before which took around 5-10 seconds to wake up all the time. After I broke it, my insurance company replaced it.
My new HD2 wakes up instantly almost always.
Well i forgot to mention one thing :
The slow wake up problem is not happening every time i try to unlock phone(its not that much often but when it happends im pissed off).
When it happends, buttons and screen are up, but screen is blank for 7-10 ( not 15 seconds i overreacted )..
So any help now ?
Laynee1 said:
Well i forgot to mention one thing :
The slow wake up problem is not happening every time i try to unlock phone(its not that much often but when it happends im pissed off).
When it happends, buttons and screen are up, but screen is blank for 7-10 ( not 15 seconds i overreacted )..
So any help now ?
Click to expand...
Click to collapse
hmmm my screen is only ever delayed by around 3 or 4 seconds e.g. when in the middle of installing software.
Only thing that might help is, as before, trying another microSD card or a different ROM/kernel.
The one I'm on is Mdeejay Clean Sense with hastarin 8.5.1. Try that and see if it's any better. If not, its either your microSD card or just your phone.
pkchips said:
hmmm my screen is only ever delayed by around 3 or 4 seconds e.g. when in the middle of installing software.
Only thing that might help is, as before, trying another microSD card or a different ROM/kernel.
The one I'm on is Mdeejay Clean Sense with hastarin 8.5.1. Try that and see if it's any better. If not, its either your microSD card or just your phone.
Click to expand...
Click to collapse
Thanks dude Ill try and see whats happening.. Tell me, in mdeejay clean sense rom, do u have those cool fold and flying animations when going back or closing smt?
Laynee1 said:
Thanks dude Ill try and see whats happening.. Tell me, in mdeejay clean sense rom, do u have those cool fold and flying animations when going back or closing smt?
Click to expand...
Click to collapse
Nope. It doesn't
try formating your sd card delete any partition keep the whole card FAT32 and use a RAM build my lag is so much better by doing this
Related
When i press the power button, there's a 0.5s delay before the screen turns on. Is this normal, or just with mine?
You flashed it with anything or running stock?
Sent from my GT-I9000 using XDA App
running JM2
Any custom kernels for lagfix / oc?
Sent from my GT-I9000 using XDA App
Nope, just flashed jm2, and rooted, nothing else.
Dunno then, might be normal. Its even worse with the lagfix kernel.
Sent from my GT-I9000 using XDA App
Hmm ok, thanks for you fast reply's!
OMG! are you guys for real!
this is >insert slur here<
a fraction of a second for the screen to turn on from off is normal on any phone device.
....
Don't label me with the same brush as the op. I was trying to ascertain if he had the startup lag from the custom kernel used for the lag fix with samset. I said it was probably normal - I refrained from calling him an impatient fussy so and so. Abuse him all you like, leave me out of it.
Sent from my GT-I9000 using XDA App
How is this normal on any device? as my touch diamond didn't have it, my ****ty nokia 5800 didn't have it, my htc artemis, htc tytn II, do i need to continue?
It's 0.5s-1.5s. But mostly 0.5s, that's why i said that.
If you don't have a solution, just don't post , i flashed jp3 to try it out, and the delay i've got from jm2 is gone. Hmmm, guess the delay wasn't normal after all.
Damn, i feel like i'm on a chatbox with 12-year old's.
And no, i don't mean Bynar010 to be clear.
Hello all.
This wake up lag is killing me, coz its 1.5s most of the time.
I did apply the lag fix kernel, and that was worse at times. So now i simply reflashed it (JM5 now) and removed the SD card.
Is there anything else I gotta to to remove this fix, or re-flashing removes it ok?
Thanks in advance
I am also having this problem. It can be anywhere from half to three seconds . I have just flashed to jm5 and applied the one click internal lag fix. Anyone know what I can do to fix this. Thanks in advance.
Same problem here on JM2 + 1 click lag fix. I previously use JM2 + memocan and not found this problem. Wondering why others with 1 click lag fix didn't realize this since it's very longer (mine's about 3 sec).
3 second is nothing...
just pressing the POST button to this took more than 3 sec
In that case not only this phone sux, but your internet connection isn't much better..
Please just reply if you can help us with this problem. I like the phone, but the power-on delay is just annoying. I use it instead of a watch too. Wouldn't you care if you had to look at least 3 seconds at your watch before you could see the time, EVERY time you looked?
As i said, this is just annoying, other phones i've owned didn't have a delay like this, not even the WM ones.
i don't know about you, but the last WM phone and PalmOS phone i've had took at least 1 sec to display
yes i use my phone as a watch as well, i don't carry a watch with me
Just to throw it out there, mine lags about 0.25 to 0.5 seconds on average. I'm on JM5 without root.
Do you mean lag when you press the power button to unlock your phone, or when you switch on your phone? It's of course normal during switching on the phone. But I also experience a lag when unlocking the phone (~1 second). It only happens when I haven't used the phone for 5 minutes or more. Doesn't happen if I lock it and immediately try to unlock it again. I believe it's the chipset waking up from sleep or something.
@ AllGamer:
The ones i had: HTC: S100, Artemis, Kaiser, Touch Diamond.
They all went on faster. I didn't have the problem at first (with stock firmware), guess it started after my first flash (to jm2), but the problem stays when i flash back to the stock firmware, that's the strange part..
@ ssj4Gogeta1:
I mean the delay when you press the power (or home) button when the phone is already powered on, and it happens everytime, even when i press the power button, wait 5 seconds, and press it again. Nowdays, it's at least 1.5s every time.
Lol, would be great if i meant the power-on time.
the thing is, all phones i've had, will go slower and slower the more apps i install into them
the same applies to SGS.
to keep them fast, i always only install apps that i'm really going to use.
i used to clam every single piece of software i can put my hands on into the phone before, that always lags the phone to death.... although so far the SGS is holding quite well
still testing out a lot of software, but once i'm done i'm going to stream line it with only the stuff i want in it.
Regarding the delay with the Home button, that is not the same as Power button.
See now we understand you better, it does takes a split second after you wake up the phone with the home button.
however anything longer than 1 sec is not quite right, if you have that sort of lag, try optimizing the phone.
recent firmware updates like JH1 or JH2 depending where you are, have made vast improvement on performance
in the worse case scenario you can try the one click lag fix from the Dev section of the forum
are you still on the stock firmware?
About 50% of the time when i wake up my phone and try to drag down the lock screen, the touchscreen doesn't respond. The music widget on the lockscreen also does not respond when i tap it. I have tried restarting and it still does it. At first I thought it was when the wifi was on, but the problem exists either way. Anyone have any suggestions? I am running mdj froyo sense revolution 1.7. Any help would be appreciatied.
3agle said:
About 50% of the time when i wake up my phone and try to drag down the lock screen, the touchscreen doesn't respond. The music widget on the lockscreen also does not respond when i tap it. I have tried restarting and it still does it. At first I thought it was when the wifi was on, but the problem exists either way. Anyone have any suggestions? I am running mdj froyo sense revolution 1.7. Any help would be appreciatied.
Click to expand...
Click to collapse
Dude I had the same problem with mine running that rom. I would turn screen on and off till touch screen worked. It gradually got worse and worse till it just stopped working. Don't know if its the rom that cuased it or just my device since my touchscreen just gave out and no longer works on windows or android. It's sent off for repair.
i'm also having this same problem with the combo in my sig. very annoying.
Now the problem has spread to winmo too. i have a horrible feeling the touchscreen is going bad as well. what do you have to do to get it back to stock so you can get a replacement?
3agle said:
About 50% of the time when i wake up my phone and try to drag down the lock screen, the touchscreen doesn't respond. The music widget on the lockscreen also does not respond when i tap it. I have tried restarting and it still does it. At first I thought it was when the wifi was on, but the problem exists either way. Anyone have any suggestions? I am running mdj froyo sense revolution 1.7. Any help would be appreciatied.
Click to expand...
Click to collapse
I have exactly the same problem ! With hd roms too.
For all friends experiencing this issue here is my sum-up:
- HD2 (as I read somewhere) has slightly different resolution than what Android places on the screen (difference in 4 pixels I guess) - but this should not be the issue for normal operation right? Well, maybe yes maybe not.
- My screen went dead completely after using many ROMs but the longest I used was hyperdroid - again I don't think it is build related but hardware related issue.
- I sent back to Tmobile mine and got replacement - but until this one will work we will see...
Solution in USA: I have enrolled myself in extended warranty for $2/mo -- technically it covers the phone for as long as you have it (exclusions are of course liquid and physical damage) but anything else - covered. I even asked what happens if HD2 is discontinued and they said I would get comparable replacement of my choice. Therefore, I am covered.
NOTE: Tired tonight to do any updates - but Im gonna install back HD rom now and move on - push it really hard until it dies again ahahhahaha - cuz guess what? I don care - since im covered now...
it is the power button (AP Board); it gets stock inside. my does it all the time i just played with the botton untill it goes. the AP Board needs to be replace.
Is that a bug of android or is my hd2 defect?
its cuz of the setcpu
souljaboy said:
its cuz of the setcpu
Click to expand...
Click to collapse
What do you mean?
Have the same problem!! the screen won't come back up on after going on sleeping mode if the phone is unused for 5 m or more. Very anoying coz i love android.
adr205 said:
Have the same problem!! the screen won't come back up on after going on sleeping mode if the phone is unused for 5 m or more. Very anoying coz i love android.
Click to expand...
Click to collapse
This is not the problem we are experiencing. You are experiencing the sleep of death.
What we are experiencing (MYSELF INCLUDED - THOUGH NOT AS OFTEN) is an unresponsive screen when the screen comes on and go to the lock screen, though it wont register the unlock swipe. It takes a good 3-5 seconds for it to become responsive. Not a deal breaker but definitely annoying as hell!
I am having the same issue as the OP and i wish someone can find a way to fix it because it is very annoying.
It's caused by low SD card speed when r/w small block. I used kingstone SD card before, i had the same problem as you. After I switched to Sandisk, the problem is gone. I test the speed of two card, for large block r/w, they had the same speed, but for small block. Sandisk is 20 times faster than kingstone.
ferretzhu said:
It's caused by low SD card speed when r/w small block. I used kingstone SD card before, i had the same problem as you. After I switched to Sandisk, the problem is gone. I test the speed of two card, for large block r/w, they had the same speed, but for small block. Sandisk is 20 times faster than kingstone.
Click to expand...
Click to collapse
HUmm... tell me why my 8GB class 6 has this problem then?
I assume class 10 will complete remove the issue?
ferretzhu said:
It's caused by low SD card speed when r/w small block. I used kingstone SD card before, i had the same problem as you. After I switched to Sandisk, the problem is gone. I test the speed of two card, for large block r/w, they had the same speed, but for small block. Sandisk is 20 times faster than kingstone.
Click to expand...
Click to collapse
thank you my friend. I Change it and all is ok.
Um try waking the screen with other button than the power one that sud help but this is a hardware issue I experience it too and it usually get worse over time so best bet for u is to send it in under your repair or get yrself a replacement but it doesn't have anything to do with specific Rom just is that android puts so much stress on our hardware button because Android heavily relies on the keys through the operating system and the hardware keys ware out and cause this issue so look into this as well but before you send it in revert It back to the stock Rom
Sent from my HTC HD2 using XDA App
No I am pretty sure that it is not a hardware issue. I to have had it, and it is gone the only thing i can relate it to is that i stoped using mdjays kernell,, and started to use hastarin again. well it sure is a longshot but mine works perfekt again.
Do your finger on the sensor and turn it on.
I have the default 16 Gb class 2 card tmobile usa gave me and my hd2 did this on all builds until the new hastarin recently and it stopped it. Has not come back yet. So, while the sd card may have some pull in this issue, the kernel can play a factor too. Try using hastarin's kernel just for a day and see if it works.
ummm ive come up with this
http://forum.xda-developers.com/showthread.php?t=868452
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83
Hey guys, would love to get some help.
Flashed 2.08HSPL to my phone a while back with radio 2.15.50.14
Using Transcend 8GB Class 6 Fat32 format with 32kb buffer.
I've tried multiple Android versions (MDJ, PPDSHIFT, DL Desire) and they all often freeze. Either within a day, or literally after I load the ROM for the first time and doesn't seem to be stable. The longest I've ever had a ROM with no freezing is PPD Shifts 2.3.2 V6 Gingerbread series. Then one day it started freezing.
As in freezing, the screen freezes, I can't turn the phone off at all. I leave it hoping it would un freeze, but nothing works. The only way is to take out the battery.
Is there something wrong with HSPL 3? Should I try to reload it? Or fix the radio?
I've upgraded from a class 2 SD card and I thought it works better, but no avail.
Should i stop going SD but go to NAND? Would that stop freezing?
Or is it my phone?
I'm running Stock Windows 6.15
Please, any help would be great. This phone has so much potential but it just freezes.
It sounds like the quite common overheating problem some hd2s have. Mine gets really hot in the bottom part under heavy usage and freezes afterwards. I think it its covered by the warranty though.
I'm having the same problem. Once it gets warm the phone freezes and when I turn on data connection also. Without a sim card in place phone works just fine hmm..
I got the same issue few times.
I am guessing you are heavy user too!
Mine even got reboot automatically when its overheated -.-!
sniper3 said:
I got the same issue few times.
I am guessing you are heavy user too!
Mine even got reboot automatically when its overheated -.-!
Click to expand...
Click to collapse
Anyone managed to sort this yet?
Its happening to my hd2 all the time.
If I turn data and GPS on....game over...freezes straight away and sometimes loud buzzing
Noise.
Have to pull battery out to reboot.
I´m sorry if this problem has been solved elsewhere, but i´m not able to find any description of the problem like mine.
The problem is, that my HD2 won´t wake up from "sleep" sometimes, most after about half an hour of sleep. The screen and the keys gets lit up, but the screen stays blank. This has happened to me with diefferent ROMs (i tried Dorimanx, Hyperdroid, Nexus ICS and EVO ICS), but it worked with both Dorimanx and Hyperdroid for some time. First i had the same issue with these roms, but i managed to get them to work. But the problem is: I dont know how.
Now, after running on Hyperdroid for some time (witout any problems) i flashed the NEXUS HD2 ICS ROM from Tytung, and i´m having the same problem again. I did a clean install, tried with task29 and factory reset in the recovery, but nothing worked. Any suggestions?
Sorry for bad English btw :angel:
I thought the bsod was fixed ages ago? .. weird. And since it's an issue JUST with you on EVERY rom, it might be hardware related, I cannot say for sure. Maybe a logcat will help us get something?
Marvlesz said:
I thought the bsod was fixed ages ago? .. weird. And since it's an issue JUST with you on EVERY rom, it might be hardware related, I cannot say for sure. Maybe a logcat will help us get something?
Click to expand...
Click to collapse
+1, this issue was supposed to have been fixed a while ago. I'm also guessing it's some sort of hardware fault.
It seems to be a problem with the sd-card.. or more likely the format or the ext partition. I took it out, and the problem disappeared. But the card cant be broken, since it worked on the previous rom.. any ideas?
[Edit] Now i´ve Formattet and created a 1GB ext4 partition with the ext4 recovery, and reflashed the ROM and the 40a2sdx-a2recovery.zip script. I´ll try just not to put anything on the sd-card, and see if the problem still appears..
Now it happened again, without anything on the sd-card other than the ext4 partiton (and the .zip´s for the rom and the a2sdx script, but that should not change anything?). Am i doing anything wrong with the formatting or the partition, or is the sd-card just broken? I dont know what to do.. Do i have to buy a new micro-sd card? I have a 32gb sandisk class 4 card btw
No ideas? I´m getting a bit frustrated after hours and hours of searching the web and flashing different roms, recoverys and stuff. How can it be a problem with the sd-card, when i have used this one for the last rom, too, which worked just perfect?
Try setting the CPU-s minimum frequency to 384 or higher. If problem still appears, try setting the governor to performance and the max. frequency to for eg. 1036. The second solution will eat your battery but try it. I don't think the answer I gave you is right and I think your problem is due something damaged in your phone inside because my minimum freq. is 96.
EDIT:
Fix for Black Screen of Death
Black Screen of death occurs in many different phones like Htc Hd2, droid, Samsung..(With Android Rom Mainly). It is not caused by hardware, software or battery issues but because of Android Rom and clash of few settings.The screen will be black and the lights will be lit up and screen won't wake up. The only temporary fix is pull the battery. Annoying as hell. But, screen of death continues. My Solution ( it works on HTC Hd2) go to settings> personal> display settings. Deselect automatic brightness(No auto brightness).Screen time out 1 Minutes (No 30 Sec). Animation medium. Apply Settings. Okay.Go to settings again. Settings>system> Wlan (wireless network) > advance settings > wlan sleep policy > select never. Apply settings. Okay. Restart Phone twice to apply settings and test your phone. you screen should not go blank. Optional install android assistant & battery monitor widget that might prevent screen of death in certain cases. Good Luck!
Regards,
Mosa
I've found this on androidforums. There was probably a solution here but I was lazy.
Shaumaaa said:
Try setting the CPU-s minimum frequency to 384 or higher. If problem still appears, try setting the governor to performance and the max. frequency to for eg. 1036. The second solution will eat your battery but try it. I don't think the answer I gave you is right and I think your problem is due something damaged in your phone inside because my minimum freq. is 96.
EDIT:
Fix for Black Screen of Death
Black Screen of death occurs in many different phones like Htc Hd2, droid, Samsung..(With Android Rom Mainly). It is not caused by hardware, software or battery issues but because of Android Rom and clash of few settings.The screen will be black and the lights will be lit up and screen won't wake up. The only temporary fix is pull the battery. Annoying as hell. But, screen of death continues. My Solution ( it works on HTC Hd2) go to settings> personal> display settings. Deselect automatic brightness(No auto brightness).Screen time out 1 Minutes (No 30 Sec). Animation medium. Apply Settings. Okay.Go to settings again. Settings>system> Wlan (wireless network) > advance settings > wlan sleep policy > select never. Apply settings. Okay. Restart Phone twice to apply settings and test your phone. you screen should not go blank. Optional install android assistant & battery monitor widget that might prevent screen of death in certain cases. Good Luck!
Regards,
Mosa
I've found this on androidforums. There was probably a solution here but I was lazy.
Click to expand...
Click to collapse
I tried changing the CPU speed without any luck, and in the previous rom i had min set to 96 aswell... I also deselected autobrightness and Wlan sleep policy... Seems not to be the problem. And as i said, everything is working when sd-card is pulled out..
Shaumaaa said:
Try setting the CPU-s minimum frequency to 384 or higher. If problem still appears, try setting the governor to performance and the max. frequency to for eg. 1036. The second solution will eat your battery but try it. I don't think the answer I gave you is right and I think your problem is due something damaged in your phone inside because my minimum freq. is 96.
EDIT:
Fix for Black Screen of Death
Black Screen of death occurs in many different phones like Htc Hd2, droid, Samsung..(With Android Rom Mainly). It is not caused by hardware, software or battery issues but because of Android Rom and clash of few settings.The screen will be black and the lights will be lit up and screen won't wake up. The only temporary fix is pull the battery. Annoying as hell. But, screen of death continues. My Solution ( it works on HTC Hd2) go to settings> personal> display settings. Deselect automatic brightness(No auto brightness).Screen time out 1 Minutes (No 30 Sec). Animation medium. Apply Settings. Okay.Go to settings again. Settings>system> Wlan (wireless network) > advance settings > wlan sleep policy > select never. Apply settings. Okay. Restart Phone twice to apply settings and test your phone. you screen should not go blank. Optional install android assistant & battery monitor widget that might prevent screen of death in certain cases. Good Luck!
Regards,
Mosa
I've found this on androidforums. There was probably a solution here but I was lazy.
Click to expand...
Click to collapse
It's a very old problem. It was fixed long ago, so it shouldn't be happening to anyone on a NAND ROM right now.
Nigeldg said:
It's a very old problem. It was fixed long ago, so it shouldn't be happening to anyone on a NAND ROM right now.
Click to expand...
Click to collapse
But i´m actually having this problem, and i´m definately on NAND
Are you really unable to change the sd-card? Why not get an upgrade? maybe a better class? or a higher storage? (I know you have a 32 GB class 4 sd card, it's really hard to upgrade that, I understand)
If you don't want to, you have to narrow down the problem.
Try a different recovery ( I doubt this has anything to do with it, but you gotta try)
Try a different fs. (other than ext4, give ext3 a shot)
Are they both set to primary and not logical? (I thought it shouldn't work if either is set to logical? perhaps I'm wrong)
What is the fs of your main partition? (Are you sure it's FAT32?)
Try to check for bad sectors.
^I know it's too much, and you can try from the most likely to the least likely. (Sorry, I do not know the order)
Or, you can sit tight and wait for other answers.
Marvlesz said:
Are you really unable to change the sd-card? Why not get an upgrade? maybe a better class? or a higher storage? (I know you have a 32 GB class 4 sd card, it's really hard to upgrade that, I understand)
If you don't want to, you have to narrow down the problem.
Try a different recovery ( I doubt this has anything to do with it, but you gotta try)
Try a different fs. (other than ext4, give ext3 a shot)
Are they both set to primary and not logical? (I thought it shouldn't work if either is set to logical? perhaps I'm wrong)
What is the fs of your main partition? (Are you sure it's FAT32?)
Try to check for bad sectors.
^I know it's too much, and you can try from the most likely to the least likely. (Sorry, I do not know the order)
Or, you can sit tight and wait for other answers.
Click to expand...
Click to collapse
Yeah, its much, but i must say i have tried nearly everthing. I tried different recoverys, both ext4 and ext3, both of the fs are set to primary and the main fs is FAT32. I´ll try to check for bad sectors, and if i get the black screen next time i´ll try with another sd-card. Until then, if any of you have any other ideas or suggestions.. But thanks for the try
It happened again-.- No other solutions? am i really the only one suffering from this issue? BTW, anyone know what caused this problem, when you say it was "fixed long time ago"? I realized i have the 3.0.0 recovery, could this be part of the problem? Looks like I´ll have to try another card, but i dont know why that should be the problem, since this one worked for my previous rom...
You can try to upgrade your recovery, since nothing else is working for you. It is worth a shot.
I'm experiencing the same issue since I changed my SD card. I'm running NexusHD2-JellyBean-4.1.2. It was very slow with a class 2 card, but I had no wakeup freezes. After I upgraded to a class 10 card it's much faster, but I also started experiencing those wakeup freezes.
First I changed the cpu frequency range to 128-998, I kept smartassv2 as the governor and I also disabled wifi (someone else suggested keeping it always on as a possible workaround). I haven't had any freezes for almost 24h. I suspect it freezes while trying to turn wifi back on during wake up, but it definitely has something to do with the card, too, because when using the other (slower) card the rom was stable.
I haven't had any issues of this kind with any other rom.
Marvlesz said:
You can try to upgrade your recovery, since nothing else is working for you. It is worth a shot.
Click to expand...
Click to collapse
atakama said:
I'm experiencing the same issue since I changed my SD card. I'm running NexusHD2-JellyBean-4.1.2. It was very slow with a class 2 card, but I had no wakeup freezes. After I upgraded to a class 10 card it's much faster, but I also started experiencing those wakeup freezes.
First I changed the cpu frequency range to 128-998, I kept smartassv2 as the governor and I also disabled wifi (someone else suggested keeping it always on as a possible workaround). I haven't had any freezes for almost 24h. I suspect it freezes while trying to turn wifi back on during wake up, but it definitely has something to do with the card, too, because when using the other (slower) card the rom was stable.
I haven't had any issues of this kind with any other rom.
Click to expand...
Click to collapse
Thank you both I´ll update my recovery, change sd-card and make another clean install. Its a bit weird, but we´ll see
Ok, seems like the sd-card really was the problem. I changed to an 8GB card, and i have not had the issue since. Everything is a bit slow, and some apps need time to load, but that could be because it is a slower card.. i hope. I think i´ll buy an 32gb class 10 card, and hope that it works and is faster Thank you all for the ideas and help. I hope my problem is solved :victory:
yup.. same problem a while ago..
Flash Latest ROM
Install Easy Task Killer and manage it properly
Try using a High Speed Micro-SD Card.
When it comes to HD2. you can face "n" number of issues
Don't use task killer!
Marek989 said:
Don't use task killer!
Click to expand...
Click to collapse
I read many senior members giving the same advice. Task Killers are a pain if you use them randomly. I configured Easy Task Killer to kill only specific and useless apps/process.. all required apps and processes are ignored by it.
By using SystemCleanUp i have disabled all useless autoruns.. my roms are much faster and stable now.
HD2 has too less RAM for not using Task Killers.
Using Task Killers and SystemCleanUp even on my Asus Transformer TF101..