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.
This fixed both my Camera and Google Talk that stopped working in Sense ROMS om 08-31-11.
FIX:
1. Go to Settings and select Date & Time.
2. Un check Automatic
3. Change the time to 08-01-11
4. Go and open your camera (it should work now)
5. Now you can go back and check Automatic in the Time & Date Setting
yes,I see log:
Code:
I/CameraService( 3944): CameraService started (pid=3944)
I/OlaEngine( 3944): [Ola_Engine_Create:75] engine build info [ name ] : htc
I/OlaEngine( 3944): [Ola_Engine_Create:79] engine build info [ date ] : 2011-05-13 18:34:22
I/OlaEngine( 3944): [Ola_Engine_Create:83] engine build info [ version ] : __bulid_revision_171__
E/OlaEngine( 3944): [Ola_Engine_Create:91] This library will be expired at 2011/8/31.
D/OLAWORK ( 3944): create OlaEngine failed -32
Have time to lock this file:/system/lib/libcameraservice.so
However, I found that you can use incredible_s (s710d) file to replace.
I put a file in here, from RUU_Vivo_W_CT_Gingerbread_S_HTCCN_CHS_CT_2.13.1401.4_Radio_1_01_50_0701_NV_MFG_CT_2.22_release_202988_signed extraction.
This file is not the time lock. 2.07.605.0 ~ 2.11.605.0 stock rom application.
View attachment libcameraservice.zip
I TAKE NO CREDIT FOR THIS. Thanks to the help of mpwt51 on the Android Central Forums and Snow02 on the BAMF Forums, this issues is now resolved.
Looks like Verizon put some sort of time bomb into these apps. Simply changing the date back wil resolve this issue. Of course that is no way to actually resolve it. Flash this http://db.tt/Bcltlcr instead and it should solve these two issues.
Source: BAMF via Android Central Forums
You guys are freaking geniuses. I have been looking for a solution for this for over 4 hours and found nothing. Figures, the minute I check XDA there is a solution, right there.
Kalandros said:
You guys are freaking geniuses. I have been looking for a solution for this for over 4 hours and found nothing. Figures, the minute I check XDA there is a solution, right there.
Click to expand...
Click to collapse
That wasn't the case last night when I originally posted the issue and 4 guys over at TheMikMik were flashing like mad men, including myself, to try to figure out what sickness was ailing our beloved devices! Glad there's a cure though.
not rooted
This can't be flashed if not rooted, correct? I'm on GB 2.11 not rooted
It worked on GB 2.11 1nd 2.10 not rooted, Thank you very much!
Mig1234 said:
This can't be flashed if not rooted, correct? I'm on GB 2.11 not rooted
Click to expand...
Click to collapse
I seriously doubt it.
I've tried this and can confirm it works like a charm.
8-1-11?
Hey guys,
I'm amazed that someone actually figured out that the date is causing this problem. Seems lame that there's this code in the system with expiration dates. WTH Verizon!
Thank you for this fix its a life saver
Sent from my ADR6400L using xda premium
Does this fix the front camera issue on google talk on gingerbread?
wj_johnson said:
Does this fix the front camera issue on google talk on gingerbread?
Click to expand...
Click to collapse
No idea what you're talking about.
Google talk video on gingerbread (thunderbolt) will not use the front facing camera
wj_johnson said:
Google talk video on gingerbread (thunderbolt) will not use the front facing camera
Click to expand...
Click to collapse
That's always worked fine for me. You're ROM is the issue.
UndergroundWire said:
I TAKE NO CREDIT FOR THIS. Thanks to the help of mpwt51 on the Android Central Forums and Snow02 on the BAMF Forums, this issues is now resolved.
Looks like Verizon put some sort of time bomb into these apps. Simply changing the date back wil resolve this issue. Of course that is no way to actually resolve it. Flash this (nooblinkremoved) instead and it should solve these two issues.....
Click to expand...
Click to collapse
I'm not really sure why, but this only fixes my google talk, but not my camera. I've tried several of the camera fix .zip files and the most common result, across multiple ROMs is that google talk gets fixed, but the camera stays black, acting like it's working, but there are no buttons and the screen is black.
I first tried this on BAMF Forever 1.10 and acheived that result. Then, I tried it on Liquid Vigorsense v1.1 (can't find v1.2 on Rom Manager and the rootzWiki link doesn't work b/c it was on multiupload) and had the same problem. Eventually, I flashed each ROM again, wiping data, cache, dalvik and batter stats multiple times and when I wen't back in to BAMF Forever, it worked. B/C I liked sense 3.5, I wanted to go back to Liquid VS, so I tried flashing back to it and sure enough, both gtalk and the camera worked.
At that point, the only thing I wanted on a sense 3.5 ROM to make my life complete was the keyboard with arrows, so I tried a few keyboard w/arrows zips and none of them worked, so I tried flashing one of the Infected ROMS (Airborne). I found a keyboard w/arrows zip within their lists, so I flashed it and got the keyboard to work, but then the camera was gone. I found a camera fix that they had and it didn't work initially, but after a few re-flashes, everything worked.
Then I got greedy and wanted my sense world clock/widget, so before flashing back to one of my backups from liquid vs, I backed up the Infected ROM and when it booted back up, gtalk and camera were broken again. I tried flashing all of my backups from liquid and bamf forever that had a working camera and the camera/gtalk were broken on them as well.
So, I've flashed Bamf SOAB and I used the keyboard zip for bamf SOAB (worked!) and the camera fix mentioned in this thread and no dice. gtalk works, but still, just a black screen camera. I've wiped and flashed and wiped and flashed each, liquid and SOAB couple of times each (each time, wiping multiple times).
I've got a hilarious 1 year old girl and really want to get back to documenting her life in the candid fashion she so often provides, but I need my camera to be fixed.
I haven't seen many posts on this topic across most of the forums/sites after Septemer, 2011, so it makes me feel like everyone else got this to work. I didn't have the problem in September. It never hit me until I had to swap out my TBolt due to the right side of my screen crapping out. When the new one came from VZW, the camera/gtalk problem happened.
Any help or ideas? (sorry for writing a book)
Much thanks in advance.
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...
Hi guys,
I've been a member for ages, but this is my first post - thanks for all the help you've inadvertently given me over the last year or so!
I'm a bit of a Cyanogenmod groupie - I almost always install the latest nightly builds on my I9300, several times a week at least. Apart from the odd camera glitch here and there, I've never had any serious issues, and I absolutely love it - so much nicer, cleaner and more responsive than stock.
But the last 4 or 5 days, when I've updated to the latest nightly release, I get loads of SuperUser errors, and Tasker seems to have completely vanished, along with the few widgets I have created to go with it. All that is left are Android icons, with a toast error saying "not installed" when I try it.
I also can't seem to get onto the internet, either via 3g or wi-fi, but I think that is a local problem with my router...
I would re-download Tasker and reinstall it, but why should it vanish in the first place? And when I try and restore it from my Titanium backup, it just takes forever and never finishes - this makes me think the new nightlies are not compatible with the current release of Tasker (or the other way around - d'uh)...
I hope I'm wrong, and just doing something stupid. 'cos I use Tasker a lot and this is stopping me from updating CM.
Any advice appreciated!
Cheers guys,
J
jasonnm said:
Hi guys,
I've been a member for ages, but this is my first post - thanks for all the help you've inadvertently given me over the last year or so!
I'm a bit of a Cyanogenmod groupie - I almost always install the latest nightly builds on my I9300, several times a week at least. Apart from the odd camera glitch here and there, I've never had any serious issues, and I absolutely love it - so much nicer, cleaner and more responsive than stock.
But the last 4 or 5 days, when I've updated to the latest nightly release, I get loads of SuperUser errors, and Tasker seems to have completely vanished, along with the few widgets I have created to go with it. All that is left are Android icons, with a toast error saying "not installed" when I try it.
I also can't seem to get onto the internet, either via 3g or wi-fi, but I think that is a local problem with my router...
I would re-download Tasker and reinstall it, but why should it vanish in the first place? And when I try and restore it from my Titanium backup, it just takes forever and never finishes - this makes me think the new nightlies are not compatible with the current release of Tasker (or the other way around - d'uh)...
I hope I'm wrong, and just doing something stupid. 'cos I use Tasker a lot and this is stopping me from updating CM.
Any advice appreciated!
Cheers guys,
J
Click to expand...
Click to collapse
Flash the most updated version of 4.3 gapps. The error is "missing some libraries" or something to that extent.
after rownerd
davtse said:
Flash the most updated version of 4.3 gapps. The error is "missing some libraries" or something to that extent.
Click to expand...
Click to collapse
You're a star - it worked like a charm! The only thing that seemed to still be affected was the shortcut to my phone app, which I just deleted and re-dragged to my home screen.
Thanks so much for your help :good:
So I was using the CM11 mod for my fascinate for about 2 months. The first 2 weeks of using it, it was awesome. After that, my RAM was going down for no reason, and i had some problems but i could fix it by optimizing my device.
A few days ago, my phone kept crashing. I kept on getting messages that Trebuchet had failed, Clock had failed, Play Store Services have failed, etc. Today morning, almost everything on my phone failed. It would just keep reloading the home page. I restarted my device several times, but after that nothing would really load.My battery had about 93% charge and i went to school. When it was 3rd period in school, my battery was 15%. I had no applications running. I just turned it off
When i got home, it would load but everything was slow. i optimized, cleared cache and everything but it wouldn't work. When i open an app, it takes a long time to load. The home screen, and menu pop us normally, but the apps are slow. I really dont know what to do and what ROM to move onto next. Im not getting a new phone for a while, and i really need help.
What ROM should i flash? I need something stable, that wont have problems like this. I also like to use Facebook a lot.
Please help me with my problem because i really want my phone to work. I bought the phone for $200 and it was a bad decision, since all these problems started occurring. What ROM would be the best for me?
@samsung striker
Wow, you have a lot going in there...
Hopefully when you say cm11, it's the version from unjust 06/04/14
That thing is ridiculously stable...
I'll start off with this, Facebook and any fb messenger apps are huge memory hogs.
Next, i saw you mention optimize several times, what program are you using to do that with?
The particular problem i see with the fascinate right now is browsing and using social media sites fill up the cache folder quickly. When that happens the phone well act like you have described.
You can easily fill the cache on one or two days depending on how heavily you browse.
At a minimum, what i think you need to do is boot into recovery and wipe cache and davlik.
Then reboot and let it rebuild things, if things don't smooth out within 15 minutes of booting up, go ahead and reboot again to see if it clears up.
It's very possible if you filled up the cache it probably tried to write information somewhere else and why it freaking out
I would recommend ever other day wiping cache from in recovery and you should be real safe with things and the ROM would be very stable.
If you have done that and are still having issues,,,
Or if you at ready to sacrifice losing your call history and text history and apps etc,,, Go ahead in recovery and do the factory reset,,, it will wipe your apps and stored data (not download items like music or zip files) & put everything back just like you did a fresh install of cm11, so you have to set up all your preferences and gapps and other apps you want all over again
.
Yea i use Facebook a lot. I like to download a lot of apps and most of the time it works fine, but sometimes these problems start to occur, followed by a lot of lag.
When i optimize my device, i optimize it with this program called "Smart Booster." I also use this other app called "Fast Reboot."
Anyways, ill try what you suggested and see if it works well. If it doesn't work out for me, do you have any other Rom's in mind that are better for me?
Thanks.
I had the same issue pop up a week or two ago. Cleared cache and Dalvik on a semi-regular basis (although I probably browse less than it sounds like you do) but it didn't do too much for me. Ended up on the most recent CM 10.1 nightly and only installed the apps I use regularly instead of my usual restore of every app that had a TiBu backup. It's been working great for me over the past week or so. Personally, I couldn't handle the data drops on CM 11 any longer either, so CM 10.1 has been a good solution on that front.
layjn said:
I had the same issue pop up a week or two ago. Cleared cache and Dalvik on a semi-regular basis (although I probably browse less than it sounds like you do) but it didn't do too much for me. Ended up on the most recent CM 10.1 nightly and only installed the apps I use regularly instead of my usual restore of every app that had a TiBu backup. It's been working great for me over the past week or so. Personally, I couldn't handle the data drops on CM 11 any longer either, so CM 10.1 has been a good solution on that front.
Click to expand...
Click to collapse
How did you go back to CM 10.1 Nightly? Did you just download and flash it? Im worried that somethings gonna happen since im going to JB from KK. I wanted to try the PAC man Rom.
layjn said:
I had the same issue pop up a week or two ago. Cleared cache and Dalvik on a semi-regular basis (although I probably browse less than it sounds like you do) but it didn't do too much for me. Ended up on the most recent CM 10.1 nightly and only installed the apps I use regularly instead of my usual restore of every app that had a TiBu backup. It's been working great for me over the past week or so. Personally, I couldn't handle the data drops on CM 11 any longer either, so CM 10.1 has been a good solution on that front.
Click to expand...
Click to collapse
Also, Can you please post the link for the CM 10.1 Nightly? i cant seem to find it.. Thanks
Grab the latest nightly from the CyanogenMod site - I PM'd you the link since I can't post them here.
I booted into recovery, wiped data/cache/dalvik and installed the zip. It failed, I rebooted back into recovery, and installed the zip again and it worked without a hitch. Very similar to flashing CM 11.
layjn said:
Grab the latest nightly from the CyanogenMod site - I PM'd you the link since I can't post them here.
I booted into recovery, wiped data/cache/dalvik and installed the zip. It failed, I rebooted back into recovery, and installed the zip again and it worked without a hitch. Very similar to flashing CM 11.
Click to expand...
Click to collapse
Yea thanks for the help
So i flashed it, and it was working pretty good. I downloaded a few apps such as Messenger, Kik, TB, Smart Lock, and Clash of clans. It was working well, until i used Facebook Messenger, which made it lag just a little. I used clash of clans, and it did lag a little so i had to get Smart Booster, and optimize.
I like to download a lot of apps so im not sure how my device would handle it, since im experiencing a little lag from these few apps. Did you download similar apps as me? Also, do you like to download a lot of apps? Im just asking just to see how well your Fascinate runs compared to mine.
Again, thanks for the help. My Fascinate runs better now
Im gonna try to get a custom kernel and see what happens.
I found that when I installed ALL of my apps that the phone would slow down significantly. I just have the essentials now - a few games, a few social apps, and some other items, well below what I had earlier. The Fassy didn't respond too well when I had a ton of apps on there, so I scaled back and it seems to be working a lot better for me. The single-core can only handle so much - hopefully Devil or another kernel will help you out if you need additional apps!
layjn said:
I found that when I installed ALL of my apps that the phone would slow down significantly. I just have the essentials now - a few games, a few social apps, and some other items, well below what I had earlier. The Fassy didn't respond too well when I had a ton of apps on there, so I scaled back and it seems to be working a lot better for me. The single-core can only handle so much - hopefully Devil or another kernel will help you out if you need additional apps!
Click to expand...
Click to collapse
Yea that's the bad thing about the fascinate, and i don't think there are any kernels for Cm 10.1 because I searched online, and couldn't find anything.
Check out HHP's thread in the General section - plenty of JB kernels to choose from. I think Devil was the most widely liked from that group if I remember correctly.
http://forum.xda-developers.com/showthread.php?t=2149067
layjn said:
Check out HHP's thread in the General section - plenty of JB kernels to choose from. I think Devil was the most widely liked from that group if I remember correctly.
http://forum.xda-developers.com/showthread.php?t=2149067
Click to expand...
Click to collapse
Thanks