Related
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
I received my OTA to FRF83... and now my phone seems to be freezing up every so often while doing basic tasks... even waking up the phone sometimes freezes at the unlock screen. Anyone else getting this? My phone is UNROOTED and official. FRF72 ran fine... not sure whats going on but its REAL annoying.
I even tried factory resetting and still getting the same issues.
Any ideas? Can I manually go back to FRF72 somehow?
Can you clear the cache and dalvik cache via recovery, if you have stock recovery? I know you can if you have a modded recovery.
if not, then maybe it's an app or something hogging memory
stuff said:
Can you clear the cache and dalvik cache via recovery, if you have stock recovery? I know you can if you have a modded recovery.
if not, then maybe it's an app or something hogging memory
Click to expand...
Click to collapse
I just tried "clear user data"... thats about all I get with stock recovery. I don't think its an app considering I deleted everything and it still continued to freeze.
Can I delete Dalvik from ADB even unrooted?
I get frequent lock ups and freezing on an unrooted AT&T with 2.1. Seems too many apps load up and even though they may be in the background not using resources, the overall memory drops to about 25 MB. Go get ProcessManager from the market and kill the apps running. Some will restart but it will cure the lockups. I also disabled a handful of things on startup, stopped using live wallpapers and routinely kill apps to free up memory because of the lockups. Maybe Froyo 2.2 will correct this issue. Seems most of the rooted guys don't have any of these issues, so it must be this version of firmware.
Big_O said:
I get frequent lock ups and freezing on an unrooted AT&T with 2.1. Seems too many apps load up and even though they may be in the background not using resources, the overall memory drops to about 25 MB. Go get ProcessManager from the market and kill the apps running. Some will restart but it will cure the lockups. I also disabled a handful of things on startup, stopped using live wallpapers and routinely kill apps to free up memory because of the lockups. Maybe Froyo 2.2 will correct this issue. Seems most of the rooted guys don't have any of these issues, so it must be this version of firmware.
Click to expand...
Click to collapse
Like I said... I factory data reset so there where NO APPS. and the phone still comes to a screaching hault after a few minutes of jumping in and out of apps. It freezes to the point I have to remove the battery. Becomes completely unresponsive to touch.
As a side note, ive been using android since the first G1 on pre-order... I know how it works and how you need to use a task killer to keep stuff running smoothly... This however is extremely odd as it completely freezes.
again, only started after my OTA update to FRF83.
thanks for the input. I guess i'll have to send back my N1 for the forth time to HTC... getting pretty sick of this. That Iphone 4 or Galaxy S looks better everyday.
You don't need a task killer manager since 2.1. Froyo is even better at handling memory.
Sent from my Nexus One using XDA App
i noticed the same thing on my phone today...unlocked phone went from ERE27 to FRF50 to FRF83 yesterday......
today it seems to freeze...from time to time - i thought it requires a battery pull but if i wait long enough it will be ok again.
anyone know what the issue is?
rensky said:
i noticed the same thing on my phone today...unlocked phone went from ERE27 to FRF50 to FRF83 yesterday......
today it seems to freeze...from time to time - i thought it requires a battery pull but if i wait long enough it will be ok again.
anyone know what the issue is?
Click to expand...
Click to collapse
I'm glad I'm not the only one. Mines also an unlocked phone. Wonder if that has anything to do with it.
Ugh we need frf90 to come along and fix this!
The Same here
It happened to me right now, My phone hanged and I forced reset it, it happened one time when I was on FRF72 and one time now on FRF83. it was after a phone call and I couldn't unlock the phone, touch screen didn't work but it did work for power button menu so it should be a software problem, I thought it should be something incompatible between launcher pro and FRF 72 and FRF83 but it seems it is not the case.
I have the same problem. Went from ere27-frf50-frf83. I thought it was launcherpro so I uninstalled it.
Still getting freezes on unlock...and switching between Apps. Sometimes need battery pull sometimes just some time for the phone to catch up.
I had previously switched from frf50 back to ere27 because I couldn't stand the constant need to pull battery because phone freezes.
issues i have with frf83 is not as serious as frf50 so I think I will still stick with it for a few days and see what happens.
Just really need the official ota.
Sent from my Nexus One using XDA App
I just upgraded to the 2.2 (FRF83) yesterday, already had to pull the battery twice in one morning because it just froze up..
What the fu*k did they do! The 2.2 prerelease was fine hadn't had any crashes at all in the month I used it.
Edit; make that 3 times.. WTF!
Now, I'm extremely tempted to just root the phone but I was sticking with official builds for stability, I really didn't think it would get worse..
Yup having the same problem... Had to pull the battery twice today due to freezing and the same thing yesterday... It just started happening to me. Got 83 when it first came out, and its now starting to freeze. Idk what the deal is..
I still have no idea what these updates do.. What's different? I'm talking about the frf50, 72, and 83.. Froyo by it self seemed fine, what's new??
Sent from my Nexus One using XDA App
Hello, So i have had the Captivate for a full 2-3 weeks now from rogers Canada.
LOVE IT ! Not much lag, GPS super accurate but Ive come across few problems that may be related to software.
For the first time tonight, my phone shutdown. It wasnt charging or anything, but i couldnt unlock it and the opening animation lit up when holding down the side so i assume it had shutdown.
But my biggest worry is 3 days ago, and again last night, I woke up to find my screen all black and white, (like a faded black) and phone was completely unresponsive. I had to remove battery and reinsert, then it would start up and work normally all day. I really do not wish to return it, unless I have too, but can this be app related? or just buggy? I will keep track, but couldnt find any other with this issue on google search.
Hopefully someone here can help.
It's been a problem with AT&T Captivates and my phone suffered as well. There's a thread in General section where people all talk about random shutdowns for their phone. Is your phone rooted? I think my shutdowns started happening when I just rooted the phone.. but somehow after I flashed a cog rom, it was all ok...
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
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