So I had 2 of them since I woke up this morning. One was random, the other was with me checking the task manager settings. I'm starting to think it's a problem with the Task Manager itself. If a program sky rockets with memory out of nowhere and the phone gets stuck and lags trying to maneuver through it, the BSOD comes on.
Wait... BSOD on your EVO 3D?
THAT'S what I was wondering, HUH?????
I have only noticed the black screen of death if I am overclocked. If you are overclocked try bumping down your speed a bit. If you aren't overclocked then I don't know what to tell you.
Sent from my PG86100 using XDA Premium App
Not overclocked whatsoever. Funny thing is when it happens the red charging light comes on, and its not even on the charger. I may just RUU all over.
Sugar, Spice, and everything Nice!!!
Black screen of death is a very big known bug of Android 2.3.3. It was resolved in 2.3.4, so if you see it in 2.3.4 then that's a first.
I flashed the rpm from 2.3.4. Im on 2.3.3 though. Im waiting for viper to update, then we will see.
Sugar, Spice, and everything Nice!!!
I've had it a couple of times. I don't think I've had it yet using 2.3.4. Ill post here if I do
I get it 2 or 3 times a day. It's always random for me though.
I haven't had the black screen of death on either Android version yet.
Sent from my PG86100 using XDA App
dastin1015 said:
Black screen of death is a very big known bug of Android 2.3.3. It was resolved in 2.3.4, so if you see it in 2.3.4 then that's a first.
Click to expand...
Click to collapse
Saying its resolved on 2.3.4 is a bit premature seeing as though we can't overclock on 2.3.4 yet. Overclocking for me leads to a black SOD without question. Which I don't get. On temp root I could overclock fine without issue.
Sent from my PG86100 using Tapatalk
Don't forget to make sure your sdcard and emm3 readaheads are default
sdcard at 1024, emm3 4096
I will black screen, run away process every time if my read aheads are cranked up at all
aramova said:
Don't forget to make sure your sdcard and emm3 readaheads are default
sdcard at 1024, emm3 4096
I will black screen, run away process every time if my read aheads are cranked up at all
Click to expand...
Click to collapse
How would I do that?
Edit: Oh snap, your from West Palm Beach also? I thought I was the only Palm Beach guy in the 3D forums.
felacio said:
Saying its resolved on 2.3.4 is a bit premature seeing as though we can't overclock on 2.3.4 yet. Overclocking for me leads to a black SOD without question. Which I don't get. On temp root I could overclock fine without issue.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I have the HTC Hero and the BSOD was common on all devices using 2.3.3, it is not specific to the Evo 3D. Google's bump up to 2.3.4 solved it for all devices as well as adding some features.
Related
I'm a little hesitant re-flashing Gingerbread because of the little scare we had, but I hear that now just two people got bricked.
So how many of you are back on Gingerbread?
I am. It has always ran really good for me. I'm using gingivitus IX. The only problem I have with this Rom is that the battery takes forever to charge. No other complaints.
Sent from my ADR6400L using Tapatalk
I'm using no-frills CPU to Overclock. I have HTC inspire 4g running coredroid 6.6 what would be a good starting point for my
Min. Clock freq? And my max clock freq? And also what do the freq's do? Help please trying to get the most out.
Also if someone would explain what the governers are....
Smartass
Interactive
Conservative
Userspace
Ondemand
Performance
Help pleas
Sent from my Desire HD using XDA App
And also what is the correct way to use a different kernel than the one that is in the ROM? I have the ext4 wipe. Not used it. I just clear everything from recovery mode.
Basically what's the correct way to flash a new kernel?
Sorry for the double post.
Sent from my Desire HD using XDA App
Sent from my Desire HD using XDA App
yatyas2141 said:
And also what is the correct way to use a different kernel than the one that is in the ROM? I have the ext4 wipe. Not used it. I just clear everything from recovery mode.
Basically what's the correct way to flash a new kernel?
Sorry for the double post.
Sent from my Desire HD using XDA App
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Wrong forum....
>--The Game--<
superchilpil said:
Wrong forum....
>--The Game--<
Click to expand...
Click to collapse
Hahaha, yeah I know seriously.
I'm going in
Flashed GB successfully last night then flashed back to Fro ...on GB now so far so good DAS BAMF rom... HTC Thunderbolt rooted...
Tbolt101 said:
Flashed GB successfully last night then flashed back to Fro ...on GB now so far so good DAS BAMF rom... HTC Thunderbolt rooted...
Click to expand...
Click to collapse
I just flashed that and I'm loving BAMF 2.0 Remix.
Is there any news on GB radio causing bricks I would like to try it. The firdt post said it was only two phones that got bricked.
wooddale said:
Is there any news on GB radio causing bricks I would like to try it. The firdt post said it was only two phones that got bricked.
Click to expand...
Click to collapse
I heard that it was just two phones out of thousands, but I don't know that's a risk you take every time you flash anything.
wooddale said:
Is there any news on GB radio causing bricks I would like to try it. The firdt post said it was only two phones that got bricked.
Click to expand...
Click to collapse
After I flashed GB to my phone my wife left me, dog ran away, and I got pregnant, twice.
Hasn't phased me though. Flashing LiquidGingerSense tonight, just because.
Sent from my super duper deluxe rooted re-romed Thunderbolt. ( and yes, it can also wash my car AND do the dishes)
I was hearing from Jcase that it was more than just a few phones
I heard around 30 were bricked, but considering how many TB's there are out there, not a bad ratio. How many of those 30 were caused by user error?
Hey, lovin my TB! recently after returning from TB back to fresh rooted froyo, everything's been ok. Then I flashed bamf 1.7 fine. Stripped version getting shut offs, not reboots.. I don't notice till I reach in my holster and the HTC logo appears. I thought it might be the rom so I flashed cm7.0.0 RC. Still getting them. Is anyone else getting these? This is serious considering i almost woke up late today after setting my alarm last night only to find my phone is turned off.
Sent from my ThunderBolt using XDA App
I'd start by checking kernel settings. Too low won't wake. Too high will cause a shut off. Not all processors respond well to extreme over/under clocking and under voting.
Sent from my ADR6400L using XDA Premium App
keith.mcintyre26 said:
I'd start by checking kernel settings. Too low won't wake. Too high will cause a shut off. Not all processors respond well to extreme over/under clocking and under voting.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I actually have not touched the kernel nor the radio.. but I'm wanting Netflix so I'm going to have to flash the gb radio I think. As for the kernel it is the one that came with cm7, the highest clocking is around 1ghz. I guess ill show around for a decent kernel.
Sent from my ThunderBolt using XDA App
shut off fix worked for me
I was having the exact same problem and I flashed the new cdma radio and the old LTE radio combo and I have not had a problem since.
here is the line to the thread where I got the radios from:
http://forum.xda-developers.com/showthread.php?t=1045081
alluzzion2o9 said:
I actually have not touched the kernel nor the radio.. but I'm wanting Netflix so I'm going to have to flash the gb radio I think. As for the kernel it is the one that came with cm7, the highest clocking is around 1ghz. I guess ill show around for a decent kernel.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
Most likely the dumb radio then..last couple radio releases have reboot issues depending on the person...seems your an unlucky one too.
n0vemberrain86 said:
I was having the exact same problem and I flashed the new cdma radio and the old LTE radio combo and I have not had a problem since.
here is the line to the thread where I got the radios from:
http://forum.xda-developers.com/showthread.php?t=1045081
Click to expand...
Click to collapse
Ill give it a try. Thanks for the link.
EDIT: as an update. So i reached 24hrs without a single shutdown. I flashed cm7 dream kernel 1.8 and one of the radios from above link.. only question is the types of signals of each combo from the link looks like hyroglyphs to me.. which is the recommended radio running cm7?
Sent from my ThunderBolt using XDA App
In the past two weeks I have used Gingeritis, Bamf 2.0 and Gingerbean using the latest updated imoseyon kernel. I am currently using the latest Gingeritis with imoseyon 3.0.1 and the MR2 radio that was just leaked.
There is one lingering issue that is uniform throughout all updates and changes of roms/kernels/radios. Charging time/speed.
After a new Rom install, charging is just how it should be. Then, after a phone call the charging time becomes extremely slow or even sometimes stops at a certain percentage. The only way to fix this is a reboot.
Anyone able to explain what in the GB OS and/or kernels is causing this?
Sent from my ADR6400L using XDA Premium App
I can't, but I promise you the search button can
joshnichols189 said:
I can't, but I promise you the search button can
Click to expand...
Click to collapse
Dide come on...he just had a simple question. You didn't have to blast him like that.
Simple question != Dev thread
sent via telepathy
This was in my backyard today.
Sent from my ADR6400L using XDA Premium App
KGBxxx said:
This was in my backyard today.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
You need to ****ing move now.
Sent through the interwebs.
Mudavo said:
In the past two weeks I have used Gingeritis, Bamf 2.0 and Gingerbean using the latest updated imoseyon kernel. I am currently using the latest Gingeritis with imoseyon 3.0.1 and the MR2 radio that was just leaked.
There is one lingering issue that is uniform throughout all updates and changes of roms/kernels/radios. Charging time/speed.
After a new Rom install, charging is just how it should be. Then, after a phone call the charging time becomes extremely slow or even sometimes stops at a certain percentage. The only way to fix this is a reboot.
Anyone able to explain what in the GB OS and/or kernels is causing this?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Same here and I have searched and can't find solution .
Same here - also no solution upon searching. Back to Froyo BAMF 1.7 until someone finally addresses this...
gramsey1911 said:
Dide come on...he just had a simple question. You didn't have to blast him like that.
Click to expand...
Click to collapse
It was kind of harsh I'm sorry but it's talked about a lot in the rom threads
Sent from my ThunderBolt using XDA Premium App
yep.. charging time is definitely an issue.. I wonder if it has anything to do with the kernel.
I must have been lucky then, because after i flashed the MR2 radio, all that BS went away. Now I have super fast charging and it goes to 100%
It is a slight hassle, but there is a fix for it right now. When your phone is plugged in and charging, restart it while keeping the cord in. It should charge normally after it restarts. I've had the same issue and this makes things act normal. However, you need to do this every time you charge, not just once.
Why aren't developers asking for help on fixing this?
Why's everyone so mum about the issue?
This is starting to drive me nuts.
I know you reboot to fix it but , what specificly is causing it??
I mean when you think about it. Wouldn't killing the process whatever it may be, that kicks in when you get a call fix it?
Is anyone still having lag issues?? I've been using blade buddy and even that touch screen app for the galaxy!!! My screen is starting to come unresponsive at times!! I'm so tempted to take this phone back....any help?;
Sent from my PG86100 using XDA Premium App
Chauleyboii said:
Is anyone still having lag issues?? I've been using blade buddy and even that touch screen app for the galaxy!!! My screen is starting to come unresponsive at times!! I'm so tempted to take this phone back....any help?;
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
lag issues? i'm not familiar with blade buddy or that touch screen app for galaxy.
i haven't done anything *too* intensive on the phone but i have rarely experience any type of lag on this device. the lack of lagging has been very impressive to me.
if you are on the stock ROM and kernel and still experiecing lag, based on my personal experience, you might want to look into taking it back for an exchange as it could be a hardware issue.
if you don't experience the lag on a stock ROM and kernel, it might be whatever custom ROM or kernel you're using has an issue or bug. if you're on a custom ROM/kernel, also good to check in those specific threads to see if anybody else has reported a similar issue so the dev knows to look into it and resolve.
hope that helps!
Yea when I first got the phone the xda east major laggy and that's before I rooted so I guess I need to take it back then cuz this sucks...since I rooted its been flawless but couple days later the lag would come back and now my screen is becoming unresponsive at time for like 2-3 secs!!!
Sent from my PG86100 using XDA Premium App
Chauleyboii said:
Yea when I first got the phone the xda east major laggy and that's before I rooted so I guess I need to take it back then cuz this sucks...since I rooted its been flawless but couple days later the lag would come back and now my screen is becoming unresponsive at time for like 2-3 secs!!!
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
yea. as a last resort test, i'd flash everything back to stock and run it for a day. see if its still laggy. if it is still laggy, find good examples of when it lags so when you take it back, you can show the person how laggy it is through the examples.
hopefully you can swap out for a device w/no issues!
joeykrim said:
yea. as a last resort test, i'd flash everything back to stock and run it for a day. see if its still laggy. if it is still laggy, find good examples of when it lags so when you take it back, you can show the person how laggy it is through the examples.
hopefully you can swap out for a device w/no issues!
Click to expand...
Click to collapse
Ok koo I guess i shouldn't show the xda app to them since its a developer site right?? Even tho they can't prove I rooted it but just wandering??
Sent from my PG86100 using XDA Premium App
Chauleyboii said:
Ok koo I guess i shouldn't show the xda app to them since its a developer site right?? Even tho they can't prove I rooted it but just wandering??
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
lol yea, given the unknown area rooting a device currently sits from a legal standpoint, i'd avoid anything related to rooting the device as a prime example.
ideally, if you're experiencing lag on the device, it will occur frequently in common tasks like making/ending a phone call or moving between text messages or moving between menus in the settings screen, etc. it makes the best case for having an issue when you're able to demonstrate it lags during normal routine operations.
hope that helps!
joeykrim said:
lol yea, given the unknown area rooting a device currently sits from a legal standpoint, i'd avoid anything related to rooting the device as a prime example.
ideally, if you're experiencing lag on the device, it will occur frequently in common tasks like making/ending a phone call or moving between text messages or moving between menus in the settings screen, etc. it makes the best case for having an issue when you're able to demonstrate it lags during normal routine operations.
hope that helps!
Click to expand...
Click to collapse
Right on joey appreciate it bro ill see hoe it acts when I return back to stock .....are you still developing?? I'm pretty sure I seen you around the evo 4g forums I think
Sent from my PG86100 using Tapatalk
Chauleyboii said:
Right on joey appreciate it bro ill see hoe it acts when I return back to stock .....are you still developing?? I'm pretty sure I seen you around the evo 4g forums I think
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
hah yea. working on mainly two small apps on the market, root check and flashimagegui. pondering publishing the completely stock ROM with root, busybox and some developer tools i use on my personal device (as I did publish this on the evo and it was decently popular - might be where you saw my name). also, trying to help out (give back) in the q&a boards when i can!
if you find some good common tasks which cause the device to lag, post them back here as people with the same or similar issues might find this thread through searching and it'll give them some rough benchmark to compare against.
i've yet to see this device lag through any common tasks i run. previous android phones ive had would experience lag so this device has definitely impressed me!
joeykrim said:
hah yea. working on mainly two small apps on the market, root check and flashimagegui. pondering publishing the completely stock ROM with root, busybox and some developer tools i use on my personal device (as I did publish this on the evo and it was decently popular - might be where you saw my name). also, trying to help out (give back) in the q&a boards when i can!
if you find some good common tasks which cause the device to lag, post them back here as people with the same or similar issues might find this thread through searching and it'll give them some rough benchmark to compare against.
i've yet to see this device lag through any common tasks i run. previous android phones ive had would experience lag so this device has definitely impressed me!
Click to expand...
Click to collapse
NICE BRO REAL NICE!!! I was looking into making apps but man it look so complicated and indeed I will do that for you so far the stock is running nice I'm using tapatalk instead the the regular xda AOL this time and tapatalk is scrolling flawlessly so far but ill give it til tomorrow to see how things get
Sent from my PG86100 using Tapatalk
Chauleyboii said:
NICE BRO REAL NICE!!! I was looking into making apps but man it look so complicated and indeed I will do that for you so far the stock is running nice I'm using tapatalk instead the the regular xda AOL this time and tapatalk is scrolling flawlessly so far but ill give it til tomorrow to see how things get
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
i put mine back to stock and my screen well freeze or lag couple times a day and i have to hit power button to put it to sleep and wake it back up to stop it from doing that and that last only a couple hours.
I am running CM7 pre-beta #2 on Faux 1.6. Underclocked to 600mhz today and undervolted -75 at that speed.
Today on a few occasions my keyboard started acting odd. I was typing a text message and noticed that keys were being "pressed" while my finger was still 1/4 to 1/2 inch from the screen over or near those keys (Q and W mostly)
Anyone else had that happen before? Any idea as to what could be causing it? undervolt, underclock, kernel, rom, ghosts, gnomes?
Xirta said:
I am running CM7 pre-beta #2 on Faux 1.6. Underclocked to 600mhz today and undervolted -75 at that speed.
Today on a few occasions my keyboard started acting odd. I was typing a text message and noticed that keys were being "pressed" while my finger was still 1/4 to 1/2 inch from the screen over or near those keys (Q and W mostly)
Anyone else had that happen before? Any idea as to what could be causing it? undervolt, underclock, kernel, rom, ghosts, gnomes?
Click to expand...
Click to collapse
Ghosts
Sent from my MB860 using XDA Premium App
Xirta said:
I am running CM7 pre-beta #2 on Faux 1.6. Underclocked to 600mhz today and undervolted -75 at that speed.
Today on a few occasions my keyboard started acting odd. I was typing a text message and noticed that keys were being "pressed" while my finger was still 1/4 to 1/2 inch from the screen over or near those keys (Q and W mostly)
Anyone else had that happen before? Any idea as to what could be causing it? undervolt, underclock, kernel, rom, ghosts, gnomes?
Click to expand...
Click to collapse
Make a poll. But yeah is it refurbished? If it is maybe the guy who owned it before you got into a horrific accident and his wife got it back and sent it in to get replaced. That could be the cause of the paranormal activity.
Who you gonna text?!?!
---
- adb push iPad2post.apk to /forum/thread
I had that problem on the aura rom, flashed kens alien rom haven't had it since.
Sent from my MB860 using XDA Premium App
Been having the same issue on and off for a couple of weeks.
The longest it has remained stable is 3 days.
After running through the nandroid backups, sometimes this works, I fastboot back to 1.8.3.
If that doesn't work I SBF to a random build, have never used the firmware OTA so have never bricked. Then keep playing with them till voila everything returns to stability. Can take a while though.
I have tried different ROM's, searched this and every other forum, uploading editing pds files, posted here twice on 2 different forums.
Good luck in working it out as it seems I can't.
Those three days of stability ? That ended today and I am on back up no.3 so about to start the fastboot route.
Fixed.
Sgs Screen Booster from the Market has done the job.
Can't remember who suggested it but worked a treat!
Sent from my MB860 using XDA App
Andy_Thatcher said:
Fixed.
Sgs Screen Booster from the Market has done the job.
Can't remember who suggested it but worked a treat!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
What settings did you use for the app?
Sent from my MB860 using XDA Premium App
I went with Super Optimized.
Rebooted did it again and have been fine ever since.
Sent from my MB860 using XDA App
I've had this exact same problem and SGS Booster appears to have fixed it! I'll report back if it stops working again, flashing a new ROM made the problem go away for a while, but it came back.
Edit: Nope, it came back.
TheBassman369 said:
Who you gonna text?!?!
---
- adb push iPad2post.apk to /forum/thread
Click to expand...
Click to collapse
Ghostbusters!!!
---