Related
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
Experiencing random shutdowns ever since moving to Congnition. This morning, just to clean everything out, I did an Odin Master Clear and used Odin to flash Cognition 2.2b6. About an hour later, I had my first random shutdown.
This doesn't appear to be totally random. It only occurs when the phone is in screenlock mode, such as when it's in my pocket or sitting unused on my desk. I will go grab the phone to turn on the screen, and realize that it is shut off. So, I have to long hold it to boot it back up again.
Is anyone else experiencing this issue with Cognition? It seems to occur about once an hour for me, and sometimes it will go hours without shutting down. Also, it never appears to shutdown when I'm using it, but maybe that's just by chance.
Any other ideas how I could fix this? I've already Master Cleared. Could it be an app that doesn't play well? The only apps I've installed so far is Launcher Pro, Beautiful Widget and Titanium Backup, of course.
Are you serious??????? You open a thread just to ask this question?? Why not ask in the Cognition thread?!!!!
daraj said:
Are you serious??????? You open a thread just to ask this question?? Why not ask in the Cognition thread?!!!!
Click to expand...
Click to collapse
Because it has a trillion posts and my question would be swallowed up in about three minutes.
Same here but i dont think its cognition its the froyo leak. It was happening to me with the stock leak too so i know its not cog. If u think it is try the stock leak. But id wait to see if it still happens after offical build.
Sent from my SAMSUNG-SGH-I897 using XDA App
I had them on Stock ROM but havent had any since installing Beta 6 or 7.
ryanjg11 said:
Experiencing random shutdowns ever since moving to Congnition. This morning, just to clean everything out, I did an Odin Master Clear and used Odin to flash Cognition 2.2b6. About an hour later, I had my first random shutdown.
This doesn't appear to be totally random. It only occurs when the phone is in screenlock mode, such as when it's in my pocket or sitting unused on my desk. I will go grab the phone to turn on the screen, and realize that it is shut off. So, I have to long hold it to boot it back up again.
Is anyone else experiencing this issue with Cognition? It seems to occur about once an hour for me, and sometimes it will go hours without shutting down. Also, it never appears to shutdown when I'm using it, but maybe that's just by chance.
Any other ideas how I could fix this? I've already Master Cleared. Could it be an app that doesn't play well? The only apps I've installed so far is Launcher Pro, Beautiful Widget and Titanium Backup, of course.
Click to expand...
Click to collapse
I would use Odin One Click and go back to stock for a few days and see what happens.
If your restoring with Titanium Backup, don't restore settings.
bet you don't get a solution before they lock this thread
No random shut downs here on either cog 2.2 beta 5 or beta 6
formgen said:
I had them on Stock ROM but havent had any since installing Beta 6 or 7.
Click to expand...
Click to collapse
+1 b5.5,b6,b7 No shutdowns. Had them all the time on 2.1 JF6.
my random shutdown issue STOPPED as soon as I started running Cognition ROMS. DG was a lifesaver for my phone.
If your having them.. keep it on stock - if it repeats - you have a dud and need to get it replaced.
And when you flash it to stock.. don't load anything on it to see if it stops the random shutdown.
**edt... and um wth is this in the dev forum and not the Q&A?
Try this if you havent
No problems here either. I have been with Cog since the beginning and have never had this problem. I had it on another ROM from another Dev and immediately came back to Cog. I am now running Cog 2.2 Beta 7 and Love it! Fastest phone I have ever owned, very stable and GPS finally works!!! I would recommend flashing back to stock with Odin, doing a master clear and then installing Cog beta 7 via Rom Manager. I dont deal with Odin when flashing ROM's, only when going stock.
Hope this helps!
hey... i thought i was the only one getting the random shutdowns. i think i've been getting it since the first month of owning my phone. i get it 2-3 times a day. 1 if i'm lucky. i don't blame it on cognition's rom, tho... dunno what to do or who to ask about this problem.
but as for flashing back to stock and then the latest COG rom, i have tried that, but it didn't work...
I haven't run Cog beta7 for very long, but I can tell you I've never had a random shutdown for the entire time I've owned my phone (bought 3 days after release).
I'm tempted to tell you to try a different battery or something of that nature...
gflare said:
I haven't run Cog beta7 for very long, but I can tell you I've never had a random shutdown for the entire time I've owned my phone (bought 3 days after release).
I'm tempted to tell you to try a different battery or something of that nature...
Click to expand...
Click to collapse
i would agree swapping the phones battery or the whole thing would be the way to go...
This is not an unusual issue. Seems even Moto apologized for it in their Froyo OTA for the Droid. Moto says a fix is coming. I would suspect it is a Froyo bug and something that will be worked out in a future update for all Froyo handsets.
No random shutdowns for me on stock leaked of any of the 2.2 cognitions
I've been having random shutdowns on Stock 2.1 Eclair for a while, there was another thread poster about this in the Q&A.
Even after I flashed to cognition b5.5, I get them, and with the same frequency. Sometimes I get 2 or 3 a day if I'm extremely unlucky, usually I'll only get one like once a week. I don't really find it to be too big of an annoyance.
I think it has something to do with an app, and not the phone itself. If you're getting them consistently 2-3 times a day then I guess you should just master clear, go back to plain stock, and then reflash cognition if you want to.
PEBCAC problem
ryanjg11 said:
Experiencing random shutdowns ever since moving to Congnition. This morning, just to clean everything out, I did an Odin Master Clear and used Odin to flash Cognition 2.2b6. About an hour later, I had my first random shutdown.
This doesn't appear to be totally random. It only occurs when the phone is in screenlock mode, such as when it's in my pocket or sitting unused on my desk. I will go grab the phone to turn on the screen, and realize that it is shut off. So, I have to long hold it to boot it back up again.
Is anyone else experiencing this issue with Cognition? It seems to occur about once an hour for me, and sometimes it will go hours without shutting down. Also, it never appears to shutdown when I'm using it, but maybe that's just by chance.
Any other ideas how I could fix this? I've already Master Cleared. Could it be an app that doesn't play well? The only apps I've installed so far is Launcher Pro, Beautiful Widget and Titanium Backup, of course.
Click to expand...
Click to collapse
PEBCAC problem "me thinks".
Its device specific, I had one that did it, they gave me a new one.
designgears said:
Its device specific, I had one that did it, they gave me a new one.
Click to expand...
Click to collapse
That definitely seems to be the case. I had a Captivate that was running JF6 that was completely stock other than being rooted. It started randomly shutting down within a couple of days. I thought it could be an issue with rooting it, so I flashed back to stock and used it like that for a few days. The random shutdown issue didn't go away, so I took my phone back and told them it was defective. They gave me another one and I haven't had the shutdown issue even once, through JF6, JH7, JI6, and Cognition 2.2 Beta 6 and now Beta 7.
Okay so I updated to ICS o days after the initial release, lost all my numbers and some apps here and there but no big deal. Well now my vivid has been acting extremely glitchy with apps disappearing from the home screen, the stock internet browser starts dock mode after a few page searches, the phone resets itself when I set it down or plug it in, there are times when it resets itself that I can't even turn it on so I have to pull the battery out so I can finally turn the phone back on, and finally when its been reset no matter which way it has to update all the apps.
I don't know what the heck is going on all these problems have started within the last week and I'm running ICS 4.0.3. Stock, anyone got a clue what's going on?
IF you did the ota....download the ruu and reflash with it...ota has caused alot of issue for a lot of people
Think of the OTA as a Windows 'upgrade' instead of a full installation. It can cause things to go haywire. I just had this issue today. Lol.
Sent from my HTC Vivid
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
So apparently I didn't pay enough attention and maybe applying the OTA 246 update from a rooted 905 creates problems. I knew that the update had been around for at least a little bit so I finally decided to go ahead and do it. I did make sure that there would be a way to root again after the update but in all of that investigation I never noticed anything about needing to unroot before applying the update.
So I did it with no problems. After it booted to the homescreen again it was a bit slow but I figured that it was due to things getting settled and loaded for the first time. But after a few minutes of the phone being on and me just looking around the new menus, the phone froze. After a minute or two of being frozen it automatically restarted. If I leave the phone alone once it has booted I can come back to it 10 minutes later and it will unlock and I can mess around for about 2 minutes before it will freeze again.
So not sure if this is a result of updating while rooted or not. I did attempt to re-root though and was "successful" but now I have SuperSU AND Superuser apps installed.
So needless to say I think that I've messed something up. I have a titanium backup from 905 and was thinking that I should try and do a factory reset. Assuming that it will take it back to stock 246.
Any thoughts or help would be appreciated.
Nathan
So interesting tidbit. I read that some others had at least similar problems but they weren't able to make or receive calls so I tried to do that myself. So I called from my landline and connected just fine. After 5 minutes and 45 seconds the phone froze but the call is still connected after 20 minutes. Can't do anything on the phone but the voice signal is still intact.
So another update. I kinda forgot about the call being connected so it was connected for about 25 minutes before I hung up. I left the phone alone for a few while I was researching how to restore texts from my titanium backup that was made on the 905 build, (since the texts were really the only thing that I couldn't get back from the market). When I came back to it I thought that I'd click on the text app just for the hell of it and lo and behold it came up just fine. I checked around with some other apps and made sure that I could both send and receive texts. For all intents and purposes it looks like my phone is functional. For now.
I don't know if something about leaving the call connected for that long jogged something into place but I'm grateful so far. It does look like the wifi has some issues staying connected but that is possibly due to some setting that I haven't figured out yet.
Anyhow, not that there's anything specific here in terms of troubleshooting but I hope it helps someone else too.
Nathan
Forrice said:
So interesting tidbit. I read that some others had at least similar problems but they weren't able to make or receive calls so I tried to do that myself. So I called from my landline and connected just fine. After 5 minutes and 45 seconds the phone froze but the call is still connected after 20 minutes. Can't do anything on the phone but the voice signal is still intact.
Click to expand...
Click to collapse