Every time I load Android and the screen locks, I am unable to get the screen to come back on. I've tried multiple builds but have the same issue with each one. Anyone else have this problem?
replace th zimage with the 7/23 build
if you're tmous then yea zimage 7/23 for any build. i found radio 2.08 to not cause any SOD's on the builds with android 2.1. froyo i had to upgrade to 2.10 because it would sod on me consitantly. even after that i had one or two sods after the initial "installation" of the build, although 3 or 4 restart button hits later and now i don't get any more sods. it seems to me anyway, that you just have to beat froyo a little bit before it behaves. 2.1 is old and wise and doesn't throw tantrums.
this is assuming you've formatted your sd card blah blah blah. common practice stuff we should all be in the habit of doing by now.
I've had a issue recently where darkstone froyo goes into SOD, and I have the 7/23 zImage...
cavemaneca said:
I've had a issue recently where darkstone froyo goes into SOD, and I have the 7/23 zImage...
Click to expand...
Click to collapse
may just be a weird thing with my setup then. i get them the first day and after enough reboots they stop coming all together. for the remainder of the time i have froyo booted, but very very rarely maybe twice in the past 3 days, it will act like it's going to sod but after 3 seconds the screen comes back.
darkt123 said:
may just be a weird thing with my setup then. i get them the first day and after enough reboots they stop coming all together. for the remainder of the time i have froyo booted, but very very rarely maybe twice in the past 3 days, it will act like it's going to sod but after 3 seconds the screen comes back.
Click to expand...
Click to collapse
well, it was fine for the first couple days, then all of the sudden just started it. I guess with the slowing down from w/e it just locks when it's asleep. I'm gonna try the 1gb data.img and see if that stops it from slowing down/SOD after i've got some programs installed.
Related
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
CodeMonk said:
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
Click to expand...
Click to collapse
Just go back to 2.0d. I ran 2.1.2 for a very short time and I couldn't take it anymore plus you know that the sprint 2.1 has confirmed issues one of which is the sdcard
Where can I get the original 2.0d now? Can someone post a download link to it please? I'm also experiencing a lot of lag these days as well..
Here's a quote from Fresh Toast v2.1:
A note on slowness: It is coming to our attention that there are several bugs in the latest Sprint 2.27.651.5 RUU which is the official Sprint release. It doesn't surprise me that there are bugs considering our original 1.5 had plenty. The main one that we have come across is a service called com.htc.bg that sucks up your processor. This causes that phone to become extremely laggy and overall run like crap. Go read my new FAQ: Why is my Android phone running so slow? to see what you can do about it, and to report the issue. Keep in mind that this would be a Sprint bug and not Fresh Rom / Fresh Toast.
Click to expand...
Click to collapse
I think this is why we're experiencing lag, hopefully someone can find a fix for it..
EDIT: Nvm, found the link, here it is:
http://geekfor.me/new-release/fresh-20d
I think you guys are right. I've been toying with the idea of using Fresh Toast to get overclocking, but 2.0d just worked for me and I had no real issues other than keyboard lag.
Are you guys running w/ Auto Killer (or alternative TK) or no? I've been running FT w/ AutoKiller set to Extreme, with max time between boots having been about 48 hours, and haven't seen any significant slowdown the longer the phone's been on..
I just need to start off by saying you guys are awesome! I'm actually enjoying my phone for the first time since I got it the first week it came out. Keep up the awesome work!
Main concern is that when the screen times out in either my Froyo or Eclair Roms, I cannot get it to wake up. Anything I press will initiate the back-light and nothing more. I've pressed several times using each button and nada, I have to pull the battery. All issues occurred prior to installing the latest zImage, running the task29 and formatting my sdcard.
Additionally, I've noticed the Camera Flash doesn't work in either Rom and no picture is shown in the Froyo build. Other then that, I have found no issues. Mild delays but that's probably attributed to the Class 2 card and early Android builds. No real concern here. None of these issues occur in the Windows Mobile environment.
So I pretty much put everything I am using in my signature. I have the Froyo build in \Android and the Desire files are all in the root of the SD. I have task 29 the system and used Panasonic's SDFormatter v2.0 to wipe the SD. I have nothing installed but exactly what I have listed in the signature. I haven't even copied over the Transformers movies. My issues are consistent even if I haven't set up any account information or anything. I'm not complaining and I've read some others express similar issues but haven't figured out an answer. So that's about it. If I find any answers to my few issues, I'll post here. And again, I'm freakin excited for the development of the Android Roms and NRG's WinMo Rom has never let me down. I just prefer Android but like having both options. Thanks for all the help and if there's nothing that can be done right now, well again, I'm not complaining... Stay at it Chefs, you guys are awesome!
OK I didn't think to try a different zimage but I used the July23rd one and my screen timeout issue is fixed. Now to resolve the no camera issue in my Froyo Rom and I'm set. The other issues are fairly minor and will likely get worked out in time.
Does your zImage charge the phone, too? I'm facing the same problem, sometimes the screen doesn't come on and at other times it's unresponsive even if it does.
Look around, the newest zimage causes this for some ppl. Chill for a new zimage release.
HI,with respect to user's , admins n DEvelopers i would like to say SOD might be due to the sleep time settings (image attached)in brightness.i might be wrong or might not be,if im wrong sorry in advance n would req. the admins to delete this thread,Tnx to all..
EDIT :
Use mattcfroyo 1.4 (with latest cotulla zimage) or DARKSTONE froyo v1 latest(384ram enabled)
[my preference] with windows rom: chuky gtx/chukydroid/miri17.6
and radio 2.10.50/2.12.50 no echo no robovoice no sleep of death evrything is fine
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Stoferr said:
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Click to expand...
Click to collapse
thats y i let this info to other users let see what happens to them,n i dont hav n SOD problem but i have robotic voice :"S too bad cant get rid off it,can u sggest me a ROM,m using updated tmous ROM n radio 2.12.50.xxx.. tnx in advance.. and lets see what others say with sleep turned of.. and please do share your results... thank u..
Im testing it right now, so far no problems, but it seems randomly whener SOD appears, so i'll just test it a little longer.
Im using the european HD2.
hmm.. Lets see the results of other users also... and please do share ur findings...
P.S: m using TMOUS HD2 and waitin when i can get rid of robotic voice.
Damnit just got it! Well, seems that this won't help It was a nice try tho
i have never had sleep of death its gta be rom and radio related
i tried to help all... thats all.. but tnx for tryin... but i dont hav SOD either.. now dloadin maatcleo+froyo v1.2 n gonna test if it has SOD..
robotic voice is killing me :'(
I've had sleep of death with basically every android build out there.. i don't think it's a setting in my personal opinion. i think it is because it's still in develoupment and the drivers aren't 100% yet.. and i'm sure in time it will be fixed.
I tried it on zimage 7/25 and still have SOD .Some claim they use the new zimage without SOD ,no matter what I do it won't wake up.
the battery is horrible on 7/23 zimage and carrying the charger in my pocket all the time is a pain.
Off topic: I loved the notes on dna u had there
The "Turn screen off" setting is active in my WM. Using German T-Mobile 1.72 ROM, Radio 2.10.50.19_2, Dan's Froyo V1, zImage 25/7.
Using this combination for two days now and didn't have a single SOD during this time... only two or three times a freeze for few seconds, but afterwards Android resumed working.
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Been using dans13 build with cotullas no speddy zimage. My Rom right now MIRI 17.6 and Radio 2.12.50.26. No SOD report here just couple of freezes now and then. Good battery life. I have to say that I disabled the Auto lock in Windows with HD2 tweak. The first time I tried android on hd 2 i got the SOD, but with this combination and disabling the auto lock been running smoothly. just my 2 cents.
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
Well what I don't get is when I started trying Android on my tmo hd2 I didn't get the sod but now I do. if its the screen why did it start now?
Daaaaaaaaaaaaaaaaaaaamn waiting for new zImage... Seems that I have a sharp panel... How can I check this?
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
well now im using miri's v17.6 rom wid radio 2.12 on tmous HD2 no SOD till now although sleep is active in WM...
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
I've read the same but i think a lot of it is just down to individual ROMs & radio builds, as when android started on hd2 everyone said turn off backlight but mine was never on high nor did i alter any settings as when haret kicks in it turns off all windows functions altogether so you can't have any cross network/OS issues, winmo is supposed to be cut off. although saying that if android is only running off sd how can you remove sd and still run android for 1hr or more? but that's a different topic.
If you have a Tmo US HD2 just use Cotulla's 7/23 zimage and you should not get sod. If you use 7/25 zimage, you WILL experience sod! If you experience sod with 7/23 zimage, then the likely culprit is your sd card. Reformat and try again. If that doesn't work, you need to try a different card.
I am using the 7/23 with chucky's rom, and i was fine all day yesterday but this morning i got 4 sod in 15 minutes, and everytime i rebooted after that. I changed my Radio to 2.12.50.02 and i turned off the sleep thing in WM, and so far haven't had a sod in about 3 hours.
Just done a search about this prob and there is a couple of similar threads but they are not really same issue.
This has happened 3 times now with different roms over past month and not sure what is causing it. Phones screen seems to go bright white on wakeup, looks like a negative.
Is there any experts out there who could shed some light on it. Does it sound like a slow hardware failure or is it more likely a software issue. As I say its only happened a few times and a reboot brings it back to normal but it just concerning
Has anybody else had this same issue on wakeup before?
My first reply post here...
I have the same issue...reboot will recover it...but ones it recovered after normal stand-by upon wake up...I assume it is just some incompatibility of Android with HD2 graphic processor, minor issue.
Current ROM
Omega WM6.5.x v14
Current Android Build
NexusHD2 v1.8
I used to have the same problem and put it down to an incompatibility. Since moving to a Nand ROM it seems to have gone away.
TheATHEiST said:
Phones screen seems to go bright white on wakeup, looks like a negative.
Has anybody else had this same issue on wakeup before?
Click to expand...
Click to collapse
I used to have this issue, but only on SD builds, and very, VERY rarely. From about 5-6 months of SD Android, I probably had it about 4 or 5 times.
I agree with madmillsy that I've not seen it on a NAND build, but I don't think I'd seen it on recent SD builds either.
Is it an SD build you're running, and if so, how old is it?
Edit: Forget that last question - just saw your current ROM in your sig.
I saw this effect twice, never in WM, only in Android. First time with SD build, but second time, last week with gauner's HD NAND build.
As it was already described, there is probably some incompatibility regarding graphic, when waking up from idle mode. I do not think it is related to SD builds only, they handle graphic same way, with same kernels.
By the way in gauner's build I noticed also problem with activating sound from idle mode time to time. So maybe it is not directly graphic driver part, could be somewhere else and this is just consequence.
At the end, it is rare and minor issue, the only discomfort is because of restarting the phone.
Had a few times this issue, and didnt need to reboot to make it worn off. Just put it in a colder environment, and it will go away after 10 minutes orso. So I honestly thing is has todo with the temp of he device. Mostly it came up after a long phonecall I had, which maked the phone a little 'hotter'.
Just a speculation though, didnt have this issue since I use NAND. But I guess it can come-up randomly, but I don't worry it to be honest.
Its happened twice on SD builds and once on NAND build.
I was concerned that I was starting to get a hardware fault but im relieved to hear that others have had it so it must be simply a soft bug.
It rare anyway so no big deal.
Thnx for replies guys.
happened to me once with NAND - sorted with a reset. Scared the hell outa me
F-bone said:
happened to me once with NAND - sorted with a reset. Scared the hell outa me
Click to expand...
Click to collapse
same here, including the scared bit.
sodeknetters said:
same here, including the scared bit.
Click to expand...
Click to collapse
the weird thing is that since I posted in this thread it happened to me twice today!...total 3 times so far... Im getting worried...
Never happened to me with an SD build (after 3 months of use) but happened twice to me with DFT's NAND, reboot fixed it as stated and yes...it scared the **** out of me the first time lol
For anyone that might be debugging the issue - it might be connected with calls.
I receive a call. After I'm done with talking, i turn on phone and it's on negative. Alright, i restart it. After restart it works fine, until i call somebody. After call, again negative screen. It happened two times in a row.
Also i don't really need solution to this problem. Only some kind of workaround that will allow us to fix problem manually without restarting phone. Maybe a script that will reset display driver or something?
Ok guys, I know that there are posts about random reboots but it seems non have a solid solution. My Hd2 has started doing these annoying reboots for about a week. I was using Tyweens NexusHD2 2.9 and all of a sudden reboots started. So I switched to Typhoon CM7 3.5.7(currently on phone now). Reboots still occur. So I did Task 29, wiped sd card, plus clean install of Typhoon CM7 3.5.7. Phone still reboots. It actually rebooted during setup. I even changed from Magldr 150/5(suggested) to 200/45 thinking it was memory related. Still rebooting. I have noticed it does it more when WiFi is on. Is there something with the latest Android 2.3.5 and Wifi? Any help would be greatly appreciated.
beergenius said:
Ok guys, I know that there are posts about random reboots but it seems non have a solid solution. My Hd2 has started doing these annoying reboots for about a week. I was using Tyweens NexusHD2 2.9 and all of a sudden reboots started. So I switched to Typhoon CM7 3.5.7(currently on phone now). Reboots still occur. So I did Task 29, wiped sd card, plus clean install of Typhoon CM7 3.5.7. Phone still reboots. It actually rebooted during setup. I even changed from Magldr 150/5(suggested) to 200/45 thinking it was memory related. Still rebooting. I have noticed it does it more when WiFi is on. Is there something with the latest Android 2.3.5 and Wifi? Any help would be greatly appreciated.
Click to expand...
Click to collapse
did you overclock or undervolt ?
Sent from my HTC HD2 using XDA Premium App
tmotard said:
did you overclock or undervolt ?
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No not at all.
I'm having the exact same problem... but strangely now even when I try older gingerbread builds, it does the same thing. Its only been recently, too... I've had the phone for a while and I don't remember it doing this.
I can have the, same build and same gps libs on my wifes hd2, and hers won't reboot. Mine will.
I even went as far as swapping out my mainboard with another one I had from a cracked screen issue... and that didn't solve the reboots.
I can't figure it out. It must be gingerbread and certain phones. Ive tried 2.3.5, 2.3.4 and 2.3.3 and they all are now rebooting. I don't know why its only been lately, too. The, only thing that solves it for me is running Tytungs NexusHD2 ROM v1.9 Froyo based. I can even add the latest agps fix and don't have any reboots. Only thing I really miss from gingerbread is the DSP bass boost which makes a huge difference for my bluetooth audio via my car.
Remains a frustrating mystery to me.
turn wi-fi sleep policy never
karizman76 said:
turn wi-fi sleep policy never
Click to expand...
Click to collapse
I always set this as my default wifi policy since I am always connected at home. So that's a no-go for that tip. At least for me, personally... still reboots.
So far the only thing that works at home is to turn off 3g.
I am trying Rafdroid 4.2 and so far has not rebooted away from home.
beergenius said:
So far the only thing that works at home is to turn off 3g.
I am trying Rafdroid 4.2 and so far has not rebooted away from home.
Click to expand...
Click to collapse
Rafdroid is a Froyo based ROM - same with the NexusHD2 v1.9g build that I'm using and so far no problems.
But when using any gingerbread (sense or non-sense) / CM7 build, I am getting those random reboots. Sometimes so much to the point where the phone is unusable. Then there are times when I could go hours without any. I thought it was something related to 2.3.5 since that's right around the time things started going strange, but like I noted - I've downgraded to 2.3.4 and 2.3.3 - and the same thing is happening. I used to use Hyperdroid GBX 7 for months without issue... now when I load it, it gives the same result. Same with Hyperdroid GBX v12, Hyperdroid CM7, Typhoon, stock bravo based CM7 Nightlies, AmericanAndroid, NexusHD2 Gingerbread version or anything Gingerbread based - period.
It also seems coincidental that the reboots started right around the time when Tmobile issued a bulletin asking for user input about recent unusual high battery draining with mobile data. I really haven't followed up and I don't know if it was determined what was causing it for some users but I am thinking maybe it could be possibly related. I can't explain why my wife's phone can run the exact same ROM and not experience the same thing yet mine does. It seems like an isolated issue - I don't see a lot of people complaining about the same issue lately. Maybe it has something to do with a specific mainboard revision/manufacturing date and some kind of over sensitivity to mobile data power output or something. As I noted in the prior post, I did switch out the mainboard with another one that I had laying around. I did take note of the revision manufacturing date stamped on the board, and they were identical. And both experience the identical problem. My wife's HD2 was bought 3rd party from a private owner at another time separate from when the 2 HD2's I have on hand were purchased. Perhaps she has a different revision/manufacturing date.
The two mainboards that I am having a problem with have a date of 2010/03/16 - they are both identical.
I would take apart my wife's to check her date and am willing to bet it's something different, but I've had really bad luck picking apart these HD2's the few times that I've done it. I've broken wifi coaxial cables and ripped flex cables. The date is stamped on the bottom of the mainboard.
beergenius said:
So far the only thing that works at home is to turn off 3g.
I am trying Rafdroid 4.2 and so far has not rebooted away from home.
Click to expand...
Click to collapse
mine is the same, the only solution works is to turn off 3G, with all GB ROM I tried
zaq said:
mine is the same, the only solution works is to turn off 3G, with all GB ROM I tried
Click to expand...
Click to collapse
I am wondering if specific phones that run Gingerbread are experiencing this lately because of this:
http://support.t-mobile.com/thread/3544?start=0&tstart=0
Like I noted - perhaps it has something to do with an oversensitivity to 3G mobile data power output, etc.
zaq said:
mine is the same, the only solution works is to turn off 3G, with all GB ROM I tried
Click to expand...
Click to collapse
Same behavior here - had random reboots multiple times per day until I switched to 2G only (only adjustment I made)....have not had one in over 72 hours of uptime now.
Sounds like Bad Blocks to me. Happens to a lot of ppl, me included.
I have 4.
http://forum.xda-developers.com/showthread.php?t=1189544
casemandan said:
Sounds like Bad Blocks to me. Happens to a lot of ppl, me included.
I have 4.
http://forum.xda-developers.com/showthread.php?t=1189544
Click to expand...
Click to collapse
How would bad blocks be the problem if the solution is turning off 3G?
rocklobster702 said:
The two mainboards that I am having a problem with have a date of 2010/03/16 - they are both identical.
I would take apart my wife's to check her date and am willing to bet it's something different, but I've had really bad luck picking apart these HD2's the few times that I've done it. I've broken wifi coaxial cables and ripped flex cables. The date is stamped on the bottom of the mainboard.
Click to expand...
Click to collapse
OK, I can now pretty much confirm my original hypothesis about the mainboard. I have switched it out with one that was manufactured in late 2009 according to the timestamp on the board, and that's eliminated this problem for a while now with Gingerbread entirely.
The exact problem is beyond me, but unfortunately I stick to my guns that it's a hardware issue. Not sure why it would affect Gingerbread so much more than Froyo but my guess would be it has something to so with mobile data power management or something of the sort.
So for those saying that turning 3G off counteracts this rebooting effect, try a good Froyo build to keep your 3G connectivity. The reboots didn't happen nearly as much as they did wile running Gingerbread for me (although I would get 1 or 2 every few days).
Unless you can get your hands on another mainboard... or another phone.
Replacing my HD2 entirely for now wasn't an option for me... it's the only "Android" phone that I can run with the grandfathered 5.99 Tmobile web. Any native Android phone is identified by tmobile from its IEMI and forced to upgrade to a smartphone data plan to work with mobile data. They just happen to allow legacy (less than WP7) Windows Phones work with that old data plan, which is what the HD2 is.
sgalbincea said:
Same behavior here - had random reboots multiple times per day until I switched to 2G only (only adjustment I made)....have not had one in over 72 hours of uptime now.
Click to expand...
Click to collapse
+1 switching to 2g sucks but works,my wifes hd2 works fine though like others have mentioned. this is crazy lol
BTW all these reboots stated for me when to mobile messed up their signals and was causing android phones to have high batt drain.
Where can i switched off 3G beacause i've the same problem with reboots?
Settings networks and mobile network
Sent from my HTC HD2 using XDA App
I have notice mine does it when I am at home using WIFI and 3G is on. If I turn 3G off all is ok. When I am out and about I can turn WIFI off and 3G on and no problems. Wacky.
i had a similar problem on my hd2 tmobile with coredroid 1.6 on it..
Random reboots have become all too often, usually when i start applications and i did not want to waste any more time so I changed the rom...
I would get a random reboot every two our there hours until I took of all my widgets except for two and I haven't had a random reboot in about 2 days and I didn't mess with the 3g signals. but my phone still has battery drain issues
Sent from my HTC HD2 using xda premium