Database Develop

Touch Screen Issues

I have a stock N1, updated to Froyo. So every now and then, ever since I got the phone, the screen just stops responding when waking it up. Sometimes, the screen doesn't turn on at all, but the soft buttons light up. And the only way I've found to fix the problem is to either restart the phone, or connect it to my USB.
Was wondering if it's a hardware or software issue?

same thing happening to me aswell...seems to be only since Froyo flash. Really crappy when you are trying to show off the phone and you have to reboot first. Im gonna mess around a bit tonight and see if I figure anything out...Im also not getting any trackball notifications... I think its software related, for now.

I can say it's not Froyo since I've had this problem before the update, unfortunately.

mailliw320 said:
I can say it's not Froyo since I've had this problem before the update, unfortunately.
Click to expand...
Click to collapse
Ok some weird stuff going on for sure..
With CM 5.0.6 every couple days I would the keyboard would "uncalibrate", but the screen would never freeze up.
Since installing Froyo I am getting the freezing and unresponsive screen at least once a day.
Lets hope my it is not my screen getting worse. Ill have to flash back to CM 5.0.6 and see if I still get freezing.
Bye bye Froyo, see you in a couple days!!

So...anyone else with this issue pre-Froyo?

ive never had my nexus freeze, then i flashed froyo and that day it froze for about a minute, now it has done the hard sleep thing and it does it more times per day each subsequent day.
I know that we have an early "test" version of froyo so this stuff isnt grave, but since there seem to be groups of people experiencing different issues, i also wonder if its possible that specific apps can cause problems unrelated to the app since they arent really ready for froyo...is that possible and does anyone know of apps to beware of? not so much apps that dont work but apps that cause other problems?
Edit: my phone is stock by the way

i used to have a lot of problems when i switched from landscape to portrait mode with the calibrations but since ive put on 2.2 that problem is long gone and i have no other issues...

I had shocking touchscreen issues on 5.0.6, to the point where the phone was unusable and I had to reboot or pull the battery. Turning the screen off and on using power button would work occasionally but not always. Unfortunately I am still having the occasional problem on froyo. I had some mates trying to troubleshoot for me and took a few logs, the recurring error was (CM 5.0.6):
I/InputDevice( 117): Dropping bad point #1: newY=176 closestDy=3401 maxDy=2779
I haven't taken a log while on froyo

Thanks for the input, fellas. Sounds like it's a more apparent issue in this test release of Froyo. I've had the issue since before flashing the update, with stock 2.1, but it's sounding like it's software related and nothing actually wrong with my phone. Guess I won't bother contacting HTC haha

[Q] Deathly crash issue: only solution is factory reset. SERIOUS ISSUE

Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?

sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)

The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol

[Q] Recurring wifi error

I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?

seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium

Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium

Lagging/Keyboard/Notification issues after Towelroot

Actually, Towelroot may not be related, but oddly enough my phone did a couple of app updates and then Tmobile could tell my phone was rooted. Then it started acting really weird. I got a green LED notification but had none in any apps. The stock keyboard gets really laggy. (1 press per 4 seconds), if you try to long press to move a widget/button or anything, the phone hangs up.
I am almost convinced it is something Tmo is doing. The phone shows in Tmo My Accounts that the phone is rooted.
I tried to unroot (SuperUser is a no-go), I tried downgrading using downgrade methods but I get an error and it shuts down. I don't know where to start now. My phone will be kicked back from Tmo if I try to send it in. I knew one day Root Exploits would catch up with me.
If anyone has a bright idea other than wait till there is a fix, I am all ears.

Brutal-Force said:
Actually, Towelroot may not be related, but oddly enough my phone did a couple of app updates and then Tmobile could tell my phone was rooted. Then it started acting really weird. I got a green LED notification but had none in any apps. The stock keyboard gets really laggy. (1 press per 4 seconds), if you try to long press to move a widget/button or anything, the phone hangs up.
I am almost convinced it is something Tmo is doing. The phone shows in Tmo My Accounts that the phone is rooted.
I tried to unroot (SuperUser is a no-go), I tried downgrading using downgrade methods but I get an error and it shuts down. I don't know where to start now. My phone will be kicked back from Tmo if I try to send it in. I knew one day Root Exploits would catch up with me.
If anyone has a bright idea other than wait till there is a fix, I am all ears.
Click to expand...
Click to collapse
Has nothing to do with rooting your phone. I wasn't rooted for 2 months and it was doing that switch to the g3 keyboard in the g2 thread use the apk installer

D-FUSE said:
Has nothing to do with rooting your phone. I wasn't rooted for 2 months and it was doing that switch to the g3 keyboard in the g2 thread use the apk installer
Click to expand...
Click to collapse
The new android L keyboard in the playstore is really smooth too. No lag, good feel, has emojis if that matters to you. There's a thread in the apps section for the 5.0 keyboard you can manually install and it'll have more skins but the easiest way is to install from the playstore.
Edit: T-mobile keeps track of rooting somehow? How have I never heard that!? Seems like something a Dev or someone would have figured out how to block or what app they're using to spy. That sucks especially in regards to warranty etcetera being denied.

Its not just the Keyboard. I too switched the thumb keyboard which resolves the lagging key-input, but there is also a blinking green led notification that won't go out and I can't answer the phone because touch input (drags and long presses) are buggered.
I have installed TWRP, gonna Try to install a rom and fix it

[Q] Moto X turning off suddenly

Hi all, I need help.
It happened a couple of days ago that overnight, with aero mode on, my not rooted xt1053 didn't wake me up since it just turned off sometimes before the alarm. Even if it had never happened before (just one week before it reached the amazing uptime of 650 hours without any reboot), I decided for a factory reset, since it's very important to me that it works as an alarm too. Yesterday, after the factory reset, it turned off while using whatsapp, all on a sudden. Tonight, it happened again, and I missed the alarm again.
Everytime I turn it on, I have the notification that Google Maps stopped working, or alternatively Google Keep. Battery is always at the same level it was before, I mean, it's still charged with at least 50% battery when this happens. Now I tried to uninstall Google Keep to see if there was something wrong with the last update, but it seems strange to me that it may be the cause.
Does anyone has any idea of what to do?
Any help would be really appreciated.

I have the SAME exact problem. Don't know why...

Julienjarod said:
I have the SAME exact problem. Don't know why...
Click to expand...
Click to collapse
I have the suspect that is Google Keep that now shows also the map on the notes...somehow Keep and Maps have some conflicts maybe? I unistalled Keep and for the moment no sudden death...let's see...

luxpast said:
I have the suspect that is Google Keep that now shows also the map on the notes...somehow Keep and Maps have some conflicts maybe? I unistalled Keep and for the moment no sudden death...let's see...
Click to expand...
Click to collapse
I tried uninstalling most of the apps, but it still happen. I've tried with brazilian soak test, but it still happens.
What should I do to understand the problem? I was thinking about going back to the original rom and try to use it in safe mode...do you think it could help?
With the brazilian lollipop soak test, I do not have any Maps or Keep stopped working once turned back on. Moreover, last times it did happen during the day, while in my hand or on the desk. Twice a day, more or less.
Please, help!

Mine has the same issue. Maps will randomly force close, or just crash back to the home screen. Usually though, Google Maps locks the phone for 30 seconds and then it reboots.
Happens twice a day. It got so bad that I've given up on my Moto X and bought an LG G3. Now I'm sitting on a boot loader unlocked Moto X xt1060 that literally will not last half a day without randomly rebooting.
It does this on any firmware, custom or stock.

bobdamnit said:
Mine has the same issue. Maps will randomly force close, or just crash back to the home screen. Usually though, Google Maps locks the phone for 30 seconds and then it reboots.
Happens twice a day. It got so bad that I've given up on my Moto X and bought an LG G3. Now I'm sitting on a boot loader unlocked Moto X xt1060 that literally will not last half a day without randomly rebooting.
It does this on any firmware, custom or stock.
Click to expand...
Click to collapse
I've bought a Z3 Compact too in the meantime, but I still would like to fix the Moto X since is a beautiful phone otherwise. It's a shame this thing of rebooting or randomly turning off, since I need a reliable phone... It was just two weeks ago that I reached 30 days without turning off and with any rebooting. I can't believe there's nothing I can do to fix it, it doesn't seem an hardware issue...

I'm not so sure my issue isn't a hardware problem. I've never dropped it, but its gotten wet a couple times by accident. (Rain, spilling things on my lap, etc...) I'm notoriously horrible with phones though.
Its always worked afterwords, though. And the reboot problem just recently showed up randomly.
I also had an issue making or receiving a call. I could use data, send MMS and SMS, but it would not make or receive a phone call.