Related
Im currently using the imate rom 2.16.9.1.wwe Rom date 2/6/06 extrom version 0 2.16.9.101
It has been working fine for the past few weeks and the performane increase has been much better. I was also using the oush mail which also worked well. Then a few days ago I started to have a few problems with the phone, basically it would look as if it was working the lights flashing, however when I went to turn it on it wouldn’t turn on. The only way to resolve this si to soft reset the handset. This problem is now occuring on average 2 times a day! I havent even installed any new software!! Thwe only major incident before this started happening was I used skype twice! But havent used it since! I have also stopped push mail cause I thought this maybe the issue but it didn’t solve it!
Its so annoying cause I think the device is operating normally cause I see the flashing lights however it cant do anything cause it has frozen!
Any ideas???
I was thinking of going for a hard reset but if I restore my backup ive taken with spb will this not just reintroduce the problem?
just to add for further info i have no apps running and the
program memory is total - 44.01mb
in use 19.67mb and Free 24.34
thats after a soft reboot!!
This might be a really silly suggestion, so appologies if it is, but could it be just the backlight turned off for some reason so it looks like the device is off when it is actually on?
No, I don't think that it is the backlight as I am also now experiencing this same problem ... approx 1 - 2 time daily. You think that the phone is functioning until you try to use it. Only option is soft reset.
Any help on this would be appreciated.
no at present a soft reset is the only cure and even then it may occur again later on! Bluey HK are you using the same rom as me??? the imate one?
its done it twice already today and its only midday! the last time i was just browsing the web, closed the browser, then switched it off and then couldnt turn it back on! Do you think it may be a memory leakage issue????
This happened to me yesterday on my T-Mobile MDA. I am running the latest T-Mobile_RUU_Wizard_2210401_221_20710_ENG_US image from xelencin.
What appears to have triggered the problem for me was attempting to connect to T-Mobile's My Email app to download mailbox settings while the signal level is too low or intermittent (Wi-fi and Bluetooth were disabled).
The backlight would not turn on and I could observe the My Email app trying to access the server.
it sounds as though it may be a bug connected with a GPRS connection???
ahh its done it again, this time i wasnt doing anything just died! I think i am gonnna have to do a hard reset cause this is making the phone unuseable!
if i do a hard reset and then install a back up is there a high possibility that this will reintroduce the bug???
its not the backlight
my 8125 is having the same damn problem. its nto a backlight issue, as it just stalls, and the past 4 times its done it, i've just removed the battery and turned it back on as a soft reset wont work, and i can't it to react to any commands. this is either a software issue all our phones are dying. i was having this problem with summitter's previous 2.17 rom, then updated to the recent 2.17.11 aku 2.2 rom... thinking the upgraded rom is what it needed...NOPE... still crashed. almost all instances i believe are when the wifi connection was active. but i could be making that up, i'm positive on 3 occasions it was with a wifi connection active. but not too sure about the 4th.
this is making me insane, and we need to figure out whats up~!
to expound on the problem:
one time i was in the middle of checking voicemail, then tried to delete, but the screen wouldn't light up, and it wasn't responding to my option 7 to delete command. the other time was in the middle of a phone call. something's up....
i am having the same issue with my 9100, its running the latest offical rom, mine does it whenever it feels i dont believe it is wifi or gprs related as i have the problem at time when i have been using neither.
there does not appear to be a link to any software i am using either
any ideas?.
yea- i get the same sometimes, i go to take my phone out of standby and it wont do anything, the power button doesnt work- the light just flashes. sometimes it freezes on the today screen, the power button dont work or anything. really need to sort this!
any ideas? any1 else get this? its where u put ur MDA in standby, and next time u press power button 2 turn on nufin happens, but the leds still flash at the top!
yep i still get the problem! still no cure!
I have exactly the same problem... I just pick up my device from my pocket to use it, I press on the power button once but the device won't wake up from the standby mode. I wish someone can give us a cure.
Low Battery...
I had this happen to me once recently...for me it was becuase my battery was too low. Freaked me out, because everything looked good, but I would power on and get nothing! Right after it started it powered on for a sec then quit. I had to put it on the charger and leave it for a couple hours to get a good solid charge, then everything was fine. Hope this helps....
thanks for the response, unfortunately mine is definately not related to the battery charge!
mine hasnt done it in the last day, ive been leaving it a while before putting it into standby. i used to exit my app (messaging or whatever) and shut it off straightaway, but i give it a sec or 2 to make sure its all good
and its doin ok so far!
It all started when I upgraded to a new rom. So the first thing I did was ditch the rom and install a new rom. I was running Black 3.0.1 and now updated to Black Satin.
The time it takes to lock up seems to very. I have had times where I could leave it for 4hrs and then hit the power button and it comes to life, other times I can have it sit for 30mins and hit the power button only to find it won't wake up. When it is in its locked up state, it won't even receive calls. It just sits there with the top right led blinking green. Its really getting frustrating.
In order to get it to come back I have to push the reset button on the bottom of the phone with my stylus.
I have been reading as many "lock up" threads as I can on the forum and so far it seems that most are to do with Push Mail. Which I don't use.
Any suggestions will be much appreciated.
I dont know if its a ROM issue as my does this sometimes (dont know about incoming calls as i dont get that many anyway) I am on the stock T-Mobile rom
I dont use push mail either
doesn't happen much to me (now i said i bet it does it all the time )
I think it seems to do it when i havnt soft restarted it for a while, so it could be that the lock up is due to memory or something and it just needs a soft reset to clear it down
I also have this problem, only a soft reset makes the phone respond. This happens sometimes when the phone has only been reset an hour previously.
It also happened once during the night and caused my alarm to not go off, so I only made it to the office for 10:30!!
Did you guys find a solution or did the problem just go away?
bump
got the same problem.
For me the problem went away only after I installed a new radio and new rom. I honestly don't know what was causing the problem. But it went away and I am happy. There might have been an issue with an installed app, but I never did find any app that directly caused the issue.
I'm in between surgery so thought I'd post a quick question where the answer is puzzling me.
Basically, I'm in wonder if this has happened to any other soul?
Picked up my HD2 when I came out of Theatre and it simply would not switch on.
Thinking it may be the battery that had run down I connected it to a power source to charge and noticed the Orange charge indicator did not light up.
Next I took out the battery and reinserted, then pushed the power button......
Still nothing.
Thinking was it a problematic battery (although it still should have switched on when connected to a power source) I exchanged the battery for the spare I take around with me.
Still nothing.
Finally, I reinserted the first battery and once again pressed the power button.
This time it fired up and loaded without any issue.
I checked the battery level ~ that indicated 56% still remaining.
So I am in puzzlement as to what may have caused it's temporary death.
Has any other had a similar experience?
Edit 01 ~ 24 Feb 2010
It would seem that to some (myself included) there is a fix that does indeed cure the problem and that is by using the software application MemMaid.
Others have tried SKTools but MemMaid seems to operate much better at terminating the freezes.
Unfortunately MemMaid is not free and seeing as HTC will not budge from this being a 'users personal settings' that is causing the freeze our only course of action at the moment is by using MemMaid.
However, please do note..... Not everyone has benefited from using MemMaid; why that is the case could be down to some individuality ~ a different setting, installed software, routine notification, etc. etc.
In other words first try the free trial version of MemMaid and if it seems to cure the the problem then do consider investing in it.... besides all this it is a great piece of software.
You can get hold of MemMaid here.
Word of Warning.....
Ensure you set up MemMaid correctly. I spent ages with member wacky banana throwing many personal messages between the two of us like fervid lovers until finally wacky came up with a setting we could use.
Below is the settings to apply to MemMaid:-
In your programs section you should see 2 icons, one called Memmaid Quick Clean and the other is Memmaid.
Click on the Memmaid icon and a window opens.
At the top left corner it should say Quick Cleaner but this is not relevant for now.
Put a tick in the the following options (the list is scrollable):
- compact ram
- windows temp files
- temp files
- ie cache files
- ie history files
- opera cache
- dead shortcuts
- duplicate notifications
- dangling notifications
- invalid notifications
- rebuild notification queue
- recycle bin
- google maps cache
Press the CLEAN button and wait for the tool to do its job then press the close button.
Next, on the bottom right of your screen, click the Tools option. From the drop-down menu choose CLEAN SCHEDULE.
Tick the following items:
- on soft reset
- daily (here you need to scroll to the right to select the icon with the 3 dots in it to set your schedule)
- show report (optional)
- show progress (optional)
Click DONE on the bottom left corner on your screen and job's a good 'un!
Edit 02 ~ 24 Feb 2010
Member jonbaker76 came up with a few extra tips to help alleviate the problem:-
1). Install MemMaid and follow settings provided by Beards & WB
[*]2). Disable the alarm (use G-Alarm maybe)
[*]3). Turn off Facebook updates
[*]4). Turn off Weather updates
[*]5). Turn off Internet Time Sync
[*]6). Wait a while before carrying out a soft reset, your Phone may just wake up
Edit 03 ~ 25 Feb 2010
Guys,
We are starting to find a pattern building up here relating the problem with Sense.
Some users don't have problems with ROM 1.48 but others Do/Did (I used to) so we can't say v1.48 was okay.
However, it's the later ROM's which seem to have the greater of the problem which could relate to an issue with Sense.
i.e. Although evident in v1.48 it was not as strong but with either Cooked ROM's or updated ROM's the problem has been magnified.
A few Guys have now tried using their HD2 without Sense and report a stable platform.
What I am saying here is if you have the problem and you can afford not to use Sense then try running your Phone without it for a trial and see how it performs...... With enough info we can pass this on to HTC.
I had a situation where I switched the phone back on (from standby/power saving mode) only to find it was dead. To get it running again I had to perform a soft reset and, like you, I found that I had plenty of battery remaining. This happened only once in three weeks of usage and I'm not sure what caused it.
James
I had a similar issue a few days ago.
I picked the phone up and pressed the power button, but nothing happened. I did the same as you and assumed that it was flat (despite me being a charging maniac!) I plugged it in and got no charging light, so I popped out the battery and put it back in. It turned on first time then.
I wasn't really concered as it's only happened once in over 3 weeks, and I'd only recently upgraded the ROM so I was ignoring any little foibles like this.
Maybe it's a little more common than I thought?
this has happened to me twice since upgrading to the new recent rom.
Beards said:
I'm in between surgery so thought I'd post a quick question where the answer is puzzling me.
Basically, I'm in wonder if this has happened to any other soul?
Picked up my HD2 when I came out of Theatre and it simply would not switch on.
Thinking it may be the battery that had run down I connected it to a power source to charge and noticed the Orange charge indicator did not light up.
Next I took out the battery and reinserted, then pushed the power button......
Still nothing.
Thinking was it a problematic battery (although it still should have switched on when connected to a power source) I exchanged the battery for the spare I take around with me.
Still nothing.
Finally, I reinserted the first battery and once again pressed the power button.
This time it fired up and loaded without any issue.
I checked the battery level ~ that indicated 56% still remaining.
So I am in puzzlement as to what may have caused it's temporary death.
Has any other had a similar experience?
Click to expand...
Click to collapse
May be a warning from HTC for your now very famous camera thread,if I were you would be carefull LOl!!
hagba said:
May be a warning from HTC for your now very famous camera thread,if I were you would be carefull LOl!!
Click to expand...
Click to collapse
....
Big brother watching us...
Beards,
Did you have any diary appointments or alarms set on the device today that you did not immediately cancel on notification or multiple alarms set/going off? If you did then this is probably a notification queue issue locking up the phone, forcing a reboot.
This symptom was very common with the TYTN when it first came out and drove me absolutely bananas!
Long shot but let me know.
WB
No... nothing was left to tie the Phone up.
I remember checking everything before I went down to Theatre earlier this morning.
In a way I'm pleased it's not an isolated case and that others have experienced something similar (sorry Guys, I don't wish it on you ~ just a little relieved I'm not the only one).
I know HTC monitor the 'Camera Problem' topic (they've told me this directly). Maybe they have some super-duper exra-terrestial monitoring machine that can achieve the Dynamics of masspoint collections..
Yep, I too have had this issue.
Was using phone normally, left it on stand by by pressing the power key. Wanted to make a call, it did not turn on. Opened back cover to do soft reset, did not turn on, started sweating..., swore at the phone and took battery out and then replaced battery and pressed power button and what do you know, booted up like nothing happened.
Am using original shipped UK ROM. Have not upgraded.
You should check this as well (first 2 might be from the same poster):
http://forum.vodafone.co.uk/index.php?showtopic=41974
http://forum.xda-developers.com/showthread.php?t=591226&highlight=freeze
http://forum.xda-developers.com/showthread.php?t=595646&highlight=freeze
I had the same problem - it happened only 2 times for a week, but it was nasty enough (and in combination with the camera problem) to make me finally send my phone back for a refund.
Basically the symptoms were similar - I would leave the phone somewhere for more than a couple of hours only to find it somehow switched off or something. The buttons light up when clicked, but the screen remains black - only battery removal helps and after that runs like normal...
I have quite a number of calendar notifications etc. - this might be a good clue!
I have the feeling that this thread might grow as big as the camera thread. Perhaps HTC fix that with a software update as well ...
A friend of mine had this problem with his HD2 on Sunday morning. He was surfing the web with it when it froze up. When he took the battery out/in again it wouldn't turn on.
He called HTC and they came to pick up his handset on monday. I guess he'll have to wait to get it back repaired Maybe he should have tried taking it out a few more times first.
deyanp said:
You should check this as well (first 2 might be from the same poster):
http://forum.vodafone.co.uk/index.php?showtopic=41974
http://forum.xda-developers.com/showthread.php?t=591226&highlight=freeze
http://forum.xda-developers.com/showthread.php?t=595646&highlight=freeze
I had the same problem - it happened only 2 times for a week, but it was nasty enough (and in combination with the camera problem) to make me finally send my phone back for a refund.
Basically the symptoms were similar - I would leave the phone somewhere for more than a couple of hours only to find it somehow switched off or something. The buttons light up when clicked, but the screen remains black - only battery removal helps and after that runs like normal...
I have quite a number of calendar notifications etc. - this might be a good clue!
I have the feeling that this thread might grow as big as the camera thread. Perhaps HTC fix that with a software update as well ...
Click to expand...
Click to collapse
I had something similar this morning, I have been using the alarm for the last 2 weeks with no problems. this morning the screen lit up, i saw the notification on the top but there was no noise. as a veteran of WM i dismissed it as "typical". however, the screen then went blank, the buttons would light up but nothing happened. I reset the phone to no avail, button still lit up but no screen - mild panic. removed and refitted the battery and all has been well since.
won't be too chuffed if it happens again....
rivets
Beards,
Notwithstanding that this may be some kind of new software or hardware problem, I just wonder about the notification queue.
I would try using a copy of SKTools to clear the notification queue ( I think you can do other tweaks as well but it's been a while since I used it) and see what happens.
Did you have any missed calls you did not answer today (another possible culprit, linked into auto screen lock = disaster).
I am simply putting ideas out for you to try to narrow the problem down. Don't know if any of this will work.
WB
PS: Just had another thought; have you installed an application onto your SD card that is on-screen? Used to have this issue with a weather application, sat on screen but installed to the SD card.
If the phone went into sleep mode and the application polled the weather servers then it would die a horrible death. De-installing and reinstalling to phone memory solved the problem.
Again its a long shot but you never know.
WB
Ive had that same problem twice last night within th space of 1/2 hour and the today i ran fine up until about 5pm today, where it froze, I updated the rom on sunday from O2 1.43 hope this is not gonna be a problem, anyone know where to get O2 1.43 rom just in case I have to return
wacky.banana said:
Beards,
Notwithstanding that this may be some kind of new software or hardware problem, I just wonder about the notification queue.
I would try using a copy of SKTools to clear the notification queue ( I think you can do other tweaks as well but it's been a while since I used it) and see what happens.
Did you have any missed calls you did not answer today (another possible culprit, linked into auto screen lock = disaster).
I am simply putting ideas out for you to try to narrow the problem down. Don't know if any of this will work.
WB
PS: Just had another thought; have you installed an application onto your SD card that is on-screen? Used to have this issue with a weather application, sat on screen but installed to the SD card.
If the phone went into sleep mode and the application polled the weather servers then it would die a horrible death. De-installing and reinstalling to phone memory solved the problem.
Again its a long shot but you never know.
WB
Click to expand...
Click to collapse
Even though my profession is based on absolute accuracy in detail, when it comes to finding out why the HD2 died I'll try any long-shot.
There were no programs loaded though and I know nothing was paged to make the Phone send any notifications.
I'll have a good check at possible programs/dll's later though.
Thanks.
I've had the same a few times. Probably the reason was overloaded main memory. I removed some mp3 files, but the situation wasn't change.
htc touch pro2 vs hd2... just got the answer!
a day ago... i was unsure about the upgrade. i had posted tis msg in xda but was advised by a senior member tat it was worth the upgrade n i culd find all my answers to the query here. here was my msg...
"hi all. with all the hypes surrounding htc hd2... n my htc touch pro2 fast losing its crown of being the best winmo device in the market... shuld i upgrade to the hd2? n watz wif the glass screen? wuldn't it crack easily? it's glass! appreciate everyone's take on this. the only selling point tat is tempting me away frm my pro2 is abt the speed... 1ghz vs my miserable 528mhz... sad. everyone's talking abt its blazing speed. is it tat obvious?!
then again there's tat camera issue... the infamous pinkish spot, which htc support claims it's related to the 1ghz dragon fella... software related... n restricted to only a selected few?! so it's like going2 the lottery n c who gets the infected piece is it?! bottom line is... my pro2 seems like a honda civic... n the hd2 is purportedly a nissan skyline, but wif so many question marks hanging over its head, shuld i still go for the upgrade? thnx!"
guess wat, after reading most of the threads here... i think i'll stick with the htc touch pro2. the hd2 has way too many issues... even worse than the camera thingy tat i knew abt... but the number of issues tat r highlighted here abt the hd2... is enuf2 make me say no to hd2.
This thread here reminds me to some issues with WinMo 6.5/Manila 2.5 ROMs for the Xperia X1: Over there in the forum, you can find quite some postings describing the "standby of death" problem.
Just very close to some of the other issues we now face with the "real" Leo, too. In fact, there are more "similarities" like the stand-by issue, and nobody was really able to clearly reproduce the problem as there seems to be no pattern. The same problems are not existing in WinMo 6.1/Manila 2.1 ROMs for the Xperia - but some in a WinMo 6.1/Manila 2.5 version, when I follow the thread correctly.
I do strongly believe that there are, underneath the hood of Leo´s operating system, quite some nasty bugs in WinMo as well as Manila. I cannot imagine another explanation why 2 totally different devices with very different hardware (parts) would show the almost exact same issues.
Of course, porting the Leo ROM to something like Xperia may bring some issues, but most apparently, most bugs are coming from MS and HTC, not the talented chefs here. (One more reason to look forward to custom ROMs for the Leo. No good sign for HTC though, frankly spoken...)
mine die this morning too ... alarm didnt go off
but press and hold the power button wake the phone up and alarm start ringing. Then I power it off, and all the other buttons does not turn on the phone other than press and hold power button = soft reset ... weird
Camera patch is out today
waiting for new ROM release
Same thing happened to me this afternoon. The phone wouldn't start up when I pressed the power button so I tried holding the power button down to force a soft reset. At one point all the buttons lit up but nothing more happened. Eventually I pulled the battery out, stuck it back in and then the phone started.
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
Once in a while my screen will go completely BLACK outta nowhere... NOTHING I do brings screen back on or does ANYTHING at all UNTIL about 30-60 seconds it suddenly comes back on..
**Here is the curious part.. When screen comes back it is ALWAYS in CAMERA mode! weird right? I'm thinking maybe a virus though have found none...
My ONLY other guess is that it may be related to app LASTPASS as im running it at time AND it has a screenlock function after idle timer...
The part with camera showing up on return is quite disturbing though, although maybe thats a result of me pressing every button possible during blackout??
Any clues or similar experiences? It used to occur daily.. Now just once a week.. Every virus spyware scan came clean.. Tho since phone is NOT rooted im skeptical how accurate these virus/trojan screeners can be without system access?
Phone has never been out of my possession & utilize screenlock since day 1...
??