My s3 doesn't keep settings after a restart and basically has never been 100% at it. Eg. Ring tones will revert to default, default application settings get forgotten. Phone has been rooted before but actually isn't right now.
Running 4.1.2
I have done a factory data reset.
Any thoughts?
Due to it being rooted and had a replacement screen im hesitant to return it for warranty
@OP, I closed your other thread in the I9300 section. Use this one please and thanks.
My S3 LTE never remembers which launcher to use. I have to tell it use SPB3Dshell every time I turn it on instead of Touchwiz. Thats the only thing though everything else is .
I`m unrooted and on 4.1.2 stock ROM
Related
ISSUE SOLVED!!!!!!
I just realized I kinda screwed up.
My phone (AT&T Captivate, rooted and SIM unlocked, but still using the ROM that came with the device) got into a wierd state today, and crashed, and wouldn't shut down. So I removed the battery. Since then, no matter what I did, I got constant "Android.process.acore has stopped unexpectedly" messages whenever I tried to do anything of consequence with the phone.
After some searching, I found that the way to fix this was a reset to factory defaults. I did this. Now, my phone isn't really working -- it boots, and I can pull down the notification area, but the launcher doesn't launch.
Here's the thing -- I removed the samsung TwLauncher app via Titanium Backup a while back. I've been using Launcher Pro instead, but I guess that's gone now.
Oh, and to add insult to injury, I still get "Android.process.acore has stopped unexpectedly" when I get a phone call.
So.... what can I do here? Am I totally hosed? Do I have to re-flash the ROM or something? What are my options?
I would say reflash. I cant really tell for sure but thats your best bet. Both newer firmwares offer better battery life anyhow. So you cant go wrong.
Ok... but how do I go about doing that? I've never done this before, and am kinda new to Android. I can't even get to the settings menu.
I think I'd like to go back to the stock Samsung ROM. How do I acquire that? How do I install that on my system?
I'm not looking for people to spell everything out for me -- a nudge in the right direction would be nice, however.
Never mind; I found this thread:
forum.xda-developers.com/showthread.php?t=731989
Back up and running.
The people on this forum are AMAZING!
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
h2whoa said:
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
ArtfulDodger said:
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
Click to expand...
Click to collapse
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
Hate to hear that and you're not the only one to mention swollen batteries around here lately either. Good luck to you!
theAPANT said:
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
h2whoa said:
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
Click to expand...
Click to collapse
Yes the easiest way to get rid of cwm is to flash the stock file. Go to http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G there are, i believe two methods, one using Odin the other flashing something in recovery. Just read. As for cm10.1 camcory is working on it so is smartguy. Even i compiled it but it doesn't boot all the way. Check insomniaforums.org that is probably where it will be posted
Sent from my Nexus 7 using xda app-developers app
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
afwolfpacked said:
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Bluetooth and camera dont work. I'm saying my own personal build doesn't boot yet but I'm trying some stuff. Right now I'm working on aokp 4.1.2 to get that fixed all the way, mainly because i like aokp and I'm stuck on 4.2.2
Sent from my Nexus 7 using xda app-developers app
Hey guys,
I've upgraded from a Xperia Arc to a Xperia SP, hoping for a speed upgrade, going from a 1.0Ghz single core to a 1.5ghz dual core. (a Z(1) was not an option). Strangely, out of the box, the thing felt kinda slow/laggy but I thought "let's give it a try".
Now almost two months later, things haven't been any better. In fact, it regularly freezes completely and while writing this post, I can't even turn it on anymore. I closed the screen, but it doesn't goes on anymore (with 83% battery) .. But that's a different issue.
I'm really hoping what could fix this issue. I'm preparing for a factory reset, let's hope that fixes everything. Yet I'd ask: What more can I do than a complete factory reset. (Does it matters doing a factory reset from inside the phone (@ options > security/storage), the boot loader, or when it's connected to my PC?
I hope someone knows a solution!
Wish I could upgrade to Cyanogenmod, but that would void my warranty (right?), which is absolutely not an option.
Thanks!
Suggestions
First of all,
Are you on Android 4.3 or 4.1.2?
If you are on 4.3, it is expected to be a little laggy or buggy (No offence intended)
For this, what you could do is wait for a new update or downgrade to 4.1.2.
There is also another fix to make your phone a little less laggy.
For that you need to root your phone and edit the build.prop.
Second of all, you can try CyanogenMod without voiding your warranty.
For that you have to backup your TA and then unlock the bootloader. That is how you can use CyanogenMod and then again restore your TA when you are going to a Sony Centre or something like that.
A factory reset may solve somethings but not all. :crying:
Just factory resetted and it freezes on pretty much everything I do.. Just a simple swipe down to open the notification bar freezes the phone for about 2 seconds. Even a Nokia 3310 could handle these simple tasks quicker.. :s
Oh and I'm on 4.3 right now.
Blackvibes said:
Just factory resetted and it freezes on pretty much everything I do.. Just a simple swipe down to open the notification bar freezes the phone for about 2 seconds. Even a Nokia 3310 could handle these simple tasks quicker.. :s
Oh and I'm on 4.3 right now.
Click to expand...
Click to collapse
Flash 4.1.2. I got no lags what so ever
Nanostray said:
Flash 4.1.2. I got no lags what so ever
Click to expand...
Click to collapse
I updated from 4.1.2 to 4.3 in the hope it got better, but it got worse. However, 4.1.2 was a pain in the ass to, where it hangs all the time, taking the keyboard to show up a few seconds (@ SMS / playstore / else) (default and Swiftkey) or just opening the notification tray..
So simply flashing 4.1.2. would not solve it, I'm afraid.
Blackvibes said:
I updated from 4.1.2 to 4.3 in the hope it got better, but it got worse. However, 4.1.2 was a pain in the ass to, where it hangs all the time, taking the keyboard to show up a few seconds (@ SMS / playstore / else) (default and Swiftkey) or just opening the notification tray..
So simply flashing 4.1.2. would not solve it, I'm afraid.
Click to expand...
Click to collapse
Maybe use another tft of the .254 than the one you used this time?
Nanostray said:
Maybe use another tft of the .254 than the one you used this time?
Click to expand...
Click to collapse
I'm kinda unsure what you mean. I'm currently on 4.3 -> .266 (build number right?). This one is still unrooted and, even though someone spoke about backing up the TA, since this is not my phone, but my girlfriend's, I'm not sure if I want to dare that.
If it was my owns, that wouldn't be a problem..
Blackvibes said:
I'm kinda unsure what you mean. I'm currently on 4.3 -> .266 (build number right?). This one is still unrooted and, even though someone spoke about backing up the TA, since this is not my phone, but my girlfriend's, I'm not sure if I want to dare that.
If it was my owns, that wouldn't be a problem..
Click to expand...
Click to collapse
backing up TA means unlocking your bootloader so you can flash a custom kernel. 4.3 is indeed .266, but in my opinion you better flash a 4.1.2 stock rom (build number .254)
intolerable
Here the same thing, updated to version 4.3 and the bugs started ... When my phone battery was charging the night, the screen would shut down and forced me to use the physical reset button. Doomlord installed Kernel 0.5, was even worse, I'm thinking of going back to 4.1, even with the bugs it had, I could still use the phone ...
Let me tell you something,many of my friends that using sony,they will complained something was wrong like self restart,becoming typo while charging(touchscreen loses accuracy) and laggy+freezing when they was bought it not more than 2 weeks,and then they don't feel these problem anymore after about 2 months,i think you should go to sony service center,1.3 Ghz dualcore shouldn't freezing,it might a hardware problem or buggy software,hope this help,dont forget to click thanks sorry im just need thanks
Sent from my N986 using xda premium
Hi,
I hope I won't get blasted for my questions having been asked before but I did search and couldn't find anything exactly touching on what I wanted to ask about...
So I have a Galaxy note, n7000 model, and at one point I did flash a custom ROM, but for some reason or other the phone stopped functioning properly.
So I then went back to my original ROM (I'm in the UK), and the phone's performance is extremely sluggish, even right from a reset, everything lags, launching the app menu, loading apps, switching between main screen pages, etc.
I don't know why the phone has become so slow it used to be a fast competent phone for basic OS functionality I've described.
My question is, does anyone know why this might be?
I don't believe I reflashed a stock kernal when flashing the original ROM back on, could this be the problem?
Or is there any other reason the phone might now be slow?
And any advice as to how I can get it working with the performance it used to have, would be much appreciated.
Thanks again for