So I am on CM 7.1 RC1 and running VTL ADW with the OC kernel. On a reboot, I will have all my widgets say "failed to load." Sometimes the add button won't even show up. Restarting ADW doesn't help. In fact nothing seems to help except removing them all and putting them back up again.
So far, I have tried a few different launchers (most of them ADW based), I have tried wiping the data. I have tried a factory reset, formatting System, Data, and Cache, and COMPLETELY reinstalling everything from scratch.
While not the big issue, but possibly somehow related, I noticed that Kindle is missing from the apps list, even though it claimed it was installed last night, and I have the bug where Navigation from Maps disappears on a reboot (but reappears temporarily on a reinstall).
I'm running out of ideas - has anyone else had anything similar to this?
majorpay said:
So I am on CM 7.1 RC1 and running VTL ADW with the OC kernel. On a reboot, I will have all my widgets say "failed to load." Sometimes the add button won't even show up. Restarting ADW doesn't help. In fact nothing seems to help except removing them all and putting them back up again.
Click to expand...
Click to collapse
Update to a latest nightly, there was a Widget fix that went in a week or so ago.
khaytsus said:
Update to a latest nightly, there was a Widget fix that went in a week or so ago.
Click to expand...
Click to collapse
Thanks. I'll give that a shot. I thought mine was direct off the nightly. Cubed passed the CM7 on to me, so I can't be positive. I have build GRJ22 on the 2.6.32.9 kernel.
majorpay said:
Thanks. I'll give that a shot. I thought mine was direct off the nightly. Cubed passed the CM7 on to me, so I can't be positive. I have build GRJ22 on the 2.6.32.9 kernel.
Click to expand...
Click to collapse
You'd have to check, but if you're on the 7.1 RC that's several weeks old.
Related
Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?
Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.
Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?
I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?
One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...
For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms
Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.
For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
First, thanks to the developers and participants. Great work!!
All was well with my Nook Color with
CM7 7.0.2 stable, Google apps / market, Dalingrin OC emmc-040411
Then I upgraded to CM7 7.0.3
All seemed fine except I couldn't tether via USB to my computer, which I need to do.
Someone on another thread said that this was a known issue with 7.0.3. No problem, so I used Clockworkmod recovery to revert to CM7 7.0.2., then reflashed Google Apps and the Dalingrin OC to get back to where I started before the 7.0.3 upgrade.
Everything seemed fine except for the frequent error message saying that Android.Process.Media stopped unexpectedly.
So far, video doesn't work, Android App market downloads don't work and I'm sure they'll be a few more apps but it's hard to tell since the message pops up randomly (or so it seems.) The NC also seems to freeze more than normal.
Any suggestions as to how I get clean this error? Your help would be greatly appreciated.
Never mind, Knaries2000 answered it in another thread.
The solution was to go to Settings/Applications/All, find Media Storage and delete it's data, then reboot.
Many thanks Knaries2000 !!!
I wish I could say never mind! I have this problem also.
I just rooted my NC last night.
CWR 3.0.2.8
ManualNooter-4-6-16
CM7 nightly-206
Google Apps 20110613
I've gone into the setup and cleared the cache as stated above, rebooted...no luck. I also read on another thread to use CWR to clear cache also, but that did not help either.
Any other suggestions?
Hoser88 said:
I wish I could say never mind! I have this problem also.
I just rooted my NC last night.
CWR 3.0.2.8
ManualNooter-4-6-16
CM7 nightly-206
Google Apps 20110613
I've gone into the setup and cleared the cache as stated above, rebooted...no luck. I also read on another thread to use CWR to clear cache also, but that did not help either.
Any other suggestions?
Click to expand...
Click to collapse
You want CWR version 3.2.0.1..................
Thanks! Worked like a charm.
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Cabtn said:
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Click to expand...
Click to collapse
Did you make any mods?
Also, are you using any new apps you didn't before flashing CM10?
Did you factory reset when you flashed CM10?
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Cabtn said:
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Click to expand...
Click to collapse
Which version of Semaphore did you flash? Also, are you on CM10.1 or CM10?
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Cabtn said:
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Click to expand...
Click to collapse
Alright, that's CM10.1. Just wanted to make sure you were using the right version of Semaphore for it.
You could try changing your governor and scheduler (I think I used SmartassV2 and noop on my cappy). If nothing works, flash back to stock after a good backup is probably the best solution (Odin KK4 without bootloaders). Start fresh from there.
Thanks! I'll give it a try
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Cabtn said:
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse
Odin KK4 without bootloaders: http://hotfile.com/dl/137871658/d25...O_Bootloaders_Re-partition_Full_Wipe.zip.html