Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Sounds like you need to Odin.
bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
I got that on EB as well. It's weird because it didn't start as soon as I flashed it. It was maybe about a week later when it started doing that. When it happened to me my phone would vibrate sporadically and then the screen would finally go "black" or turn off. The odd thing is the bottom four buttons would stay lit. I would have to pull the battery. It started happening more and more frequently. I've since flashed to EC and am rooted but that's it. I've been flashing back and forth between different set ups, so I haven't been on this current set up for more than 2 days. I did however have the same problem today at lunch. I had to pull the battery to get it to reset. I was playing a video I recorded on my phone before the screen went black. I don't know if it was media related. I will play some more videos and see if it does it again.
k0nane said:
Sounds like you need to Odin.
Click to expand...
Click to collapse
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
cpcormier3 said:
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
Click to expand...
Click to collapse
Have you tried formatting your SD card yet?
k0nane said:
Have you tried formatting your SD card yet?
Click to expand...
Click to collapse
I haven't with EC, but I did with EB and I still had those problems. Today was the first day that it's happened to me. I've only been on this set up for the last couple of days, because I flashed a couple of things and hoping that I would have better luck with stock. I will try re-formatting when I get home. I tried playing a coulpe of videos (the same ones as before) to see if I could replicate the problem, but haven't been able to yet. Hopefully that was just a situation to where the phone just needed to reboot....
bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
!!! Y E S !!!
It happened to me four times today!
Does anyone know a way to get logs to continuously write to disk? Otherwise I have no idea how to troubleshoot this.
I'm running, midNIGHT EC05 with minimal apps installed. I use SetCPU, and I've just changed the settings. I'm thinking this may have started after trying to use 100MHz and "startass" setting. My profiles are now set to 200Mhz minimum and "ondemand." I'll let you know how that goes.
Having to use my old BlackBerry Bold as an alarm clock now, just in case!
EDIT: I did not format SD with this install but have formatted less than 2 weeks ago.
Happened again after setCPU settings were changed.
That happened to me but what's weird isnit only happened when I was on di18 kept having to pull the battery and once I updated to eb13 it all stopped
Sent from my SPH-D700 using XDA Premium App
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Same here. Like the term sod, btw. Happening when I use flash. I'm on stock ec coming from fresh odin, and formatted sd.
Sent from my SPH-D700 using XDA Premium App
alfiej said:
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Click to expand...
Click to collapse
No Beautiful Widgets here.
I am running Go Launcher, which is new to me. Will likely eliminate that tomorrow. Oh yeah, the only other widget new to me is "Android System Info" (which is great, btw).
I run Pure Grid calendar and Sense Analog Clock widgets, but I've been running those without trouble for months.
Does anyone know how to change logging levels?
The only rom I was able to use without the SOD was myfrankenstein DK28. While on
EB13 it did it contstanly and much hasnt changed while running EC05. I formatted my sd card and only installed minimal apps. I tried not restoring from Titanium or Astro. Fresh install from market and it still happens. I've stopped using SetCPU, that didnt help either. I do have Beautiful widgets running on my home screen, but I aslo had that while running DK28. I have no idea what the problem is. It is a complete pain having to check my phone every couple of mins to make sure that its still on. Over night forget about it, every morning the phone is dead. Can anybody help me please.
I just Odin to EC05 last night.. and installed the new syndicate frozen rom... and my screen just went blank today.. so far it has done it twice in less then 5 minutes....
but I have noticed that if the phone is plugged into the charger that it wont do it.. no matter how long goes past.. thats the only way I know my alarm is gonna go off in the morning.. is to have it plugged in..
do anyone know if its doing it on plain Stock untouched modem and stock rom??
because if not imma flash over to that.. I cant take this crap too much longer..
I have had this so called SOD for almost 3-4 months and as a matter of fact I just ordered a replacement 10 minutes ago. My SOD involves the phone either rebooting or completely going black except for the bottom cap buttons, then vibrating in order once, then 3 times, then once, and so on until a battery pull. This has happened on the charger as well for some roms. I can tell you it does it on a stock rom. I just did a full reset, stock eb13, updated to ec05 OTA, wiped sdcard and everything except contacts. The problem exists, so I am almost 100% that it is a hardware flaw somewhere. I even did the ##786# reset. I'll let you know if a new phone fixes the issue :]
damn.. even on the stock rom huh???
well do anyone know if it might have something to do with rather journaling is on or off??
other wise.. i have not a clue of what could be causing it..
I have EC stock rom, but am rooted. It happens to my phone. It doesn't happen quite that often like you guys, but it happens maybe about once a day. It happened more frequently when I was on EB. It would happen at least 5 or 6 times a day. It's strange cause it never happened right when I flashed EB or EC. I was fine for a couple of days before it happened. Not sure why....?
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
sultan.of.swing said:
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
Click to expand...
Click to collapse
I had about six today. I'm flashing stock and running untouched starting tomorrow. If that doesn't fix it, it's replacement time for me too.
Sad, because a stress test on my phone at 1.4ghz ran fine.
Btw, I still use set cpu, but only in known safe configurations, no OC.
I just received my replacement. Brand new phone, I installed a formatted sdcard and synced contacts... within 10 minutes it seemed to be happening again. The phone was stock di18, then it updated to stock EB05... I have no idea what the problem could be now, since this phone is brand new.
Related
Hi,
Couldn't find anything in the forum, but it could be detailed a 100 different ways...
I'm having a problem where my x10 won't come out of sleep properly - it doesn't happen all the time, but often enough for it to be super annoying...
Basically I cannot get it out of sleep - the screen will turn on, but without backlight, and without the ability to interact with the touchscreen. to get out of it, I have to pull the back off the phone, and pull out the battery.
So in short, I'd say the digitizer and the backlight frequently fail (together) coming out of sleep (everything else 'works')
Anyone else had experience with this issue?
P.S. I'm not rooted.
Happened like 2 times to me, I leave it for 1 min and press again and it works.
No big deal.
sent from my x10i that is banging for a 2.1 upgrade. ...
mezo9090 said:
Happened like 2 times to me, I leave it for 1 min and press again and it works.
No big deal.
sent from my x10i that is banging for a 2.1 upgrade. ...
Click to expand...
Click to collapse
Normally I need the phone there and then, but worth a try waiting... I just upgraded to the latest FW, so hopefully it's the last time it happens...
Thanks!
Hmm.. tried the waiting option... left it for more than 10 min, and all it did was stay frozen and drain my battery...
Might try a full re-flash
Strange. I thought a Firmware upgrade would have sorted it. Do you have any apps installed that may be relevant, a lock app or anything? And did it do this from the moment you got your phone?
jas0607 said:
Strange. I thought a Firmware upgrade would have sorted it. Do you have any apps installed that may be relevant, a lock app or anything? And did it do this from the moment you got your phone?
Click to expand...
Click to collapse
It started happening fairly soon after I got the phone... couldn't say when, but it's now happening really frequently - at least 3 times today already...
I don't have any apps I could pinpoint, although I'd guess it would have to be something I installed fairly early on.
Strange that it's getting worse though.
Hmm, it seems that this has happened to a few other people online, but mostly with HTC devices. Do your hardware buttons (at the bottom) wake it up differently at all?
http://androidforums.com/sprint-htc-hero/115869-phone-sleeps-does-not-wake-up.html
http://www.google.com/support/forum/p/android/thread?tid=3b57dc33e2c148aa&hl=en
jas0607 said:
Hmm, it seems that this has happened to a few other people online, but mostly with HTC devices. Do your hardware buttons (at the bottom) wake it up differently at all?
http://androidforums.com/sprint-htc-hero/115869-phone-sleeps-does-not-wake-up.html
http://www.google.com/support/forum/p/android/thread?tid=3b57dc33e2c148aa&hl=en
Click to expand...
Click to collapse
Thanks for the links...
Yeah, the HW buttons wake up fine (at least from what I can tell) but they're basically useless when the phone is stuck on the lockscreen
I did a full re-flash last night, so hopefully that fixes it...
It had better since all of the backup programs I had faith in failed me completely... man I'm annoyed... have to spend a bunch of hours putting everything back on my phone and setting it up again.
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
yep
+1
Not very often but very annoying if you use your phone as alarm clock.
I honestly haven't experienced either with my SGS. I can sympathise though as my Milestone used to do both way too often (hence swapping for the SGS).
It hasn't happened to me.. It might be running a software or hardware watchdog to reboot automatically when the system panics. Ensure you are using a stock rom, otherwise, it may even be faulty hardware
Would happen several times a day on my Motorola Milestone so I sent it back and got the SGS. Totally rock solid. Only time it reboots is when I want it to. Maybe you have a rogue app?
you guys have any changes to the CPU speed whatsoever, task killers and all? i once used SetCPU and it sort of sent me into a random spree of reboots and such.
i remember rebooting, scanning 10gb of media, auto-reboot... repeat 4 times. lol.
Well it hasnt happened since yesterday. I will flash to froyo today just in case it was software related
Sent from my GT-I9000 using XDA App
dakine said:
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
Click to expand...
Click to collapse
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
AllGamer said:
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
Click to expand...
Click to collapse
Link would be helpful, because I can't find that topic.
WOW, old thread that got dug up, for me it was just a software issue. I flashed many roms since and haven't had it happen again. I never reset my battery stats but I think clockwork mod recovery has an option to do that so most of the custom roms make that easy.
I also had random reboots and power-offs, on average once every 2 weeks, running on stock-firmware JF3. Problems did not go away when I manually upgraded to JM2. Problems stopped when I upgraded to Froyo...
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk
I am so glad I didn't update to 1.0.7!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App
My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.
I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself
Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2
This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App
My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.
Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.
CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue
First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App
I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured
Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App
That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...
joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.
Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
GronHog said:
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
Click to expand...
Click to collapse
Has it happened again since? If it has try and study your phone's behaviour whenever it happens (does it only happen when plugged in? and so on). Once you manage to get an idea of what actions cause it to happen, start up a logcat and replicate it and send it here. Also, if you've restored anything, downloaded a ton of apps, etc. try a clean install (w/ no restores, minimal apps, and so on) and see if it continues. I don't like to just leave things as "it's a hardware issue" because sometimes it can be difficult to tell.
Hasn't touched the phone for several hours, been on computer, when the incident happened. Had installed a flashlight app earlier in the day, TeslaLED. Also installed Google now M6 offline earlier in the week. Will keep an extra eye open to provide you with any info I can. No TB restore done between BR7 and MR1, as update was done OTA automatically with just ok'ing a cache wipe. The update went smooth, to me, from notification to download to flash and reboot on its own.
sent from Glacier under control of SyNthetic_aospX
again
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
GronHog said:
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
Click to expand...
Click to collapse
Whoops I meant I'll need a last_kmsg from after you pull the battery. That will tell me the last thing that happened before the battery pull. The op in my thread has a link that shows you how.
Sent from my MyTouch 4G using xda app-developers app
Been two days now, everything running as should, smooth. Reflashed Rom to get back to unpatched kernel, and did not reinstall gNOW. Later will install your patched kernel and keep an eye on it. Still getting the occasional inverted lockscreen, but that is no big deal, as this is the most stable ICS Rom that has run on my phone. All other ics Roms have barely made it past a week, cept Awesome's vanilla ics which hit the two week mark before giving me "unfortunately so an so has stopped working" and would cascade from there with errors. Will post up another logcat and kmsg log for you on the invert screen when I make happen again.
sent from Glacier under control of SyNthetic_aospX
Inverted lockscreen from yesterday, should be towards end of logcat=http://db.tt/YOl1UM78
A freeze up while using XDA app and following a link into Maxthon browser. Touched link in XDA auto launched browser then froze, let it sit there for a minute as back button did not kill app. Then phone rebooted itself, so found last_kmsg and saved it=http://db.tt/767lXrNH
Saved both files to dropbox
sent from Glacier under control of SyNthetic_aospX
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
GronHog said:
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
BeWeather was spamming that last logcat you gave me. That might be a part of the problem.
That thought popped into my head, don't know what the logcat was saying but seeing that much from BeWeather didn't look right. Thank you again for t the work you have put into this Rom.
sent from Glacier under control of SyNthetic_aospX
Self wake and freeze happen again, checked for last_kmsg there wasn't one, just last radio. Removed BeWeather widget, and unchecked auto update in the app this morning. I installed the kernel overlay last night, two days without overlay since reflash. Going to leave phone as is for now and run kernel log to see if it happens again.
sent from Glacier under control of SyNthetic_aospX
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
GronHog said:
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
Okay. Now bear with me on this one. Because it may seem odd... but try getting a new sim card (it's free) and see if it works. I noticed your logs were different but both had to do with ARM9 crashing due to WCDMA (both times with varying feedback after ARM9 crashing, but both keeping WCDMA common in the kmsg). I looked it up and came across THIS in the cyanogenmod forums. It worked for both of these guys and the other dude basically flipped out on the other because he thought he was dumb, but it worked and ended up looking like a jerk lol.
Another log= http://db.tt/0dfJ4nYJ
Thank you very much for even bothering with my issues. Not to long after my last post the phone froze with screen off and did battery pull. Was able get another last log. I have done a format of everything and reflashed. Installed a few apps and did not do titanium restore. Going to look into getting new sim. Again I thank you and bow to your superior intellect:beer:
Sent from my MyTouch 4G using xda app-developers app