Hello,
I'm experiencing a weird issue, and searching this (and other forums) has not been of any help.
Regardless of the base rom, radio, HSPL or Android build, I keep experiencing the same problems.
My phone will simply not "wake up" randomly after going to "sleep mode".
After pressing any of the hard buttons, I can see them light up, and plugging the USB in or out will definitely make my PC Recognize the phone, so I know it's definitely "working", just the screen won't light up.
At the moment:
I have a (standard) german HTC HD2 (T-Mobile).
- Flashed with HSPL 2.08
- Radio Leo_RADIO_2.12.50.02_2
- Running Chucky's Base ROM : ChuckyDroidROM 23148 ~ 3.14
- Android Build: Motoman234 EVO Black&Blue (V0.3)
Any help will be greately appreciated!
Thank you!
PS: Also I have a Class 6 4GB SD Card (Formatted with the "official SD" Formatter!)
My phone has same issues, I stay tuned, maybe someone has a solution.
Kraion said:
Hello,
I'm experiencing a weird issue, and searching this (and other forums) has not been of any help.
Regardless of the base rom, radio, HSPL or Android build, I keep experiencing the same problems.
My phone will simply not "wake up" randomly after going to "sleep mode".
After pressing any of the hard buttons, I can see them light up, and plugging the USB in or out will definitely make my PC Recognize the phone, so I know it's definitely "working", just the screen won't light up.
At the moment:
I have a (standard) german HTC HD2 (T-Mobile).
- Flashed with HSPL 2.08
- Radio Leo_RADIO_2.12.50.02_2
- Running Chucky's Base ROM : ChuckyDroidROM 23148 ~ 3.14
- Android Build: Motoman234 EVO Black&Blue (V0.3)
Any help will be greately appreciated!
Thank you!
PS: Also I have a Class 6 4GB SD Card (Formatted with the "official SD" Formatter!)
Click to expand...
Click to collapse
First this is absolutely the WRONG section to post this in. If you had "searched" this thread you wouldve seen that thier is a Q&A section where this belongs. Anyway the black screen of death has been a problem for many people for a long time. There hasn't really been a true "fix" for the problem. the closest thing is that it might be caused by automatic brightness so disable that. Mine was cured by changing radios. Also changing winmo rom isnt a bad idea but if none of that works than theres really nothing that can be done....but that doesnt mean post such unnecisary threads in the DEVELOPMENT thread to try and get a quick fix.
It is your radio, I posted this in my thread replying to someone else that has this problem. Update to 2.14 or 2.15. I haven't had this issue on any build in months (including mine).
@JRip777, No worries, I'm immune to the "Didn't you search" flame, that's classic =)
And yes, I DID Search, and if you go ahead and give it a try, you end up with HUNDREDS of posts that say little to nothing about this particular issue.
And according to the other posts here so far, this does seem to be an issue developers should maybe look into.
I hadn't tried the brightness setting, I will try that and will post here with results.
@Motoman234, 1st: thanks for the great work on your ROM =)
And Yes, I also assumed it was the radio, I tried four different radios today, all with the same results, the one that seemed to work well the longest was 2.12.50.02_2, 2.14 and 2.15 both will end up in the "black screen of zombieness" quite fast.
Somehow I'm beginning to think this issue has to do with the G-Sensor....
Kraion said:
@JRip777, No worries, I'm immune to the "Didn't you search" flame, that's classic =)
And yes, I DID Search, and if you go ahead and give it a try, you end up with HUNDREDS of posts that say little to nothing about this particular issue.
And according to the other posts here so far, this does seem to be an issue developers should maybe look into.
I hadn't tried the brightness setting, I will try that and will post here with results.
@Motoman234, 1st: thanks for the great work on your ROM =)
And Yes, I also assumed it was the radio, I tried four different radios today, all with the same results, the one that seemed to work well the longest was 2.12.50.02_2, 2.14 and 2.15 both will end up in the "black screen of zombieness" quite fast.
Somehow I'm beginning to think this issue has to do with the G-Sensor....
Click to expand...
Click to collapse
Well the only thing is, is if it was the G-sensor then mostly everyone would have it. Out of the 2000 download's from V0.3, only two have mentioned this (including you). The only thing I can think of is your SD card. Last time I tried a class 6 instead of the stock class 2 it was horrible for me. I don't understand why because it should be better but I have heard a lot of people say the same thing. I can almost promise that if you tried a different one (freshly formated) that you wouldn't have this problem. Do you still have the stock class 2 that you can test it out on? I really hope you can solve this because I know it is one of the most annoying problems ever. If you need any help with anything at all just PM me.
Kraion said:
@JRip777, No worries, I'm immune to the "Didn't you search" flame, that's classic =)
And yes, I DID Search, and if you go ahead and give it a try, you end up with HUNDREDS of posts that say little to nothing about this particular issue.
And according to the other posts here so far, this does seem to be an issue developers should maybe look into.
I hadn't tried the brightness setting, I will try that and will post here with results.
@Motoman234, 1st: thanks for the great work on your ROM =)
And Yes, I also assumed it was the radio, I tried four different radios today, all with the same results, the one that seemed to work well the longest was 2.12.50.02_2, 2.14 and 2.15 both will end up in the "black screen of zombieness" quite fast.
Somehow I'm beginning to think this issue has to do with the G-Sensor....
Click to expand...
Click to collapse
My point was not to shun you for not searching first. While it seems that you didnt because I read TONS of posts regarding the same issue followed by TONS of other people reply how they fixed there BSOD issues. I see these TONS of posts and replies and IM NOT EVEN LOOKING FOR THEM. My point was to let you know this is 100% the wrong place to ask this question. thats all I wasn't rude. I told you what fixed my BSOD issues and what Ive read from tons of other people. But there is a very good reason why we have a question and answer thread specifically for android. If everybody just posted whatever they wanted to wherever they wanted to this forum would be an absolute disaster. Anyway I hope you get your answer.
motoman234 said:
Well the only thing is, is if it was the G-sensor then mostly everyone would have it. Out of the 2000 download's from V0.3, only two have mentioned this (including you). The only thing I can think of is your SD card. Last time I tried a class 6 instead of the stock class 2 it was horrible for me. I don't understand why because it should be better but I have heard a lot of people say the same thing. I can almost promise that if you tried a different one (freshly formated) that you wouldn't have this problem. Do you still have the stock class 2 that you can test it out on? I really hope you can solve this because I know it is one of the most annoying problems ever. If you need any help with anything at all just PM me.
Click to expand...
Click to collapse
Yes, I have the class 2, tried it, same issue, also a class 4, all have the same problem. =/
And I always format them with this : http://www.sdcard.org/consumers/formatter/
I wish I had more to offer to pinpoint the issue, I did read the WHOLE thread of your rom, and I did find that only one other person is having the issue, I'm beginning to think it might be a hardware problem, I'll have my phone replaced and will post again if that fixed the issue.
I thought this think doesn't exist anymore
Reading today news about new build fromm dell, I decided to check if there are still "too many redirects" errors on my streak build 12332 with performance fix and HSDPA and I was suprised that they are in some magical way gone, I tried so far modaco.com, msn.com, xda-developers.com and some other websites which were reported as problematic to open and they are absolutely all working, even did a reboot and still working, previously the only one way to open them was using 2G or wifi
So can somebody test that as well and/or provide me some websites which cannot be open?
cheers
Mine are still there, BUT I remember this happened to me on 1.6 - during the first weeks I regularly got "too many redirects..." errors, and suddenly they were goneand NEVER came back. I am not THUS religious, but...
Can you tell me what other webistes than which I tried you have a problem?
yes this update fix web redirect error.
i just update from 309000 to 12821
now no problem at all.
for what's its worth i only ever got the redirects on wifi, never data....
apparently the 'new' release sovles (318) solves the redirects issue, not sure how the old build could of fixed itself...
my €0.02 (well £0.02 actually), custom ROM all the way... if official releases were so great then they'd be no XDA...
a good example is fring
if you go official & wanna use fring then you need to keep 2.1
if you go for an earlier 2.2 custom rom, then you can have fring & flash
imHo, if you don't go for froyo & get flash, then you may as well be on winmo or apple
flash is the usp of droid
sorry my mistake, for some reason I was thinking today that the problem exists on my streak on 3g only, but it still exists only via wifi
....I think I have to sleep more....
Sorry for that silly thread
I had the "too many redirects" problem on both wi-fi and 3G.
I too have not had the issue for several days. I used to reboot my phone every morning when I woke up but it's been running for a week w/o a reboot. (*looking for a piece of wood to knock on!*)
Hey guys!
Nice to post here, you all are really good at this, that's why i'd like to ask you anything that's being a headache these days.
I ran the WP7 Moonlight rom on my HD2 properly last week. I've been using it for a couple of days and everything works fine, except the jailbreak thing.
I read that the Moonlight already contains the hack but it actually doesn't work for me. I've been trying to hack it by the famous chevronwp7 method (I followed all the steps, little by little, from even 4 differents guides) and no success at all... it says "check the USB ... check zune open... blablabla" I read lots of posts on here about this issue and none of the answers worked for me.
The main reason because I want to hack it is to stop the battery problem that makes my phone last less than 20 hours (I have 3G disconnected most of the time to prevent this but it doesn't make much!!). I've read that i could arrange this by editing the registry.
I think everything would be fine if I could hack the phone...
Any ideas?
Thanks!!!!!!
Hello all.
I got this phone, a month ago, for a few hours to fidddle.
Never made myself to ask following on the forum :
When it starts, it says there is no network of course.
To install roms and all that, I read that I should get past the setup and turn on debugging or something like that.
But I can not get past the screen.
I remember reading around few hours but I couldn get anywhere before turning something in the menu...which I could not get to
Can I flash something to get it removed ?
Sorry it all looks uncertain now...but maybe someone had similar problem ....
sorry there is a post about this should have searched..please lock topic ..
I need your help guys. Been on here for years, rooted every phone I have ever owned (multiple carriers). Self taught through trial and error and reading threads on here. But I have now ran into an issue that I have never seen or heard of and cant seem to find something on here to help. A friend of mine has Verizon Galaxy S5 and recently had to replace it through the insurance plan he had on it from Verizon. He had been complaining for a while and has finally agreed to let me take a look and see if I can fix it. I HAVE TRIED EVERYTHING!!! (that I can think of). This is extremely frustrating. Below ill list the issues and things Ive tried.
Issues:
Operating system crashes
Rebooting on its own
Wont load up when turned on
Apps crashing
Battery wont last long
and general "Jankyness" haha (seriously though)
These issues are constant issues meaning all happen constantly throughout the day and night.
I have tried multiple factory resets through the settings and through stock recovery
Just tried using Odin to fix this aaaannndddd NNOOO GO!!! 8-O
i have used Odin many times, never seen it not work like this. If anyone has an explanation for this and a recommended solution that would be great!! Thanks all for reading this and hopefully I can help my friend.
pockermj said:
I need your help guys. Been on here for years, rooted every phone I have ever owned (multiple carriers). Self taught through trial and error and reading threads on here. But I have now ran into an issue that I have never seen or heard of and cant seem to find something on here to help. A friend of mine has Verizon Galaxy S5 and recently had to replace it through the insurance plan he had on it from Verizon. He had been complaining for a while and has finally agreed to let me take a look and see if I can fix it. I HAVE TRIED EVERYTHING!!! (that I can think of). This is extremely frustrating. Below ill list the issues and things Ive tried.
Issues:
Operating system crashes
Rebooting on its own
Wont load up when turned on
Apps crashing
Battery wont last long
and general "Jankyness" haha (seriously though)
These issues are constant issues meaning all happen constantly throughout the day and night.
I have tried multiple factory resets through the settings and through stock recovery
Just tried using Odin to fix this aaaannndddd NNOOO GO!!! 8-O
i have used Odin many times, never seen it not work like this. If anyone has an explanation for this and a recommended solution that would be great!! Thanks all for reading this and hopefully I can help my friend.
Click to expand...
Click to collapse
if your friend's S5 is running OE1, you're out of luck:
http://forum.xda-developers.com/verizon-galaxy-s5/help/downgrade-oe1-t3149085/post61730480
if this replacement phone has been malfunctioning since he got it, I'd raise a ruckus with Verizon.