Related
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk
I am so glad I didn't update to 1.0.7!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App
Hey
I'm running DK 4.4, and my phone just appears to be randomly freezing while it's in my pocket.
I should note this has been happening with other roms as well, so I seriously doubt it's a rom issue.
I'm not overclocked (anymore).
The screen just won't turn on.
People can even call me and to them it seems like it's ringing, but it's not and nothing happens.
The only way to recover from that seems to be to take the battery out and put it back in.
I finally managed to catch it in action and have a look at the log, but I couldn't find anything useful.
Maybe someone else can
logcat:
http://pastebin.com/kS3EnPQa
Also, I should mention the freeze happened a couple of minutes before the end of this logcat, the log keeps updating even though the phone appears frozen.
adb shell doesn't seem to work, though, and neither does adb reboot
Thanks
Hi. Flash an old 2.1 stock RUU original rom, root again and check if the phone works. Sounds like a Software or Hardware issue. Otherwise you can try to wipe phone and test the DK ROM again.
Do you use cache to ext? Download and install free app ap2sd GUI from Market and move cache back to internal. Maybe your sd card should be Checked too.
Do you use the default dk Kernel without over or downclock under 3cxphone MHz?
Sent from my HTC Wildfire using Tapatalk
Fair enough, I'll try it.
I'm curious, though, are you actually seeing something in the log?
As for the cache to ext, my dalvik cache used to be on my SD card, but I already moved it back thinking it might be the issue
EDIT: as for the kernel, I use the original DK one (iirc that's the original HTC kernel?), shouldn't be over/underclocked.
I had this same issue and was about to return my Wildfire, but then the microSD died! So I got a new one and its been fine ever since so maybe try another card if you can and if the above suggestion doesn't work.
Sent from my HTC Wildfire using Tapatalk
Thanks for the suggestions!
I'll be sure to try them. Maybe my Wildfire isn't on its death bed after all
Your not the only one my GFs phone has the dame prob plz do let me know if u manage to fix it. Thx
P.s. her phone's completely stock no root no nothing.
Sent from my Desire HD using XDA Premium App
It definitely seems like it's the SD card.
I tried using a different one and I haven't had any problems for about 48 hours.
Will update if it changes
Thanks a lot for the suggestions, guys!
gbesso said:
It definitely seems like it's the SD card.
I tried using a different one and I haven't had any problems for about 48 hours.
Will update if it changes
Thanks a lot for the suggestions, guys!
Click to expand...
Click to collapse
Thank YOU for keeping us updated
For the past 3 days, periodically throughout the day, I get a notice the Google Services Framework is unresposive and must force close. My question is...
1. Is it something important I should be worried about?
2. Is anyone else getting this?
3. Is there a specific app causing this?
3a. If not, I there a known cause?
4. Is there a fix?
Btw, I am using a nonrooted Epic. I did search. And all help is greatly appreciated.
Sent from my non-rooted Epic 4G using the free XDA App
I had this problem after dropping my phone and having the battery pop out while running.
I went into Settings / Applications / Manage Applications / All, then I found Google Services Framework, opened it and clicked "Clear Data", and that seemed to fix it (note, it took 2 days for the Android Market to show anything under "My Apps")
Note, I'm rooted on Bonsai 4.1.3. This "google services framework" FC occurred even after restoring from a prior CWM backup oddly enough which is why I decided to try clearing the data in Applications.
Good luck, hopefully you have a backup in case my idea blows up your house.
I have been getting random vibrate, pause then three more vibrates like something is force closing but nothing shows on screen. I also have had maps force close several times. I am on eg22 rooted.
Sent from my SPH-D700 using XDA Premium App
I have gotten this force close a few times and wiping everything 3x and restoring a nandroid didn't work for me 9 times out of 10. I ended up having to use Odin to get rid of it. Hopefully just wiping the data works for you otherwise Odin may be the only way to get it fixed. So, try wiping cache and Dalvik 3x first. If that doesn't work, try wiping everything 3x and restoring a backup. If that doesn't work, try re-flashing the ROM and finally the last resort is Odin
Sent from my SPH-D700 using XDA Premium App
I am not using any roms, nor is my phone flashed with anything. Its stock EC05. It appears to have rectified itself but I'd still like to know what's happening to prevent it again.
Someone I know had this same exact problem a few days ago. Wiping the data for Google Services Framework fixed it.
This happened to me a few weeks ago. Clearing data is the best fix for some, for me however it just made my launcher loop-crash. If clearing data fails, go into cwm and 'fix permissions'. This got me back on my feet
Sent from my Syndicated Epic using XDA Premium App
Happened to me last night and Odin was my only fix. Tried fixing permissions, clearing data, neither worked for me. Issues still remained after a nandroid restore
Sent from my SPH-D700 using XDA Premium App
MY phone tends to overheat when on calls outside at lunch and 20% of the time this is the result when I reboot. And sometimes the fix permissions works and sometimes it doesnt. If it doesn't I was reodin'ing to fix it.. Sucks for when you are not around a computer when this happens.. My fix to a computer free solution was to keep a copy of the ec05 reRFS.zip on my sd card. I can hop over to clockwork and flash this and it will at least take me back to a stock rooted and working phone until I can get back to a computer or whatever....
I have also experienced this annoying issue and my only fix was odining as wel
So rooting my phone is the only fix if clearing the data fails?
Sent from my non-rooted Epic 4G using the free XDA App
No you don't have to root. Just odin the ec05 tar. You will lose all of your data because it basically reinstalls the os it's like starting over. If you do root you can use titanium backup and that will save all of your apps and data.
My epic does this on every custom rom. So I went back to stock no more problems.
Sent from my SPH-D700 using XDA App
Elite11b said:
No you don't have to root. Just odin the ec05 tar. You will lose all of your data because it basically reinstalls the os it's like starting over. If you do root you can use titanium backup and that will save all of your apps and data.
Click to expand...
Click to collapse
Well... I don't want to loose everything. So far it hasn't stopped functionality. I dunno if this helps but 3rd party apps running are...
Trillian
Lookout
Skype
Go Launcher EX
Go Launcher EX Notification
Google Music
Google+
Blogger
P.S. - as typing this I noticed the crash happens during background syncing
Sent from my non-rooted Epic 4G using the free XDA App
Ok I think I found it. I turn off auto sync and it fine and now it looks like facebook sync is what is crashing. Thanks for all your help..
Sent from my non-rooted Epic 4G using the free XDA App
Incubus has posted a rooted version of the OTA in the Devolpment forums! That is all....
Sent from my ADR6300 using XDA App
but no 2.15.10.07.07 radio yet... i want it to get tested and found good...
mirrin said:
but no 2.15.10.07.07 radio yet... i want it to get tested and found good...
Click to expand...
Click to collapse
The radios don't always mean better signal or faster 3G. They vary by location and phone... the leaked radio sucked for me and the 11.19 one seems best so far.
Sent from my ADR6300 using XDA App
And the leaked radio worked best for me, its gunna vary for everyone
Sent from my ADR6300 using XDA App
well i found 5.06 worked pretty well for me but i have been on most of them i only left it because people were saying it killed the wifi on their phones... as long as large numbers of reports of the same thing from 7.7 dont occur ill probably stay on that one...
Can someone who has flashed this try out the speech to text and see if it works properly?
Navigation or anything. Texting or anything. It some of the GB roms with the EVO framework and issues with speech to text.
Well this isn't the EVO GB Release. It's the actual Incredible release. But yes the speech to text does in fact work.
kjsmommy10 said:
Well this isn't the EVO GB Release. It's the actual Incredible release. But yes the speech to text does in fact work.
Click to expand...
Click to collapse
I know. I'm currently on Joel's shooter rewind 3d and working voice search would be the only thing to tempt me off of it.
Sweet
First post on XDA here, I registered primarily to give props to Joel and Incubus.
I grabbed the rooted OTA Incubus posted and flashed it with Rom Manager. Took a lot of patience, but it went pretty smooth. Thanks to you both (and everyone else who had a hand in this).
My DInc is just about to go out of warranty, so I'm going to be trying some other ROMs pretty soon. I'm pretty much locked into the root/S-Off status now, and I'm happy with it that way. I think I'll be hanging on to this phone for some time.
So far I like this update, but I've had a few random reboots. One or two while I was re-installing some of my apps or moving them to the SD card, and at least one while it was just sitting there on the charger.
For the moment, I'm going on the assumption that this is just some early stuff working itself out. When flashing the ROM, I cleared the Dalvik cache, but didn't do a data wipe. Anyone have any idea if this is a problem?
Again, thanks a million guys!
( Oh, LOVE the noob video! )
keyslapper said:
First post on XDA here, I registered primarily to give props to Joel and Incubus.
I grabbed the rooted OTA Incubus posted and flashed it with Rom Manager. Took a lot of patience, but it went pretty smooth. Thanks to you both (and everyone else who had a hand in this).
My DInc is just about to go out of warranty, so I'm going to be trying some other ROMs pretty soon. I'm pretty much locked into the root/S-Off status now, and I'm happy with it that way. I think I'll be hanging on to this phone for some time.
So far I like this update, but I've had a few random reboots. One or two while I was re-installing some of my apps or moving them to the SD card, and at least one while it was just sitting there on the charger.
For the moment, I'm going on the assumption that this is just some early stuff working itself out. When flashing the ROM, I cleared the Dalvik cache, but didn't do a data wipe. Anyone have any idea if this is a problem?
Again, thanks a million guys!
( Oh, LOVE the noob video! )
Click to expand...
Click to collapse
Well first off, welcome! And yes. You should ALWAYS wipe data, cache, and dalvik at the minimum. It ensures that you have a better experience without lag, freezing, FC's, etc.. You have to do the setup every time, but it's worht it and you get used to it. And most devs don't recommend using Rom manager since it's known to have some issues, you're best bet is to go install through your CWM recovery.
kjsmommy10 said:
Well this isn't the EVO GB Release. It's the actual Incredible release. But yes the speech to text does in fact work.
Click to expand...
Click to collapse
I flashed it. Got in my car, sped up to 35 and tried a Voice Search. Like with the GB leak, google voice search throws up its hands and can't understand you.
AJGO23 said:
Well first off, welcome! And yes. You should ALWAYS wipe data, cache, and dalvik at the minimum. It ensures that you have a better experience without lag, freezing, FC's, etc.. You have to do the setup every time, but it's worht it and you get used to it. And most devs don't recommend using Rom manager since it's known to have some issues, you're best bet is to go install through your CWM recovery.
Click to expand...
Click to collapse
Wow, seriously, ALL data? That means having to set up multiple mail accounts (GMail, private, work) and re-installing all my apps - well, Titanium at least.
Initially, I took over a month to get my phone just the way I liked it, and still wound up tweaking the hell out of the look and feel on a regular basis. Can application data backed up with Titanium be restored to get most of that back? Seems like it would take hours to get it back either way. I never found a thread on this, so I apologize if it is answered somewhere - I'd love to get a link to that thread if it is out there.
Now I think about it, this has been the biggest hurdle to my trying different ROMs. Screw the suits whining about how I use the services and devices I pay for, I just don't have the time to be messing with it that much.
Again, thanks for the info!
Cheers!
What did I do wrong? I DL'd the file in the thread, put it onto my SD card, then turned my phone off.
I rebooted into recovery (power and volume down button), chose update from .zip on SD card. Picked the file and let it update...
Now my phone will boot up and just stay stuck on the "Droid" screen. Any help?
was I supposed to rename the file or anything? Please help, my phone is stuck right now...
Install zip from sdcard not update... And u should of wiped data cache all that junk if u didn't do that
Sent from my ADR6300 using Tapatalk
BMWPower06 said:
What did I do wrong? I DL'd the file in the thread, put it onto my SD card, then turned my phone off.
I rebooted into recovery (power and volume down button), chose update from .zip on SD card. Picked the file and let it update...
Now my phone will boot up and just stay stuck on the "Droid" screen. Any help?
was I supposed to rename the file or anything? Please help, my phone is stuck right now...
Click to expand...
Click to collapse
Did you wipe anything? You should do a full wipe (data/system/cache/dalvik/etc.) before flashing a new ROM.
Cant wait for a 2.3.4/3.0 sense Rom.
keyslapper said:
Wow, seriously, ALL data? That means having to set up multiple mail accounts (GMail, private, work) and re-installing all my apps - well, Titanium at least.
Initially, I took over a month to get my phone just the way I liked it, and still wound up tweaking the hell out of the look and feel on a regular basis. Can application data backed up with Titanium be restored to get most of that back? Seems like it would take hours to get it back either way. I never found a thread on this, so I apologize if it is answered somewhere - I'd love to get a link to that thread if it is out there.
Now I think about it, this has been the biggest hurdle to my trying different ROMs. Screw the suits whining about how I use the services and devices I pay for, I just don't have the time to be messing with it that much.
Again, thanks for the info!
Cheers!
Click to expand...
Click to collapse
You can back up app data, but it is strongly recommended that you don't back up system data. And yes it means starting all over, and I too was skeptical to start over when I first started flashing ROMs, but now it takes me about 15-20 minutes to setup everything again. But then again I only reinstall about 45 apps.
Sent from my ADR6300 using XDA App
BMWPower06 said:
What did I do wrong? I DL'd the file in the thread, put it onto my SD card, then turned my phone off.
I rebooted into recovery (power and volume down button), chose update from .zip on SD card. Picked the file and let it update...
Now my phone will boot up and just stay stuck on the "Droid" screen. Any help?
was I supposed to rename the file or anything? Please help, my phone is stuck right now...
Click to expand...
Click to collapse
Boot into recovery and wipe everything 3x. Next choose install zip, then after that DO NOT CLICK ON update.zip, select choose zip from SD, then find your downloaded file (wherever you put it) and select that.
Has anyone tried any Bluetooth devices? Keyboards or such to see if we did in fact get the full bt stack?
Sent from my ADR6300 using XDA App
So I've tried everything I could think of. Reflashing ROM, using a different ROM, different browser, everything minus a different modem, which I'm not sure would really do anything. But where I'm at is that anytime I go to status on facebook it closes the browser back to the home. I'm on Frozen ROM at the moment, I've tried on stock, same issue. Tried on the ASOP ROM, same issue, tried on those ROM's with Dolphin, Miren, Firefox, Stock Browser, all the same issues.
So will a modem actually make a difference is how the phone handles? Or is it more related to data speeds? I don't know what else to do, this is driving me absoluetely nuts. Thanks Guys.
Try this go into settings / manage application / all application & wipe data from browser & wipe data from Google search then reboot if that doesn't work I don't know
Sent from my Nexus S 4G using xda premium
Figured I would move it to the proper area. Haha. I really appreciate all the help Bro. Tried the other route you said, nothing doing. So I don't know either. It's annoying though. I think I got the phone into a bootloop now tried to install a different ROM see if that would work, and doesn't seem to be working. Piece of crap. Just my luck. Ha.`
What kernals were/are you running?
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
odin back to stock
and clear out the sd card. redownload everything and rebackup.
Did you uninstall the Facebook app and redownload it? Wipe data in it before uninstalling. Did you try a different browser like Miren or Dolphin?
xTMFxOffshore said:
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
Click to expand...
Click to collapse
Well, you aren't running without a kernel - the kernel is the core of the Android operating system.
Maybe you're having a hardware issue, such as a touch screen that's acting up (you said it wasn't force closing or anything, right?) - it could be registering false touches in the wrong location... I'm just taking a shot in the dark on this one, since it sounds like you've tried restoring just about everything...
I would suggest reformatting your sd card (copy the contents to your computer first, the card WILL be erased).
Then, Odin a full stock tar (try DI18, you'll get an OTA to EC05 after you boot).
Then use the one click root and recovery - be sure to have the rom on your sd card, especially if you use an ext4 recovery like 3.1.0.1, because of the file system conversion (stock kernel won't boot ext4, so you'll need to flash the rom and an ext4 kernel before rebooting from recovery - Genocide or ACS's twilight zone or vision kernel... I would stick to Genocide for now, under worked the best for me)
You might want to skip the rooting step momentarily, so you can see if the same problem occurs on a completely stock setup.
Finally, I would suggest carefully cleaning your touch screen with something mild - I use eyeglass cleaner (safe for glasses with all the expensive protective coatings), other users here might have other suggestions.
This should cover all of your bases, and if you still have problems, it might be a hardware issue.
I do want to point out that (unless I'm missing something about what you're trying to do) the facebook that you access from the browser is loaded from their servers every time you connect - it isn't software on your phone. It cannot be the older version, not like an app, which has to be updated on your phone. The pandora issue sounds like a different issue, but I still need to test that (had to get to sleep last night, I was passing out mid-sentence, lol)
EDIT: re read the first post... Pandora issue was mentioned in the SRF thread... But it seems you did try stock and other roms...
When you say it closes back to home, I think I misunderstood - I had an issue once or twice where facebook would act up, going back to my facebook home page, but did you mean that the browser simply closes and dumps you back to your phone's home screen?
Because that could be as basic as your capacitive home button registering a false touch (the opposite of the unresponsive button issue we're all used to, lol)... But cleaning the touch surface could still help... Turn the phone off first, and apply whatever cleaner you use VERY lightly... Don't use household cleaners, if you don't have eyeglass cleaner then I would research whether rubbing alcohol is safe for gorilla glass...
Side note - swype suggested "guerilla" glass... made me chuckle...
Sent from my SPH-D700 using XDA App
What he said. ^... Also I would let it
Repartition and reset time when you Odin back to stock. I know most people say not to when flashing some things, but this would be an exception. Also when you flash to stock use the victory.pit file as well as the ROM tar.
Sent from my SPH-D700 using XDA App
All righty. I'm gonna try all that. As really nothing else has worked. I do think it's something with the screen though.....I just can't figure out why it only happens on the NEW facebook. I got her using the APP now she was only using the browser before, but I would punch say four letters it would bump a couple more then close. So you may be onto something with that touch screen registering incorrect keys so would that have anything to do with the contents of the SD card itself? Or is that an actual hardware conflict with the facebook (newer version) of the software? Cause it works fine on the APP. So I guess I'm basically at a loss for how this really makes any sense ,but really appreciate all the help from you guys.