Hey all,
I'm running the newest version of Slick Rom JB (2 Final).
I was running 1.1, and I didn't have any of these problems, but since updating to 2 and updating my radio as recommended I've run into a number of issues. The ones I think can of off the top of my head, and run into most commonly are:
ANY time I launch GMail, read an email, and go "back" using the icon in the top bar rather than the back button, GMail will stop. This only happens when going from an email to my inbox.
My GPS will not get a lock besides a 5 mile radius
Trillian will not connect AT ALL. Just constantly says connecting.
Based on what I've read in the thread, this really isn't the typically experience, so I'm just trying to figure out what could be wrong and how I can fix it.
For the record I have tried the follow:
I restored to an earlier backup when I was running GINSIX v1.6.1 and I do not have ANY of these issues. GPS gets a quick, solid lock. Trillian works fine. GMail does not crash. The only issue I noticed when I restored the backup is that my wifi and tether were both broken. I'm willing to chock that one up to the modem update?
I've tried a clean install by wiping data, wiping cache, installing the rom, wiping the cache, installing Google Apps, reboot. I immediately have the same issues.
I've read that other people have tried to "start from scratch", but I'm not entirely clear of where "scratch" is and how to get there.
So any information anyone would be able to provide would be greatly appreciated.
Thanks in advance.
Ramaniscence said:
Hey all,
I'm running the newest version of Slick Rom JB (2 Final).
I was running 1.1, and I didn't have any of these problems, but since updating to 2 and updating my radio as recommended I've run into a number of issues. The ones I think can of off the top of my head, and run into most commonly are:
ANY time I launch GMail, read an email, and go "back" using the icon in the top bar rather than the back button, GMail will stop. This only happens when going from an email to my inbox.
My GPS will not get a lock besides a 5 mile radius
Trillian will not connect AT ALL. Just constantly says connecting.
Based on what I've read in the thread, this really isn't the typically experience, so I'm just trying to figure out what could be wrong and how I can fix it.
For the record I have tried the follow:
I restored to an earlier backup when I was running GINSIX v1.6.1 and I do not have ANY of these issues. GPS gets a quick, solid lock. Trillian works fine. GMail does not crash. The only issue I noticed when I restored the backup is that my wifi and tether were both broken. I'm willing to chock that one up to the modem update?
I've tried a clean install by wiping data, wiping cache, installing the rom, wiping the cache, installing Google Apps, reboot. I immediately have the same issues.
I've read that other people have tried to "start from scratch", but I'm not entirely clear of where "scratch" is and how to get there.
So any information anyone would be able to provide would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Typically "scratch" is going into the recovery, formatting /system /data and /cache and then reflashing. You might also want to compare the checksum to make sure nothing happened to the file during the download. All fairly typical flashing stuff, which it sounds like you probably did already, but worth mentioning. Also, for what this is worth, I'm running SnowJB, and after updating my phone to the JB radio from the stock ICS radio, I had a bunch of weird issues come up that forced me to revert radio images. Something to think about if all else fails.
I had some similar problems and stumbled upon this...
http://forum.xda-developers.com/showthread.php?p=40115473
It worked for me as well as a few others.
Sent from my LG-E970 using xda premium
For now I've rolled back to the ICS radio and my older GINSIX backup, and things are running great. I figure that I'll just stick with this for now, and I'll try the whole JB thing again sometime later when I have more time to fiddle with it.
Thanks for the help!
Related
Hey Guys,
Having an issue that I just can't seem to figure out. First, my phone specs:
Running EB01 Modem & JT's EB01 Voodoo Kernel w/SuperClean 2.2 Voodoo, ASOP Lock, Power & Battery Mod (via Domush walkthrough).
Now the problem: my phone just shuts off completely when it feels like it and the only way to get it back on is to do a battery pull. Searched the forums and throught it might be the proximity sensor, but flashed it back to stock and it was fine. It seems to happen randomly. It's not the battery because each time i turn it back on it have plenty of battery life. I've tried freezing all my apps and it still does it as well.
Is there someting i'm missing? Anyone else have an idea?
Thank you in advance
My first suggestion is backup your apps and do a wipe wipe wipe. See if that corrects problem.
Let us know
sent from my vanilla voodoo fascinate
I had that happen a couple times as well with SC 2.1. I only ran it for a couple days before SC 2.2 came out. After flashing 2.2 over 2.1, and wiping the cache a couple times, I haven't had it happen again. Then again I only upgraded yesterday, so it may yet happen again. Time will tell.
Posted from my EB01 SuperClean Fascinate with Voodoo
So far so good....I wiped x3 everything (cache, davik, everything) and it seems to have worked. Thank guys. I'll let you know if it acts up again.
Come to find out it was a rom prob, fixed in the forums, called the sleep of death.
Sent from my SCH-I500 using XDA App
FWIW, I did not have the problem with 2.2, and now have upgraded to SC 2.4, and the issue still has not returned. It does seem like I have to hit the power button twice to wake it up once in a while, but it never fails to wake up.
Posted from my EB01 SuperClean Fascinate with Voodoo
It seems to have only happen when you do the steps in a certain order. It's all fixed with the patch.
Actually, it's NOT been fixed with the patch. If you read the thread, the people that thought it worked had it come back after a few hours of use. The only way I've been able to "fix" it thus far is to go back to the stock ebo1 rom. FWIW, the problem for me seems to resurface after I access any media. The first time was after I listened to music through Poweramp and the latest was after watching a video in media hub.
JJRocker said:
Actually, it's NOT been fixed with the patch. If you read the thread, the people that thought it worked had it come back after a few hours of use. The only way I've been able to "fix" it thus far is to go back to the stock ebo1 rom. FWIW, the problem for me seems to resurface after I access any media. The first time was after I listened to music through Poweramp and the latest was after watching a video in media hub.
Click to expand...
Click to collapse
Hmm, I'll have to check it out....I went through my photos and it worked fine after that. I use Audiogalaxy so I don't have music on my phone. I'll go run a video and see if that triggers it. Good looking out JJRocker
This so far has been an issue that's really hard to find info for and it's driving me nuts...lol. So yeah, even though I'm far from being an expert, I'm trying my best to figure out what's causing it so that I can work around it or better yet, help the devs out since they are the real experts here. Adrynalyne put a test patch up and asked people to report on it, so it would probably help a lot if everyone having the problem would post their results in this thread. He's the guy that's probably most likely to figure this out. Also, that link has the patch if you want to give it a shot.
One thing I should probably mention is that at least in my case, once the SOD surfaces, it happens about every 4th to 5th wakeup until I reflash the rom or go to another one. So if you've experienced it already, there's a good chance you won't be able to cure it without a reflash.
Ive noticed there is a certain population of folks who have it, and a larger population of those who do not.
I've been researching for hours on end, with no clear common resolution.
For some, not using Titanium to restore apps fixes it.
For some, my test patch works.
For some, a double reboot fixes it.
I had it happen once, ever, and it was on stock eb01. It never happened again. I myself have noticed increased instability on eb01 using maps and gps, however. A couple days ago, launching maps, and turning on the gps afterwards hard locked my device.
@adrynalyne
Exactly.
It seems that mine is fixed with the patch in both of your SuperClean 2.3 & 2.4, I've tried different media and it seems fixed. Only time will tell tho.
And thank you for all that you do with this phone. It had such great potenital and with you and folks like jt, it's making this phone amazing!
It's strange....I had it happen once this morning and now I can't replicate it. I have used Titanium to restore apps but I only restore one app, AndroidPit App Center. I need it to download ADW EX and Beautiful Widgets since they take PayPal and my debit card doesn't do foreign currency.
Anyway, someone at Android Central suggested avoiding ADW because people were reporting issues with the SOD and that launcher. So, I'm gonna run LP+ for a while and see how that works out.
I have been using ADW EX and no real problems...
...but I didn't think about it, I did clear out me Titanium Backup and just reDownloaded stuff this time. Maybe the backups are the culprit?
Well, right now I'm starting over on SC 2.4 and trying all the remedies I've seen posted thus far. I wiped data and cache, flashing SC 2.4. I'm going to skip the backup assistant since it might try to restore apps that were restored by Titanium. I'll run LP+ and flash a theme (VA green is my current fave...love the BA). Gonna restore my apps manually from the market and I'll even double reboot when I'm all done...lol. Anyway, wish me luck...the real test will be tomorrow at work. I use HandBase to keep track of things so I put my phone in and out of sleep a lot during the day.
And also, many thanks to Adrynalyne and all the other great devs here. The work put into this stuff is much appreciated. I wouldn't put this much effort into getting this working if SC wasn't such an amazing ROM.
JJRocker said:
Well, right now I'm starting over on SC 2.4 and trying all the remedies I've seen posted thus far. I wiped data and cache, flashing SC 2.4. I'm going to skip the backup assistant since it might try to restore apps that were restored by Titanium. I'll run LP+ and flash a theme (VA green is my current fave...love the BA). Gonna restore my apps manually from the market and I'll even double reboot when I'm all done...lol. Anyway, wish me luck...the real test will be tomorrow at work. I use HandBase to keep track of things so I put my phone in and out of sleep a lot during the day.
Click to expand...
Click to collapse
When I redid it again my aps were automatically restoring themselves. So to save you some sanity, make sure you go into privacy and turn off "Backup my settings" and "Restore my settings" as well. It may be dimmed out, but it will sutomatically restore them as well. It's doesn't really do much from what I can tell (I still have to manually add passwords to wifis, which it says it backs up)
Ya know, maybe that's the cuplrit of this whole shabang
Ok, so I had the SOD on LP+ too. Out of curiosity, is anyone with this problem using Switchpro widget or another power control widget that changes brightness? The one thing that seems to always precede the SOD for me has been installing and putting this widget on my desktop. Also, one time I did have it before I installed the widget and checked my screen timeout settings...there was nothing checked which is the same as having the screen never turn off. Apparently, backup assistant restored the setting automatically from a previous flash. Also, I think Super Clean has a power control widget on one of the homescreens by default if I remember correctly. Everything was running great, couldn't get it to SOD, so I started installing some of my apps and put the switchpro widget on my main homescreen, and got SOD on the very next wakeup.
I believe I may have found my culprit!! But before I say, let me recap:
I backed up using TiB. Flashed everything back to DI01 and got the OTA update. Restarted, then flashed to DL09. Reboot, Flashed to Deoxed EB01. I also kept the origional kernel, didn't meess with it because I believed that it was the cuplrit, I am assuming I'm wrong. Everything was good. Slowly started adding programs back seeing which one will kill my phone. I finally found it......it was YouMail.
If you are using this product, you can have it on to your system and it will work. But as soon as it receives its notification of a New Voice Mail notification from their servers. It locks up. Hopfully uninstallation and a reboot will take it away, but only time will tell. I'll report back in.
A little background--I'm not a newbie and have been running custom roms on my Fascinate for many months (and my Droid before it), but I'm also not an expert or programmer. OK, with that out of the way, here's the issue. When JT came out with the first version of CM7 I switched to it from the Froyo CommRom. Since CM7 had a lot of issues in the early days, I carefully followed this sticky and returned to CommRom: http://forum.xda-developers.com/showthread.php?t=1124391
I've since had a pattern of getting severe force closes, to the point that the phone become non-functional, after several days of everything working fine. This has happened with CommRom, Evil Fascinate, CM7, and currently JT's Vanilla Gingerbread. I've gone back to stock many times, have cleared everything (including data), have run the ext4 formatter, have tried different radios (currently on EC09), and have tried different roms. In each case everything runs wonderfully for 2-4 days, then FC's begin. I use Titanium Backup Pro to restore things, but have been doing so without restoring data, since some say that causes FC's. I've also unchecked the options to have Google back up data, since some say that causes FC's.
I'm out of ideas and am getting tired of clearing data and starting over every few days. I suppose I could restore things to stock and see how that runs, but that might be too painful to survive. Anyone have any other ideas?
You mentioned that you restore apps with Titanium. Do you restore only downloaded apps, or system apps as well? Different ROMS often have different versions of system apps, which can cause problems when restoring.
I'd like to see this topic explored a bit deeper. My girlfriend and I both have Fascinates as well, and each of us sees significant force-close rates...not to the point where the phone doesn't function...but 5-10 per day.
Is this simply a chronic fascinate problem on the newer ROMS (we've used MIUI and Vanilla GB).
Have you tried going 4 days without any restore of any kind?
Try a fresh install from atlas/pit/ed05 and go with that for 4 days... No restores.
Probably not the answer you want, but it sounds like your backups contain corrupt data.
KaceMN said:
I'd like to see this topic explored a bit deeper. My girlfriend and I both have Fascinates as well, and each of us sees significant force-close rates...not to the point where the phone doesn't function...but 5-10 per day.
Is this simply a chronic fascinate problem on the newer ROMS (we've used MIUI and Vanilla GB).
Click to expand...
Click to collapse
no its not a fascinate problem, its more likely user error... you must be installing apps & data with tibu. when jumping roms, only restore app's only. Also another thing to try is, boot into cwm, wipe cache, dalvik, and fix permissions.
Fwiw I very seldom ever get a FC...
I've been following the same pattern of behavior with the switching of ROMs and backing up with Titanium by restoring data and apps. My Fascinate picked up a number of bad habits along the way: phantom back button and keyboard button pressing, screen waking back up after I shut it off, and some force closes but nothing like some are reporting here.
I recently switched to PWGB which wipes all data. I used Titanium to restore contacts and text messages only and re-downloaded all the apps from the market.
Since the wipe everything has been smooth and error free.
P-bot said:
I recently switched to PWGB which wipes all data. I used Titanium to restore contacts and text messages only and re-downloaded all the apps from the market.
Since the wipe everything has been smooth and error free.
Click to expand...
Click to collapse
you can use titanium to restore apps, long as you install app only.... do not install app+ data, thats where you run into problems.
I am experiencing this same issue. I first upgraded to CM7 nightlies back around August and that seemed to be the source of the issue. Each time it occurred, I would wipe data and it would disappear for several days or weeks. I then switched to jt's Vanilla GB, and had the same issue. Now I am on CM7.1 and am continuing to have the same problem. Wiping data seems to fix the problem, but it consistently returns after several days.
I did have some success with disabling sync and clearing data for the Contacts Storage and Google Framework applications, which seemed to stop the force-closing temporarily, but they did ultimately return. This only seemed to work for me once.
lagbot7000 said:
I am experiencing this same issue. I first upgraded to CM7 nightlies back around August and that seemed to be the source of the issue. Each time it occurred, I would wipe data and it would disappear for several days or weeks. I then switched to jt's Vanilla GB, and had the same issue. Now I am on CM7.1 and am continuing to have the same problem. Wiping data seems to fix the problem, but it consistently returns after several days.
I did have some success with disabling sync and clearing data for the Contacts Storage and Google Framework applications, which seemed to stop the force-closing temporarily, but they did ultimately return. This only seemed to work for me once.
Click to expand...
Click to collapse
download disk usage from the market and check to see how full your /datadata folder is. I bet its full. there is a thread on rootzwiki about. you can either delete some apps or jt has a tweak to fix the issue.
PhoenixPath said:
Have you tried going 4 days without any restore of any kind?
Try a fresh install from atlas/pit/ed05 and go with that for 4 days... No restores.
Probably not the answer you want, but it sounds like your backups contain corrupt data.
Click to expand...
Click to collapse
I agree with this. Last summer I ran into a series of similar issues (fc and what not) on several roms. What I learned for myself is i never restore ANYTHING. What I do use tho is APP LIST BACKUP which is a very convenient and fast way to download apps fresh from the market. I currently enjoy a fc free phone
Sent from my SCH-I500 using xda premium
I've tried everything I can think of or find in this subject but I can't figure it out.
I'm getting FCs all over and seemingly randomly.
There's no one program doing it either.
I've used cyanogen 7 7/17 version with glitch kernel (both 11 and 12) and the v3 kernel. Maybe the stock but I don't remember.
Also flashed the dl09 or which ever radio was recommended for cm7 on the ROM list sticky.
Tried the nighties and am on not the recent one but the one right before it with stock and glitch 11 and 12. Also tried before and after v6 super charger which seemed to make my launcher before faster and without the stopped responding dialog.
I also use the ultimate kernel removing script between kernels.
Here's what I've already done to try to fix it:
Wipe big 3. fives it for awhile then starts up in force.
Wiped to stock 2 or 3 times. Still happens.
Fixed permissions. Works longest so far but still starts up again later.
Wipe cache and data in manage applications settings menu for creasing programs. Works for a while usually but then goes
back to crashing.
I followed ask instructions to install everything properly.
The only thing is that
do I need a special bootloader with nighties and stock kernel?
What am I missing here? It seems like it's related to wifi because I can keep things stable a little longer with wifi off but it is not always 100%. Definitely related to internet. Also seems like the cache reaches 2-3 megs when programs crash
browser seems to be more likely to crash. Will crash constantly and I'll open up Firefox or opera wends everything is peachy. I think neither ox those browsers crash from what I can tell.
Oh and could it be gapps somehow. I'm not sure but it might be a case built that all the crashing programs are gapps.
I've tried the new version 2.2.5 I think posted somewhere and the original 2.2.3 I think. I'm pretty sure they both crash.
I'm maybe to frustrated to see what's right in front of me and I maybe have forgotten an important detail so please forgive and I'll be happy to provide any info.
This is near perfect and that's the thing that's holding me back right now.
Anyone else have this happen to them? Any advise?
Sent from my SCH-I500 using xda premium
How did you originally come to cm7..ie. What was your previous rom and kernel prior to making the switch?
What steps did you take to get to
mtd format?
And lastly I read your whole OP but am still unsure if you've tried Odin'ing a stock VZW official rom to start from scratch? (ie. Eb01,dl09, or ed05)
Edit: Also did you restore any apps or system data via titanium backup?
Sent from my SCH-I500 using XDA App
I've come to cm7 at least twice from a stock froyo ROM. I followed the directions in the sticky exactly. At least twice.
I did restore titanium but not from non-mtd. I reinstalled every app one by one after upgrading.
I'm thinking it might be the wrong gapps. If browser is a part of gapps, I'd betting on it then. It seems the fc's might all be related to
the various gapps.
That's the only thing that I can think if that I haven't tried.
Sent from my SCH-I500 using xda premium
Here's the latest gapps.zip includes market...don't know if you've tried this oneand I don't think it contains anything for the browser, but i'm not sure...its for Mtd builds.
http://forum.xda-developers.com/showthread.php?t=1191063
Edit: i'm also assuming you've ran fix permissions via cwm or terminal emulator right?
Sent from my SCH-I500 using XDA App
I'm making you assume a lot, sorry. Yeah. Did all that.
I'm trying to isolate it. I'm seeing that the force closings are maybe not so random.
It's the browser, google services framework and programs that I guess rely on browser. They are programs that access the http protocol. Reddit/f5, Chan browser etc. I've yet to have a program crash that was not accessing the internet like chuzzle.
Gmail does sometimes too.
Anyway, if they fc I go into manage applications and usually clear cache for the offending program Anne it works again until the cache gets up around 2 or 3 megs give or take.
I know people have been complaining about the data cutting in and out on this ROM so maybe that's involved.
I originally thought it was wifi because it seemed to only happen on wifi but i'm getting it on 3g but not as often.
I'm thinking that the data appears to be on but isn't and it's confusing programs but then there would be others with the problem. The other theory is that my cache space is fried.
Sent from my SCH-I500 using xda premium
In case someone finds this buried down here with the same issue, here's how I think I fixed it.
Wipe data again. Make sure you let the gapp installer install everything itself.
Titanium backup: restore missing apps (double check for went google apps) and data. Or hand install your apps and restore data.
I have the install location set to original.
That seemed to work even with the seeming wifi cut out and the whole thing.
I also didn't install Firefox or opera this time. That shouldn't be the problem but i'm recording it here anyway just in case.
Good luck
Sent from my SCH-I500 using xda premium
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...
First off I have a T-Mobile Note 2, rooted, Tweaked ROM, ect. I have posted in their forum as well, just hoping for answers. I first updated from TWEAKED 2.4 to 2.5 via OTA and at that point started experiencing this issue. When I open apps and then go back to the home screen, click recent apps..they do not appear there. But they are still running in the background. I first noticed it with Snapchat and thought that it was only a problem with that app, but then I experienced it with Instagram, Yahoo Messenger, History Eraser, ect. I cleared dalvik, cache, ect and was still having this issue. So, I thought maybe it was the OTA through Goo so I factory reset my phone and cleaned flashed the entire 2.5 ROM and I am still having the exact same issue. I never had this problem on 2.4 and I have no recently installed apps that would be conflicting as far as I know. Any ideas? I have a screencast showing this issue, not sure how I go about posting it. Regardless any help would be appreciated, thanks!