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!!!
---
Related
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
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.
So I managed to get my phone back up and running... to a degree... but it is randomly locking up and rebooting when being used randomly. It seems like its an overclock problem where if your trying to push it too hard it locks and reboots but I'm having this problem on complete stock with no oc or uv. Any suggestions?
What happened to your phone? What rom and kernel are you running?
It just randomly started doing what I described in my prior post. Its doing it on every Ron and kernel combo I use, including stock...
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
It just randomly started doing what I described in my prior post. Its doing it on every Ron and kernel combo I use, including stock...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Well...it sounds like you might have to odin back to stock and see about getting a replacement from your carrier.
That's no issue I've ever heard of :/
So, recently, my touch screen has been pretty wonky. Sometimes it doesnt work at all and even pulling the battery and booting it back up doesn't fix it. Sometimes when it locks The screen isn't responsive afterwards to unlock but then locking and waking the screen again fixes it. Just wondering if there is a fix for this or if anyone else has had these same problems. I've trued full CWM wipes and Fastboot wipes and also tried different ROMs. Any help would be cool but if not I may just have to ditch the MAtrix for a different phone until my upgrade.
What is your phone currently running at the moment?
Sent from my Atrix with XDA Premium App
redhawk79 said:
So, recently, my touch screen has been pretty wonky. Sometimes it doesnt work at all and even pulling the battery and booting it back up doesn't fix it. Sometimes when it locks The screen isn't responsive afterwards to unlock but then locking and waking the screen again fixes it. Just wondering if there is a fix for this or if anyone else has had these same problems. I've trued full CWM wipes and Fastboot wipes and also tried different ROMs. Any help would be cool but if not I may just have to ditch the MAtrix for a different phone until my upgrade.
Click to expand...
Click to collapse
this happens to me on stock android 2.3.4.. when im charging the phone the slide to unlock goes dead i use the botton then works ... im in Dom. Rep.
antmiu2 said:
when im charging the phone the slide to unlock goes dead
Click to expand...
Click to collapse
I got the same issue, when charging my Atrix, touchscreen won't work.
I'm running CM9 alpha6 by Jokersax
For those having issues while charging, make sure you are using a motorola charger. Please give results back.
Sent from my Atrix with XDA Premium App
Voelker45 said:
What is your phone currently running at the moment?
Sent from my Atrix with XDA Premium App
Click to expand...
Click to collapse
I'm running CM7 Ba2tF from the atrix dev team with the kernel that comes with it. No other tweaks other than that.
redhawk79 said:
I'm running CM7 Ba2tF from the atrix dev team with the kernel that comes with it. No other tweaks other than that.
Click to expand...
Click to collapse
Have you tried any blur ROMS to make sure it isnt the phone?
Sent from my Atrix with XDA Premium App
Voelker45 said:
Have you tried any blur ROMS to make sure it isnt the phone?
Sent from my Atrix with XDA Premium App
Click to expand...
Click to collapse
So, I've been using the Wet Dream blur ROM for the past week and it's acting about the same way. I haven't had to go to the extreme of wiping it yet while on Wet but unresponsiveness is still a problem here and there.
EDIT: I haven't had touch capability since the 10th. I've tried flashing a couple other ROMs to no avail and don't really know what to do at this point.
Is a warranty claim even possible or would it just be a futile effort?
EDIT II: Sent it in on a warranty claim. We will see what happens I suppose. If not, I'm going GSII
EDIT The Third: Well, after fruitcake back to stock I sent it in and they fixed it all up and sent it back to me. So, that's that for what it's worth. Like the sig says my MAtrix got stolen so I'm on to the GSII forums but I'm definitely going to keep up with what's going on with Atrix.
After use for a while....the screen gets real unresponsive. To the point where if I try to scroll down on FB...it will actually register a click instead of a swipe and open up the picture I happen to swipe over.....anyone else???
Galaxy S III I747
fmllc said:
After use for a while....the screen gets real unresponsive. To the point where if I try to scroll down on FB...it will actually register a click instead of a swipe and open up the picture I happen to swipe over.....anyone else???
Galaxy S III I747
Click to expand...
Click to collapse
This only happens to me when I'm trying to use my phone while it is plugged in and charging. It acts all crazy, but once I unplug it the thing works fine. I pretty much keep my phone in ECO mode and haven't switched that off to see if it makes a difference.
Same here. I keep my phone on ECO mode and have no issues with responsiveness, except for once in a while when it's plugged in and charging.
Sent from my LG-E970 using XDA Premium HD app
That's horse ****! Someone has to come up with a fix for this! Doesn't eco mode cap the processors at 1.1 or something?
LGOG E970
Seems cycling the screen off and back on will get rid of the lag....until it happens again....lol
LGOG E970
I don't have that problem at all with mine. I am unlocked, rooted and running Notach's Base ROM.
jamesc760 said:
I don't have that problem at all with mine. I am unlocked, rooted and running Notach's Base ROM.
Click to expand...
Click to collapse
I DO have that problem with mine. I am unlocked, rooted and running nottach's Base ROM the problem has reoccurred with the stock ROM and versions 0.5, 0.6.5 and 0.7.3 .
It's probably a kernel-level memory or CPU issue because for most people it appears to be a specifically time-based problem. The longer your uptime is, the worse the problem gets. Reboot your phone and the problem goes away for awhile.
Sent from my LG-E970 using xda app-developers app
Have you tried restarting your phone lol. I've never lagged once.
Sent from my LG-E970 using xda app-developers app
amrando said:
I DO have that problem with mine. I am unlocked, rooted and running nottach's Base ROM the problem has reoccurred with the stock ROM and versions 0.5, 0.6.5 and 0.7.3 .
It's probably a kernel-level memory or CPU issue because for most people it appears to be a specifically time-based problem. The longer your uptime is, the worse the problem gets. Reboot your phone and the problem goes away for awhile.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Amrando, inflammatory and unhelpful statements aren't going to win you any help with your problems. It's just alienating those that would otherwise help you out and gets you reported to the mods.
Sent from my LG-E970 using xda premium
amrando said:
I DO have that problem with mine. I am unlocked, rooted and running nottach's Base ROM the problem has reoccurred with the stock ROM and versions 0.5, 0.6.5 and 0.7.3 .
It's probably a kernel-level memory or CPU issue because for most people it appears to be a specifically time-based problem. The longer your uptime is, the worse the problem gets. Reboot your phone and the problem goes away for awhile.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I've edited your post. This is a great example of the same phone, running a similar set up behaving completely different. The user you quoted wasn't doing anything other than stating that they don't have this problem so chill out a little and accept that each person can have a different experience and opinion. If you've got nothing useful to say, say nothing.
Thanks
AvRS