All those with the SXS on AT&T, have you guys upgraded to ICS via PCC? I got the message last week that the update was available, but I'm curious to know if all-mighty AT&T is going to somehow recognize our devices because of ICS?
Any issues that you have encountered?
I've read some of the positives, so I just want to make sure that it's going to work properly.
Thanks!
Haven't had any issues. Tethering still working as well for me without a message from AT&T.
Thanks, I just wanted to make sure that I'm not going to run into any issues when I upgrade...just a bit paranoid is all since this is my first Android phone
Just finished the upgrade to ICS (Build number 6.1.A.0.452).
When it asked to plug in the phone while holding down the down volume key, it didn't do anything. I unplugged it and tried again and then it started the upgrade process. It probably took about 10-15 minutes to complete and another 2-5 minutes for the initial boot up of the phone.
I noticed that everything was kept in tact (contacts, call logs, wireless ap, downloaded apps, etc) so that was a good thing.
So far, everything is working as it should.
I logged in to AT&T's OLAM and it is showing as an unknown device...for the moment. I'll check again later.
Related
So I've had a S3 for about 6 months by now, and at first, it was running pretty smoothly. Few weeks ago (might even be a month by now) the JB update came out for my phone, so I installed that. Over the past two or so weeks, my phone has been laggy as hell, including random resets. I get a few restarts which the phone does itself, without any input from me. I'm also getting a serious lag whenever I'm attempting to type a message. I'll be able to type my whole message out, but it hasn't shown up on the screen (so the phone's manage to register the touch prompts I make, it just shows them on a 5-10 second delay). This occurs even when the only app I'm running is the messaging one. Further lag issues include receiving messages. My phone will vibrate, then some 5 seconds or so later the message will finally be received by the phone and my ringtone goes off.
I've tried doing a hard reset on the phone, and that hasn't changed anything. Could it be hardware related?
And I'm currently running the stock Aus unbranded ROM, unrooted, no mods (XSADLK3 I think)
I had this issue on my sgs2 when upgraded to ics, only fix at the time was to take back to my carrier for a re flash (they told me if I flashed it myself I'd void the warranty). Dunno if that helps at all.
It could be. Try updating to the latest JB firmware first though.
jimbo1531 said:
I had this issue on my sgs2 when upgraded to ics, only fix at the time was to take back to my carrier for a re flash (they told me if I flashed it myself I'd void the warranty). Dunno if that helps at all.
Click to expand...
Click to collapse
Well, I called up Samsung support earlier, and the guy kept suggesting I just restore the phone. Which I had already done at that point. And the carrier I'm on doesn't have a store where I live, I'd have to mail it back to them, have their guys take a look at it and either can my contract or send me a new one
Hi all this is my first post, nice to meet you all.
Last week I connected phone to Kies and it asked to update to XXELLA (JB) so thought Ok I'll update it. At first was very impressed with some new features etc but my phone has since developed a few rather annoying problems.
1) Battery seems to go much quicker with no extra usage from me. Using the phone the exact same way.
2) Mobile data intermittently stops working after you come off the internet or an app no longer requires a connection. It will be turned on in the setttings but no 3G symbol on top of screen
3) The most annoying issue with this phone now since update is when the above happens (3G turned on but no connection) my phone will not send/receive text messages and will not call out.
I have to power cycle the phone to correct it (restart)
Just to let you know my phone is now rooted but this wasn't done til a few days ago and problem was happening before this.
P.S. I don't know if this has anything to do with my problem with texts etc, but a few weeks ago now I tried calling a mate on O2 only to be joined into someone elses conversation. We both could here the other person but they couldn't here us and I couldn't hear my friend either. Ended the call then rang my friend again and was fine. Just a bit scary that you could be in someone elses conversation unknowingly these days, and you wouldn't have a clue.
Any solution to my problems, other than to revert back to ICS instead of JB are welcome.
As this is a Samsung update contact Samsung service centre .
Or try a factory reset or join XDA and flash stockJB firmware are your choices .
Root voids Samsung warranty
jje
My phone has improved slightly instead of locking up reception as I'll call it when data turned on, it now works for a short while then stops working where as before it was as soon as it was activated.
I'll keep an eye on it and if it doesn't improve i'll unroot and contact samsung or get a custom rom put on and see if that improves things somewhat.
thanks
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
TallgeeseIV said:
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
Click to expand...
Click to collapse
This topic can be closed now. I looked up a video (http://www.youtube.com/watch?v=FfvOTFssDMM) of the swapping process and saw how easy it is, so i just went ahead and tried it, and it totally worked, so now it's charging fine again. Thank you to anyone who viewed this and hopefully this can help someone in the future.
I didn't read all of that. I was at a concert last night. But here what I know about the not charging thing.
In my experience
1.all the good galaxy phones do it.
2. Its not that it wasn't charging. Its that vzw turned the power up on the modems. If your in a low service or weak signal area your phone will actually drain the batter faster then you can charge it.
So if you notice this is happening. Switch your phone into airplane mode. Or turn off mobile data and let it charge for a while.
I have read about a few case's where the usb ports where disconnected. But I think the crazy fast radio battery drain is way more common.
I don't know if its the same for other carriers but I know a note guy a s4 guy and 2 other note 2 guys we all had the same problem with it.we are all Verizon too.
The original modem flash helps a lot but the 2nd one that went out ota is stronger in weak signal areas so we all use it and turn off our data if it gets to much.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.
Sunday evening, I went through HELL fixing my phone. Once I realized a text wouldn't go through, I tried the data and calling. Only data worked. I've rooted my phones since the Evo 4G and never had this issue before. I called Sprint at 3:30pm, spent an hr which got me nowhere and actually made it worse. She told me to do the ##72786# which shows the MDN and MSID. I've done this in the past for activation sake on previous phones, on the M9 it doesn't allow you to manually change the values which was a major problem. Once i did the reset, both values were the same and incorrect. At this point I was like OH SHIIT, cause I just realized you can't manually input the values. And because those values have to be your number, I knew was screwed...after the restart I lost my LTE as well since Sprint didn't know this was my phone due to no MDN/MSID values. I thought for sure I would have to do a new fresh install which I did NOT want to do as everything with the phone was perfect and a fresh install takes a looot of time to backup everything, reinstall, make sure settings and everything are like before. I told her to activate my S7 and reactivate the M9 to see if that did the trick to force the M9 into hands free activation and push through the MDN/MSID. I wasn't hopeful at all since I activated the M9 BEFORE I rooted it just to be sure and also cause I bought it off ebay so had to make sure all way well.
Once i got off the phone, I started searching on google/xda for a solution. It's quite a specific issue and similar ones were sparse and had a range of reasons for the issue. Mind you, all was well before this, it's basically the stock Venom rom, no major tweaking and this issue just randomly appeared for no apparent reason. I never used Titanium Backup up to this point(1 yr using the phone) or any Rom backups so I was like, might as well since I'm gonna have to start flashing to see if it fixes it. First I flashed the venom rom to see if a fresh flash did the trick...possibly the clean install requests MDN/MSID from Sprint to get the phone working. Didn't fix it. Next, I flashed the stock rooted rom which thankfully I saved when I first rooted the phone. Phone booted up, BINGO! Instant 4g connection. Phew, thank God. Then, I flashed venom again but with a full wipe to see if the stock install carried the MDN/MSID over, didn't fix it. I was so pisssed cause at this point I knew I was screwed.
Mind you, backing up/flashing and at the same time searching and trouble shooting is VERY time consuming! A fresh flash/boot alone takes maybe 10 min. I was also doing some extensive searching for the best SMS/MMS backup out there as I always keep my text records(which I'm making another thread to discuss). It's almost midnight and im PISSSED. My entire Sunday evening wasted and a random stupid problem on my phone that came out of the blue for NO reason. I'm guessing Sprint did some network update and the phone need a Profile/PRL update which it couldnt get. Not sure how that works.
I can't find the thread it was mentioned in, and I searched MANY, but someone mentioned the Sprint PRL patch(for a different issue) in Venom Hub. I didn't think that would do anything as that's preferred roaming list. I had nothing to lose and it was a Sprint specific patch so I tried it. I never used Venom Hub as I mentioned the phone is pretty much stock venom so I didn't know it was there. Prior to this I checked Venom tweaks, nothing of course. Phone restarts, still no data. I go to the settings mainly to see "phone information" and what do you know, "System Updates" is there. I click Update Profile, phone restarts, and BAM we are back online! You have no idea how happy I was! Was able to keep my phone as it was with no wipe/fresh start!
I don't know why software updates was removed in the first place! That's why I NEVER had this issue or data/call/text issues on previous phones, as I would periodically do a Profile/PRL update for good measure. Any1 know why it was removed?!? This is a vital feature to have on the phone! Mind you I never had issues, but you have no other options once you do run into an issue like this other than to do the Profile update. I don't see why they removed it, it's not bothering anything or taking up space/resources/etc. To my understanding from prior phones and years of rooting, it's standard procedure to do Profile/PRL updates from time to time to "sync/update" the phone when network/tower updates are done with Sprint.
I know this post is looong, but I literally spent from 3:30pm to 1:30am this Sunday talking to Sprint, flashing, backing up, researching. I was beyond pissed as the hrs went by with no solution on hand(I did NOT want to start fresh). This is my first post ever and my first time becoming a member for this reason. This issue is rare as I never, ever had an issue like this, but if any1 else out there runs into it, I hope they find this thread!