Related
Hello,
I've been experiencing annoying freezing up issues with my second-hand Glide. In all cases, the freeze happens with the screen off and a race condition ensues discharging the battery (even when plugged into power). Searching around, I've seen a good number of references to this problem:
androidforums.com/samsung-captivate-glide/462710-freeze-ups-anyone.html
gsmarena.com/samsung_i927_captivate_glide-reviews-4071.php
comparecellular.com/cell-phones/galaxy-s-glide
but I have not been able to find any resolution. Sometimes I feel like this: xkcd.com/979 . In essence I'm trying to determine if this is a hardware fault or something which can be fixed by software. Seeing minimal Glide development does not help since there are very limited options for ROMs. Since this device did get a nod for ICS, there's still hope in that, but until then have to suffer.
Anyone seen a resolution other than exchange? Warranty?
Unfortunately, this is quite common but there are few users that did not had any freezes since day one of their Glides.
One issue is, you have your Google calendar sync and you have "Auto Sync" active. This leads for the Calendar to Sync improperly during sleep mode resulting in a sync loop, which makes the device unresponsive thus, wont wake up upon pressing power/lock key. Solution, uncheck the "Auto Sync" function in Settings, Manually sync everything, or uncheck the "Sync Calendar on your Google account.
The other thing which is very common, is leaving wifi on while charging. This results on the same issue above but the reason is not clear. I experience this one in 1 out of 5 chances, so I turn wifi off or set the wifi sleep policy to "when screen turns off" in Settings. Happens on stock and custom ROM(s), except when Cranium Kernel is flashed.
In conclusion, I never thought that these are hardware issues ATM, for my previous Samsung devices also have these, but is eliminated by updating firmware, or flashing a custom ROM.
Thank you for the suggestions. I will verify wifi sleep policy as well as disable calendar sync to see if it helps. And now that there is some activity regarding ICS for this unit, maybe I'll get to test a new ROM to see if it helps.
thanks again
Neither unsynching google+calendars, or the WiFi+charging solutions worked for me.
Is there any hope for those of us with no immediate remedy?
Has Samsung even acknowledged that this is an issue?
When do you predict us getting an ICS update that will solve the issue?
Its a damn shame since I'm ****in loving this phone so far, yet i can't even use it when I want to sometimes.
Well yeah....I can confirm. I reflashed my device and restore my apps...did not do any mods and whatnot. Used it for a day and charged it overnight, no internet. And bam! Sleep Death. Like i said, this is common, and does not think that this is a hardware issue for a lot is experiencing it. So for now, dont left your glide charging overnight, or if you will, download a night clock, or use the stock desk clock. You will have a clock beside you and will keep your device awake all night.
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
wLnston said:
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
Click to expand...
Click to collapse
The issue you addressed is so called "sleep death." A few weeks past, ATT announced that 10 of their devices will get ICS in less than a month (including the Glide). No word from Rogers when will they update their version of the device.
Unfortunately AT&T did not state when they would push the update as well they only named the devices that will get it.
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
wLnston said:
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
Click to expand...
Click to collapse
I believe Samsung is already knowledgeable about the issue....unfortunately, it is not that easy to make a software update just to solve 1 problem (on the contrary to the Captivate SGH-I897 with GPS issues on Eclair, ATT immediately released a FW update within less than 2 weeks to fix it). And, even though I said the Sleep Death is quite common, not all of the users have this, so again, maybe unless a considerable large number of users (or all users) experience this, they might look into it. So I also believe that Samsung (along with ATT/Rogers) will correct the issue on the next update. When? Heaven knows.
If you are experiencing the sleep death more than twice a day, without doing anything, or if you believe non of your installed programs is at fault, and you are still in your return period, I suggest you exchange your device. You might get a unit that is unaffected. My Sleep Death only occurs when I left the phone charging for extended periods of time, like charging overnight which I always do. As I've mentioned, I keep the device awake like installing a night clock application or activating the stock desk clock app.
Well I'm going to try turning on the night clock app this night and see if that stops the sleep death.
And I bought the phone second hand off craigslist. Even if its within the 90-day period, I doubt I'll get any warranty/return ability as I am not the original customer.
interesting problem, will this should hold me back from buying it when my friends will be in the states?
taiber2000 said:
interesting problem, will this should hold me back from buying it when my friends will be in the states?
Click to expand...
Click to collapse
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day (on the contrary of the OP's post). In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
gabby131 said:
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day. In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
Click to expand...
Click to collapse
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
dudejb said:
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
Click to expand...
Click to collapse
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
i have a therory about that, as some other user mentaioned when they useed adracat kernel (that is OC) the problem is gone. maybe samsung uses a underclocked tegra2 prossesor and that tha problem.
gabby131 said:
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
Click to expand...
Click to collapse
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
dudejb said:
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
Click to expand...
Click to collapse
this is exactly what I am experiencing....and I can replicate this issue about 8/10 times....well this should hopefully be fixable via FW update (like my SGH-I896 from 2.1 to 2.2).
Yes I have CWMR installed and is very handy....I am now going back to flash OsiMood ROM for I think I already know what triggers the Sleep Death specially in stock ROMs....
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
wLnston said:
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
Click to expand...
Click to collapse
Some people have stated that once you install a Rooted Rom you will no longer get pushed the updated from your service provider. They stated this from Gingerbread 2.3.5 to 2.3.6
In order to go back to stock you have to somehow back up what you have before you flash anything or find it on the web. I am not sure about this but have heard of others doing this.
Your other option is use a ROM that someone cooks with ICS when it becomes available. I have heard of many people toying with getting this set up.
I've updated from a rooted stock GB ROM to the ICS update. I'm surprised this is the update Sprint/Samsung released for the phone. The GB ROM was stable and clean, this one seems to have some issues... primarily:
1) Battery life is 6-7 hours LESS - at least.
One thing I've noticed here is that "Android OS" is using about half of the battery. Previously (and confirmed with my buddy with his GSIII), this only used about 4% or 5% . I suspect this is a culprit.
I've attached some screenshots showing this.
Almost no use of the phone all day, I was at work - some light texting later in the day. So little that SMS or GoSMS don't even appear on the chart.
2) Swype keyboard issues.
Yes, you can clear your app cache for swype and get it to work. However, you apparently can't get copy/paste/select word/select all to work.
When you click on text and click the little handle that appears, only a small box appears above, which is where the menu should be for copy/paste/select word/select all should be. At least I think that's the options - from memory, since I don't have them any more. :crying:
I've attached a screenshot showing this.
[EDIT: This is a usage issue - I consider this more difficult than before, and quirky in that it doesn't always work, but generally if you press and hold text, it'll open an edit panel where the notification bar is. Sometimes double-clicking works.]
3) Signal issues.
Again using the Battery screen - I'm seeing some very odd patterns both with carrier data signal and wifi. Previously, carrier signal was an uninterrupted line, of varying shades of green that corresopnded to signal strength. Now, when I look at this line, there's some very good sized breaks in it. That's a sharp contrast to how it used to be.
I know that searching for signal can use battery - maybe an issue with the radio? modem?
Same for wifi - I used to have a setting for "wifi off when screen off". Now it's gone, or changed - I see a "wifi on while sleep" that is checked. Despite this setting remaining constant, I see periods where that seems to be happening (later), but also a long period where wifi is active despite the screen off.
I've attached a screenshot showing this. See the "mobile network signal" line in the plot.
4) General, observed quirkiness.
Screen not being as responsive. When I press the power button on my phone now, it takes 2 or 4 seconds for the screen to activate. Touching the screen sometimes results in a very laggy response... enough time to poke the screen a second time. Skippy/unsmooth screen transitions in some cases. I've had GoSMS vanish on me a couple times and I had to relaunch it. Other apps become unresponsive and I've had to hit the home button repeatedly - sometimes 10-15 seconds before the phone comes back to the home screen and out of that app.
The screen captures were taken throughout the day - the times appear on them.
I've also attached two BetterBatteryStats dump files - one of them I had all options checked, the other just the defaults. They were taken about the same time, and about the same time I took the 8 hour screen cap.
If it matters, I'm using Go Launcher EX, it's still my stock launcher. I'm noticing not many people on ICS using it - are there known problems?
This is frustrating to me - I use this phone for work, I came off an AOKP ROM to get back on a stock ROM, for two things:
1) stock stability and battery life.
2) the Exchange account options for sync scheduling (on peak/off peak schedules for sync) that only seem to be in the stock ROM.
[EDIT: I performed a full factory wipe several days ago, and reinstalled all apps via market, and still are experiencing these exact symptoms. No improvement. May restore my nandroid from before the wipe just to gain back a few things I inadvertently lost as this didn't resolve anything.]
Accordingly, I'd like to see this ROM working. Any thoughts on these?
Anyone else observing these symptoms, relative to the stock GB rom?
5) GPS changes/bugs
I've also noticed some GPS changes / bugs that I'm not liking.
The GB GPS sucked, now this one seems worse:
Driving tonight, I had to reboot my phone to stop my eternal wait for "searching for GPS" in the car. No different than I've occasionally had to do with the GB rom.
However, then when I made a couple wrong turns or deviations from the route, it got stuck on "recalculating". Eternally.
I know I was in an area with good data, because I exited the Navigation app, relaunched it and picked the last destination and it calculated the new route instantly. It didn't successfully recalculate once... three times I had to restart the navigation app.
Also - the old navigation app used to tell you "...in a quarter mile, exit on..." and "...in 100 feet, turn onto..."
This new navigation app does no such thing. It just says "turn right on _____ street". Which is useless if there's no street sign (hence several of my "recalculating" incidents).
Bump - anyone experiencing these bugs? I haven't seen them reported - any of them.
Looking for something to try to resolve one, or all of them.
Any suggestions are appreciated, thanks.
geolemon said:
Bump - anyone experiencing these bugs? I haven't seen them reported - any of them.
Looking for something to try to resolve one, or all of them.
Any suggestions are appreciated, thanks.
Click to expand...
Click to collapse
I have had HORRIBLE battery life since the upgrade. It is worse than half of what I was getting prior to ICS
My GPS is working like a bauce though, finds my locations within seconds.
My boss got the upgrade last night and has Go Launcher and their suite of products on his device and he can't send texts now
I feel accomplished if I've stumped all of XDA... :silly:
I did discover a workaround for the copy/paste/select issue - long pressing in ICS opens a menu at the top of the screen for that.
However, still stumped on
1) 6-7 hour battery life reduction
3) signal issues
4) Quirkiness/freezing/sputtering responses
5) GPS issues - both signal and new app
Anyone else but me experiencing any others besides #1?
geoleomon - I would suggest grabbing XDA's version of Better Battery Stats, and monitoring your battery life that way rather then using the Android version.
But yes, I have experienced some of the battery issues, just no where near to that extent (maybe 4 -6 hours less).
GH0 said:
geoleomon - I would suggest grabbing XDA's version of Better Battery Stats, and monitoring your battery life that way rather then using the Android version.
But yes, I have experienced some of the battery issues, just no where near to that extent (maybe 4 -6 hours less).
Click to expand...
Click to collapse
Where do I get that one? (I paid for the full version of the Android market version)
What's different about it?
geolemon said:
Where do I get that one? (I paid for the full version of the Android market version)
What's different about it?
Click to expand...
Click to collapse
Nothing, except this one is free.
http://forum.xda-developers.com/showthread.php?t=1179809
Hmm.. Weird I've had the ota installed for a day now and my Android os is averaging 10-15% at the most
Sent from my SPH-D710 using Tapatalk 2
GH0 said:
Nothing, except this one is free.
http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
I've previously posted my results from the paid full version of the app... see the original post, two text files attached.
(one complete, one over-complete)
Anything out of the ordinary in there? What should I look for?
thanks-
Another piece of the puzzle:
I was using the camera, and it crashed - an error I didn't capture but something like "media server crashed - camera must restart". Happened twice before the camera actually started OK. Perhaps significantly, I had the phone docked when I fired up the camera - desk dock.
Also, noticing that listening to music in my desk dock at work, several times now the song has just stopped playing a few seconds in, and the media player closes. I restart the music player, and everything is OK. Sometimes that happens 2 or 3 times before the player works again, and then sometimes it'll happen an hour or so later even after it does start working again.
Could this be related?
try this then report back I have none of these issues you speak of but I am generally in a good signal area. Your signal looks awful, defiantly will cause battery drain.
http://forum.xda-developers.com/showthread.php?t=1721229
riggs170 said:
try this then report back I have none of these issues you speak of but I am generally in a good signal area. Your signal looks awful, defiantly will cause battery drain.
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
I used the "nodata" version of that kernel to install CWM after rooting.
This will wipe my phone, which I'm looking to avoid doing if possible, if that's not the "nodata" version I already have.
Can you clarify on what you are advising?
Interesting though - a coworker suggested possibly if I wipe my phone it might clean things up.
I have just cleared my Dalvik cache, however I believe I did this before. I'm doing this now noting that as per my prior post, I'm seeing a few things force close, or else stop suddenly (like music player) without closing.
Also using CWM to "fix permissions" (not quite sure what this means).
We'll see what my results are after this.
I'd like to get this stock ROM working well if at all possible - if for no other reason than the Exchange peak/off peak email sync settings that don't seem to exist in other ICS ROMs.
I wish a mod would sticky a battery life complaint thread and close all others. Every other thread is an ics battery life complaint.
Sent from my SPH-D710 using Tapatalk 2
geolemon said:
I used the "nodata" version of that kernel to install CWM after rooting.
This will wipe my phone, which I'm looking to avoid doing if possible, if that's not the "nodata" version I already have.
Can you clarify on what you are advising?
Interesting though - a coworker suggested possibly if I wipe my phone it might clean things up.
I have just cleared my Dalvik cache, however I believe I did this before. I'm doing this now noting that as per my prior post, I'm seeing a few things force close, or else stop suddenly (like music player) without closing.
Also using CWM to "fix permissions" (not quite sure what this means).
We'll see what my results are after this.
I'd like to get this stock ROM working well if at all possible - if for no other reason than the Exchange peak/off peak email sync settings that don't seem to exist in other ICS ROMs.
Click to expand...
Click to collapse
using nodata is you're problem, all of the issues you've described could be caused by using nodata, this is why it is advised in almost every roms dev thread to do a full wipe, not no data... you may be able to get away with it without any serious bugs upgrading the same rom one revision but not going from gb to ics. you need to do a full wipe and fresh flash, legacy gb app framework is causing these issues, not ics
kingsway8605 said:
I wish a mod would sticky a battery life complaint thread and close all others. Every other thread is an ics battery life complaint.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
SERIOUSLY! i dont get why people come to xda to whine about the OTA, XDA is the place you come not to run stock... And half the threads that arnt about battery life/"bugs" where the poster provides only basic anecdotal "evidence" and no technical data whatsoever on FF18 are gripes about sprint and sprint related issues... have people never heard of the sprintusers forum, THATS where those complaints belong, not here
cp320703 said:
using nodata is you're problem, all of the issues you've described could be caused by using nodata, this is why it is advised in almost every roms dev thread to do a full wipe, not no data... you may be able to get away with it without any serious bugs upgrading the same rom one revision but not going from gb to ics. you need to do a full wipe and fresh flash, legacy gb app framework is causing these issues, not ics
Click to expand...
Click to collapse
Thanks for this part - however...
The very advantage of going the OTA (or at least stock - I didn't OTA it) stock route is to not clear the phone.
Samsung/Sprint spent how many months developing this, to provide an update that's supposed to be clean for existing, non-technical, non-rooted, mom & pop users. I wanted to go this route simply as the "cleanest" option. And I've got lots set up on my phone and very little time around now - I'd prefer not to lose it if I can avoid it. As much as you try to back up, and remember, and all that, every time you wipe you forget something...
It's a little bit like being a Jeep owner, and saying "you know, everyone could get away with driving a Jeep".
Sure... they could... but they wouldn't all enjoy it, and it really wouldn't fit everyone's use case.
Usually, advise like this really just reflects a lack of vision: "I can't imagine anyone who uses their phone different than ME".
cp320703 said:
SERIOUSLY! i dont get why people come to xda to whine about the OTA, XDA is the place you come not to run stock... And half the threads that arnt about battery life/"bugs" where the poster provides only basic anecdotal "evidence" and no technical data whatsoever on FF18 are gripes about sprint and sprint related issues... have people never heard of the sprintusers forum, THATS where those complaints belong, not here
Click to expand...
Click to collapse
Does this look like whining, or seeking a solution? Hey, look - the original post!
geolemon said:
...This is frustrating to me - I use this phone for work, I came off an AOKP ROM to get back on a stock ROM, for two things:
1) stock stability and battery life.
2) the Exchange account options for sync scheduling (on peak/off peak schedules for sync) that only seem to be in the stock ROM.
Accordingly, I'd like to see this ROM working. Any thoughts on these?
Anyone else observing these symptoms, relative to the stock GB rom?
Click to expand...
Click to collapse
Again - seems more and more like you are a child, not only lacking maturity, but injecting your own prejudices rather than reading.
I'm seeking solutions.
And XDA is the place for options. Solutions are a subset of options.
Grow up.
I wasn't referencing you as whining at all, however this thread belongs in the Official OTA thread, not on its own, that's what the commenter prior to me and I were both refrencing- the constant new threads about the same 3 or 4 issues with the OTA when there is already a thread for it... that said you said you're seeking solutions, I offered you one that will work, I'm sorry that it displeases you, but doing a full wipe and a clean install will solve pretty much every issue you have, so backup your apps, and text messages if you want those as well, it takes less than 5 minutes in titanium backup and SMS backup, and do a clean flash or Odin (if flashing make sure you are on a safe kernel). That will fix your problems, its silly to keep asking for solutions when the best and most likely to be successful one has already been proffered.... or should you still for some reason not want to do this just unroot and take it to a sprint store, they'll do a factory reset, that'll fix all of the issues you're having. Save the time and effort and just do it yourself, no one is going to post any magic advice that'll make it all OK with nothing unchanged
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
I wasn't referencing you as whining at all, however this thread belongs in the Official OTA thread, not on its own, that's what the commenter prior to me and I were both refrencing- the constant new threads about the same 3 or 4 issues with the OTA when there is already a thread for it... that said you said you're seeking solutions, I offered you one that will work, I'm sorry that it displeases you, but doing a full wipe and a clean install will solve pretty much every issue you have, so backup your apps, and text messages if you want those as well, it takes less than 5 minutes in titanium backup and SMS backup, and do a clean flash or Odin (if flashing make sure you are on a safe kernel). That will fix your problems, its silly to keep asking for solutions when the best and most likely to be successful one has already been proffered.... or should you still for some reason not want to do this just unroot and take it to a sprint store, they'll do a factory reset, that'll fix all of the issues you're having. Save the time and effort and just do it yourself, no one is going to post any magic advice that'll make it all OK with nothing unchanged
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I'll try it... just want to make that the last resort.
Wouldn't you consider it to be equivalent to just wiping/factory reset via CWM?
geolemon said:
I'll try it... just want to make that the last resort.
Wouldn't you consider it to be equivalent to just wiping/factory reset via CWM?
Click to expand...
Click to collapse
yup wiping in cwm will do it, again be sure you're on a safe recovery eg. agats or chris41's... things like the force closes of music player and the malfunctioning of swipe, camera, etc, are due to coming from gb without a full wipe... i do realize its a PITA if you wanted to keep it simple, but it is what it is you know... insofar as battery I've never had a problem running ff18 based roms such as blu kuban or goodness, I've never run bone stock myself but if you continue to have issues there are tweaks, such as kobridges and phakers scrips that'll help out a lot, in addition to disabling unnecessary syncs, etc... however after giving it a few days to settle I've not had any problem getting a full day of moderate use out of ff18 based roms...
just to add a little more, fixing permissions will help a little with force closes... if you are unfamiliar with the UNIX permission system you can find some good info here ( http://www.perlfect.com/articles/chmod.shtml ), however it would still probably be best to to a wipe as it most likely won't fix all the bugaboo's you have from keeping your gb /data partition... despite what the horrid touchwiz interface would have you believe ICS is a huge step forward from GB, and that old app data can and will cause problems... lastly sorry if i came off a bit gruff, as I'm sure you've picked up I'm somewhat tired of seeing threads about the OTA, however to your credit you did post tons of concise, detailed info and were open to suggestions, I've seen similar thread where the OP just posts something akin to "ICS data sux, wtfff????" and when recognized devs tell them what they need to do they start to argue, which makes no sense to me... I was most likely taking my frustration at those threads and their apposition to the purpose of XDA out on you, for that I apologize, good luck with it and should you need further help let me know, I'd be glad to assist or at least point you in the direction of information that may help
This thread seems to have gone off the rails a bit... All the answers you seek are in development op. It requires reading though... There are roms and explanations for every problem you listed. If you say no they're not... Then you have not taken the time to read... Simple as that... I am a developer here and no one taught me anything. I READ AND LEARNED IT. i have a family and a life and the whole bag... So there are no exscuses. I challenge you to take the time to read and learn and give back. Maybe YOU can find the answera to your questions and post the answers here so you can help someone else who will post this and that doesnt work (but does, they just didnt read and learn how to fix it). Because as soon as you post it someone else will have the same complaints and questions and will be to lazy to search...
ok so i finally bought an S3. i updated the software today from tmobile. but the update gave me 2 problems:
1 - the dialing rules dont work. for example, i call a chat line. after the number is dialed, the dialing rule dials a pause and 3 numbers automatically. this works. but when i try to dial additional keys manually, the dialpad doesnt work. this never happened in the previous version. how can i fix this?
2 - the battery drains like craxy. how can i revert back to the previous version?
by the way, is this the jelly bean update from tmobile for the S3?
It might help people help you to know what update this was ... ??
Look in your phone settings and see what you're running ?
Pennycake said:
It might help people help you to know what update this was ... ??
Look in your phone settings and see what you're running ?
Click to expand...
Click to collapse
directly from Tmo it only can be Jelly Bean. at the moment.
issues after updates on android is familiar. Factory reset your phone is the quickest way to fix it.
Turn off Google Now. My phone's battery goes back to normal now.
They weren't sure if it was JB, so I was a bit worried for them.
I wanted to be able to use Google Now's location features, and having set it to mobile data only (no GPS), it hasn't put a significant drain on the battery and I'm pleased with the results.
@OP, I was having horrible battery drain after the update, myself, but after messing with the settings and waiting a few days it's back to normal. Turn off Google Now if you don't want it and give it a few days - I don't know the technology behind it, but giving it a few days did seem to do the trick like others had said in the big battery life thread.
Pennycake said:
It might help people help you to know what update this was ... ??
Look in your phone settings and see what you're running ?
Click to expand...
Click to collapse
the new update 1s: 4.1.1. i liked my previous firmware version much better.
rookiegenius said:
Factory reset your phone is the quickest way to fix it.
Turn off Google Now. My phone's battery goes back to normal now.
Click to expand...
Click to collapse
but if i factory reset my phone, i lose all my settings and apps.. and where exaclty do i turn off Google Now? i cant find it
Pennycake said:
I wanted to be able to use Google Now's location features, and having set it to mobile data only (no GPS), it hasn't put a significant drain on the battery and I'm pleased with the results.
@OP, I was having horrible battery drain after the update, myself, but after messing with the settings and waiting a few days it's back to normal. Turn off Google Now if you don't want it and give it a few days - I don't know the technology behind it, but giving it a few days did seem to do the trick like others had said in the big battery life thread.
Click to expand...
Click to collapse
hi pennycake. but where do i find Google Now? i dont see it anywhere in the settings.
also, i found this link about how to revert back to a previous firumware.. please let me know what you think:
androidromupdate.com/2012/08/25/restore-back-t-mobile-samsung-galaxy-s3-sgh-t999-back-to-original-ics-4-0-4-t999uvalh2-stock-firmware/
If you go in the app drawer and find the "Google" icon, that will take you to it. You can also change the location preferences in "settings".
Personally, I wouldn't bother reverting unless there's something other than battery life that's really bothering you. Jelly Bean didn't have much in the way of big cosmetic changes and by turning off the location tracking, battery life should be the same as it was before. I don't think the average user will notice much of a difference.
See if the factory reset fixes the glitches you're having - when flashing a ROM (like the older firmware), you would want to do that anyway - it's possible to brick your phone flashing ROMs - not to scare you, but you might end up starting from a wipe anyway, if that doesn't go as planned.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
If you go in the app drawer and find the "Google" icon, that will take you to it. You can also change the location preferences in "settings".
Personally, I wouldn't bother reverting unless there's something other than battery life that's really bothering you. Jelly Bean didn't have much in the way of big cosmetic changes and by turning off the location tracking, battery life should be the same as it was before. I don't think the average user will notice much of a difference.
See if the factory reset fixes the glitches you're having - when flashing a ROM (like the older firmware), you would want to do that anyway - it's possible to brick your phone flashing ROMs - not to scare you, but you might end up starting from a wipe anyway, if that doesn't go as planned.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
hi pennycake. just to let you know, theres nothing worse that bothers someone than poor batt life. and other than that issue i got, i'm also having the dialing rules issue which doesnt let me dial extra digits manually after the dialing rule completes. this is very annoying.
i understand the risk in reverting back to the previous firmware. its just that if factory resetting doesnt work, i got to go back to the last fw. what i dont understand is why samsung or tmo would allow an update that disabled needed features.. and above all, mess up the batt life?
Trust me, I was pretty frustrated when I was losing 3% an hour on standby - and in use, I was just watching the battery go down another percent every time I glanced at it!
It's such a change from what many
People are used to that it ought to be better explained.
As for the dialer issues, I'm not sure if that is an issue with jelly Bean itself or not.
With every phone being a little different, sometimes things they don't expect can go wrong.
Hopefully you will get it sorted and be back to enjoying your phone soon!
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
Trust me, I was pretty frustrated when I was losing 3% an hour on standby - and in use, I was just watching the battery go down another percent every time I glanced at it!
It's such a change from what many
People are used to that it ought to be better explained.
As for the dialer issues, I'm not sure if that is an issue with jelly Bean itself or not.
With every phone being a little different, sometimes things they don't expect can go wrong.
Hopefully you will get it sorted and be back to enjoying your phone soon!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
yeah thanks penny.. like i said, if resetting doesnt work, i'll go back to ICS fw. thanks.
Alright, so my girlfriend's Samsung Galaxy S II started to go through these weird partial reboots several weeks ago (maybe even months). The phone would randomly go black, play the stupid shutdown/startup (dont remember which) jingle...then just simply be at the lock screen with a crossed out circle where the signal bars would be (for just a couple of seconds). When this happened, I used to just tell her to shutdown the phone, take out the battery, and let it sit for about 30 seconds, then put everything back together and start it back up. This seemed to work, which made me think it might have just been a software or at worst a memory issue of some kind.
This issue was always intermittent, but now, no matter what I do, it just keeps looping this "restarting" problem. I can't access any internal memory space from my computer because in the time it takes to connect, it just "reboots" again. I made a logcat of the phone up until the "reboot", and in doing so noticed that when I would browse the phone via adb shell, I saw no mount for the sd card...which then lead me to believe maybe it was an issue with that. I checked the sd card for corruption (and prior to even using it, checked that all blocks were read/writable (legit)), but that led nowhere.
Anyways, not having any idea where to go next, nor where to begin or what to look for in the 5000+ lined logcat, I turn to xda with hopes of getting some sort of help. Thanks in advance for any I get!
EDIT: Oops, some other important notes I didn't mention (other than in title); this is running stock firmware, only OTA. I tried once to upgrade her to ICS via Kies, but the upgrade would never complete. She also refused to let me root her phone...so unless there is a stock recovery mode, her phone has none...
bump, as its been a week and no responses. If anyone has any ideas or can figure out whats wrong from the logcat, please help.
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Sent from my SGH-T989 using Tapatalk
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
For starters, thanks everyone for the responses! After this long, its really great to see so many in one day!
richardlibeau said:
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Click to expand...
Click to collapse
Thats what I thought, because it seemed to get exceptionally hot before "rebooting"...at first...then I was noticing it "rebooting" when clearly cold. If it is indeed overheating like I had thought in the very beginning, is there anything I can do about it? What does it use for heat conductivity and displacement? And for that matter, I would think if it was overheating though, it would actually reboot, not the half-ass semi-reboot its been doing...
And what is wakelock exactly that it would cause an issue? Only apps I see using it are WootWatcher, KeyguardViewMediator and PowerManagerService.
krazierokz said:
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Click to expand...
Click to collapse
I would use odin...but the phone doesn't stay on long enough to do much of anything before "rebooting". Also, she is already using stock firmware + OTA updates. And her contacts are not what I am worried about, its her photos and such. This is the very reason why I hate internal memory for phones...
And I'm pretty sure its not a sticky power button, I had seen that being a common issue when researching before posting. And again, if I have not been clear, its not exactly "rebooting", just semi-rebooting; phone starts up, crap starts running, a min or 2 later, phone acts like its restarting (plays sound and all), then just comes back to the lock screen immediately...I can't really describe it much more than that.
And no, I'm not familiar with "download mode"
bzlik88 said:
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Click to expand...
Click to collapse
Ya, like I said in the reply above this, I don't think its the sticky power button problem...but I could always be wrong. I only didn't mention over heating because I felt I did a good job of ruling it out.
DeliciousLimeJuice said:
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
Click to expand...
Click to collapse
Its running GB atm, never updated to ICS via Kies...
I wish I could help you further but i can say one thing, the rebooting that your describing is called a "hot reboot". I know what ur talking about and others will too if u use that term. Good luck.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
My mother has a epic 4g,and it has been giving her problems. I am hoping maybe someone here can help me make her phone better. Here I go with all her problems.
1.drop calls frequently
2. Service drops - 3g & voice
3.has trouble picking up signals in places. Where other phones have no problem
4.takes it forever to boot up.
5.freezes when talking to someone & incoming calls. Have to take the battery out to get it to
6.hardly any battery life to it. Battery is the one it came with I believe so it is old.
I am willing to root and give it a better rom, kernal, mods to make it a better phone for her. All she does is phone calls, fb, and some internet browsing. If anyone have any recommendations I am all ears. She doesn't feel like upgrading her phone cause she doesn't have the extra cash for one.
Stability first for mothers. CM7.2 is your best friend. Still available on get.cm.
Sent from Google Nexus 4 @ CM10.2
Would that fix all her problems? I know it probably won't fix the battery to much since she probably should buy a new one. Is there a stable release of android 4.1.2 as stable as the cm 7.2? But if 7.2 is the most stable and bluetooth, txt, internet, voice is more stable
and working on 7.2, I will go with that one. I just want to make her phone work to the best of its ability for her. Watching qbking77 vids on rooting it. I was hoping to find a review vid on cm but he only has it for epic 4g touch.
We have an old device, so if the battery is not holding a long enough charge & it's the original that came with the phone--you should purchase another on eBay/Amazon/etc. The SGS2 battery fits snug in our phone without an extended back.
What release version is she on? (FC09?)
What modem is she on? (FC09?)
Do other Sprint devices have better signal in the same area the Epic is being used?
You could just be in a crap or nearly dead coverage area. It happens when you're on the edge of a tower's coverage radius with no connecting tower to jump to.
It also helps to find out which apps are consuming the most battery. Install this app to find out which apps are consuming battery: http://forum.xda-developers.com/showthread.php?t=1179809
Focus on partial wakelocks and other.
Though, since you're saying signal is a problem, I bet her Time without Signal (TWS) % is pretty high. That would destroy a battery's charge. After a day's charge/use, open Settings > Battery > Cell Standby. Look at the the bottom % "Time without a signal". If above 3%, then the phone's loss of signal and constant searching for one is killing the battery fast. The only 3 solutions are:
1.) Call customer service and complain about very poor signal. With enough complaining, they should send you a free AirWav. You'd be responsible for taxes only.
2.) Use Airplane mode in crap coverage areas to conserve battery. (But voice is not usable in this option. Can still use Wifi for Google Voice and whatnot.)
3.) Drop Sprint for a carrier with better coverage in your area. Can probably get out of any contract, if by strange chance she's still on one for this phone, by complaining to customer service enough.
Alright I'll try going into details.
Tsukiyohikage said:
1.drop calls frequently
2. Service drops - 3g & voice
3.has trouble picking up signals in places. Where other phones have no problem
4.takes it forever to boot up.
5.freezes when talking to someone & incoming calls. Have to take the battery out to get it to
6.hardly any battery life to it. Battery is the one it came with I believe so it is old.
Click to expand...
Click to collapse
Question 1, 2 and 5 can't be answered, I don't use Epic for cellular network other than mobile data. But for question 3, coverage is fine here and both CM7.2 and CM10 (4.1.2) gets strong, equal signals compared to local GS3 handsets on the same carrier. Keep in mind that I'm in China and Epic's flashed to China Telecom, so things could be kinda different for ya. And don't forget to flash the latest radio (FC09 or FC19).
4. CM7.2, when properly set up, boots as fast as my new Nexus 4! CM10 takes ~20sec longer, but they all fall within a minute for me. Much faster than Touchwiz-based ROMs.
6. Again, you'll get UNBELIEVABLE battery life with Gingerbread - may need a new battery though. Once I charged my Epic, left it there with CM7, turned off airplane mode (usually on to save battery) and somehow left it in my drawer. ~10days after, I dumped my drawer for things when Epic slips out and tells me it still has 11% battery left and yes, it has signal all this time. Which means ~12days of standby time! WTF enough speaking of battery
Tsukiyohikage said:
Is there a stable release of android 4.1.2 as stable as the cm 7.2? But if 7.2 is the most stable and bluetooth, txt, internet, voice is more stable
and working on 7.2, I will go with that one.
Click to expand...
Click to collapse
CM10 is stable in everyone's eyes. The only reason I recommend CM7.2 first is that it has nearly 1/2 the battery drain of CM10 (for me). If you miss the appearance and some cutting-edge features, CM10 would still be a nice choice. Don't try 10.1 (and any 4.2.x ROMs) though, as BT is borked more or less.
You could always wait a bit more and listen to what other members have to say. I'm Chinese and may not give practical advices based on US network environment
Sent from Google Nexus 4 @ CM10.2
Thanks for all the advice guys. I am looking at a new battery for her. Been looking at the battery thread on here to find her the best one. I like 4.1.2 but she hasn't seen it, all she knows is what her phone looks like now.
And to answer the questions
What release version is she on? (FC09?) - not sure as of the moment, I want to say yes. I'm at work and don't he her phone on me.
What modem is she on? (FC09?)- not sure as of the moment, I want to say yes. I'm at work and don't he her phone on me.
Do other Sprint devices have better signal in the same area the Epic is being used?
Yes other Sprint phones get better signal in the same area where she has trouble.
Example :we were at a hospital and my sister's evo shift, my old evo 4g had no problems at all. But her's was having trouble getting service.
Tsukiyohikage said:
Do other Sprint devices have better signal in the same area the Epic is being used?
Yes other Sprint phones get better signal in the same area where she has trouble.
Example :we were at a hospital and my sister's evo shift, my old evo 4g had no problems at all. But her's was having trouble getting service.
Click to expand...
Click to collapse
Don't use a hospital as your example. Hospital's are notorious for having horrible cell service due to the concrete walls and other interference. Use the location that she is in most for your baseline location, and if that is a hospital--then she will likely have poor service in such a building complex.
nikon120 said:
Don't use a hospital as your example. Hospital's are notorious for having horrible cell service due to the oncrete walls and other interference. Use the location that she is in most for your baseline location, and if that is a hospital--then she will likely have poor service in such a building complex.
Click to expand...
Click to collapse
I just called her and asked her where else she has trouble with service. She said mostly everywhere. I know our area is good in 3g and voice, no dead zones shown on coverage map. I know our 3g in our area is a little out of whack do to updating the towers. But this has been problem before the tower updates. And I asked her to look at phone info and she said it says gingerbread fco9.
I am looking at buying a Onite 1900mAh Li-ion Battery for her aswell. Unless you have a betterssuggestion.
My wife complains about her phone and I have tried to convince her to root it. Unfortunately, she's heard me complain about mine through rooted stock ginerbread all the way to CM10.1.
I never did CM7, but CM10.1 RC5 has been the best rom for me. Battery life is great. Great control. I don't have any issues with it, including bluetooth. it acts weird. like it connects and then when I make a call it says "disconnected" but I hear the phone ring and it functions normally. It just says "disconnected" in my headset. Otherwise, it works fine.
It's tough for a guy who screws with his phone all the time, like me, to give good counsel to someone like your mom or my wife about having a hacked phone. I honestly don't think you'd have as much trouble if you rooted it that the bone stock sprint gingerbread load. that totally sucked for me. GPS didn't work. Battery life sucked. And it had all those cutesy sprint apps like Nascar and sprint tv.
The good thing about rooting it, i think, is that once you do it the first time, it's really easy to load different ROMs in case you want to try some other ones. I downloaded the dominator one, but I have been so happy with cm10.1 rc5 that I am sticking. This is the best my phone has ever been.
Thanks for all the feedback guys. I will have to sit down with and explain all this stuff and let her decide on what she wants to do. I've been working doubles at work lately so haven't been able to talk to her about stuff.
She has told me to root her phone. I see you can get twrp recovery for this phone. So my new question is since I have been having trouble finding the answer is how do I flash twrp in? Do I flash it through cwm, odin, goomanger? I was going to follow the steps to root her phone in qbking video. But his way only shows putting cwm in.
Tsukiyohikage said:
I was going to follow the steps to root her phone in qbking video. But his way only shows putting cwm in.
Click to expand...
Click to collapse
I had rooted a few years ago and found the easiest procedure to follow here:
http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/
I rooted gingerbread first and then did other roms. But I think the Cyanogenmod web pages have a straight forward process too., You difinitely have to have the recovery console CWM or similar loaded to start which requires Odin as far as I know. So that is going to be your first step. Those links are in that android central forum. At least they were at one time.
Tsukiyohikage said:
She has told me to root her phone. I see you can get twrp recovery for this phone. So my new question is since I have been having trouble finding the answer is how do I flash twrp in? Do I flash it through cwm, odin, goomanger? I was going to follow the steps to root her phone in qbking video. But his way only shows putting cwm in.
Click to expand...
Click to collapse
TWRP: Flashes through CWM; OR you can pull the recovery.bin file from the zip file and flash that in Odin.
Root:
Power down device
Open keyboard, press and hold both the 1 key and power button. This places the phone into download mode.
Plug the device into your computer, and most likely drivers will install. Allow that to finish before proceeding.
Within Odin, wait until you see COM and a port number appear. That means your phone is recognized.
Next, uncheck all boxes on the left side, including auto-reboot.
Place the victory_8G_100528.pit file in the PIT box. Place CWM v5.0.2.7 .bin/.tar/.md5 file in the PDA box.
Click start and will complete relatively quickly.
Disconnect the phone from USB and pull the battery out.
Replace battery.
Press and hold Vol down, Camera and Power buttons until the capacitative lights light up, then release. This will place you in recovery mode.
From there you will boot into CWM, where you can flash whatever you want (custom rom or a compatible kernel for FC09 & SuperSU) off the SD card. So place those files prior to doing all the above.
Keep in mind, that if you want to remain on stock FC09, but rooted, you will need to flash a custom kernel. The stock kernel will replace CWM with stock recovery every time. That is why in the list above you must disable auto-reboot and battery pull.
All files are in my devhost, in my signature. If not, then they expired and I can reupload them if notified.
nikon120 said:
TWRP: Flashes through CWM; OR you can pull the recovery.bin file from the zip file and flash that in Odin.
Root:
Power down device
Open keyboard, press and hold both the 1 key and power button. This places the phone into download mode.
Plug the device into your computer, and most likely drivers will install. Allow that to finish before proceeding.
Within Odin, wait until you see COM and a port number appear. That means your phone is recognized.
Next, uncheck all boxes on the left side, including auto-reboot.
Place the victory_8G_100528.pit file in the PIT box. Place CWM v5.0.2.7 bin or .md5 file in the PDA box.
Click start and will complete relatively quickly.
Disconnect the phone from USB and pull the battery out.
Replace battery.
Press and hold Vol down, Camera and Power buttons until the capacitative lights light up, then release.
From there you will boot into CWM, where you can flash whatever you want (custom rom or SuperSU).
Keep in mind, that if you want to remain on stock FC09, but rooted, you will need to flash a custom kernel. The stock kernel will replace CWM with stock recovery every time. That is why in the list above you must disable auto-reboot and battery pull.
All files are in my devhost, in my signature. If not, then they expired and I can reupload them if notified.
Click to expand...
Click to collapse
Thanks for the for the walk through. I plan on doing this tonight for her and I will let you guys know if I was successful or not. Lol
I got cwm, falshed FC09 BML Deodexed Prerooted Stock ROM. As of right now the screen is black and the 4 buttons are lit up.
Battery pull and try to get back in recovery. If you can't, then Odin CWM again. If that still doesn't fix it, then you should reflash stock FC09 again and go through the steps above again.
Bad flashes happen. It could also be a bad download of the ROM.
Sent from my Nexus 7 using Tapatalk 2