Vibration logging app? - T-Mobile Samsung Galaxy S 4

Does anyone know of a vibration logger? I've been getting random vibrations for about the past two weeks on my GS4, and I want to know what is causing them. On a GPE rom, and have been on the same one since January. The issue just started, and I have not had it before. No settings have been changed recently. Just want to know which app or process is causing it so I can deal with it, since it (may) also be causing battery drain, although that could just be me being paranoid.

A logcat would probably be sufficient if you could find someone willing to take a look at it for you. I would suggest posting in the Better Battery Stats thread or the Insanely Better Battery Life thread about your issue. Those posters are extremely helpful and can help pin down your issue if you ask nicely.
I had a similar issue recently. Do you use chenxialong's dualboot by any chance?

Hey Guy, did you ever find a solution? I want the exact same thing.

It was probably the rom causing it, and most likely resolved by re-flashin rom or switching to a more stable rom.
Pp.

PanchoPlanet said:
It was probably the rom causing it, and most likely resolved by re-flashin rom or switching to a more stable rom.
Pp.
Click to expand...
Click to collapse
Noted, thanks, but mine is stock. (it'll probably be stock till the end of time. S4 zoom)
I guess there are no apps for this. Shame :/

If you're experiencing random vibrations you may have an issue with your firmware or a rogue app.
Eliminate some apps and see if issue corrects itself or flash stock firmware.
I also run stock /rooted /no bloat and everything works the way it's supposed to.
Pp.

Related

[Q] Glide freezing up

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.

Battery and stability issues with new ICS

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...

[Q] SGS3 screen flashes off and on randomly while in use

This never used to happen but in the last week has.
While using it, whether I'm in GoSMS Pro, or Chrome or even in the homescreen the screen will fade to black then back one to three times. It almost feels like proximity detection but there's absolutely no obstruction nor am I in a call.
Running 4.0.4 stock unrooted, latest update from Rogers.
Has anyone had this? Getting a bit worried!
Screen blacking out randomly
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
dropzone01 said:
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
Click to expand...
Click to collapse
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Victorminator said:
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Click to expand...
Click to collapse
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Temporary solution found
Victorminator said:
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Click to expand...
Click to collapse
I think I've solved it, but this may not be a solution for most people experiencing this (my friend also had this issue). In my case removing the game Modern War solved it.
I remember that after I installed it, the system started doing these flashes. It now has been behaving ok for 4 days since uninstalling it.
I don't think the game itself is the cause, but rather there could be some background task from it (it does occasionally push game event updates as notifications) that doesn't like the 4.0.4 update. In this case I can't quite identify what nor do I know how to diagnose it.
Just thought I'd update people in case they still have this issue. It may be one of your apps, essentially. It sucks and it shouldn't happen, but alas unless we test with a new stock OS update, we won't have much to eliminate it without removing the offending app.

[Q] All sound randomly dropping in/out

For the longest time I was on stock rooted EK02. I recently took the plunge and wiped all and installed CM10, which I love. The only problem I've had is that *all* sound suddenly decides to just go away whenever it wants to (ring/notif tones, touch clicks, app sounds, everything except in-call audio). It might last 5 minutes, or it might last an hour, but it always comes back on its own, and a reboot does not fix it. I can't seem to trigger the problem with a certain app or a certain action, but for example, I will be sitting here playing Angry Birds Star Wars, and the sound will just drop out completely. A few levels later, it comes back on its own. I put the phone down, go do something else, and the entire phone has muted itself again. Frustrating...
I'm on CM10 beta2 nightly 20121108
Kernel version says 3.0.15-CM-g8e7ed92, which seems appropriate since it references CM and this is the first CM I've ever had on the phone. Should I try other kernels though? AFAIK, no one else has mentioned this particular audio problem in the CM10 discussion thread. At least I don't think this is related to the "low volume in some apps" issue.
HOWEVER, something interesting, the baseband/radio version says EK02. I guess I should update that to get better comm, but it couldn't be causing an intermittent muting issue, right? I guess I assumed incorrectly that a ROM installed after a wipe would have to include its own modem. Argh.
This is frustrating, as I said. Thanks for any help.
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
I am not exceedingly familiar with cm10 but I would bet it is not the modem causing that issue. I would be inclined to think you have intentionally and / or accidentally changed the "quiet hours" or setup some form of silent profile. Otherwise it was perhaps a bad flash, you did not wipe CLEANLY (IE. calkulins format all or odin a full wipe/restore rim first) or maybe not install with what many revs believe to be a CWM safe kernel???
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
also do you have anything (pc or stereo) connected to Bluetooth with the phone nearby?
trmitche2 said:
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
Click to expand...
Click to collapse
Nobody knows the answer to your questions. This is not a common problem and as mentioned above the modem has nothing to do with it. My only suggestion would be to flash a stock release one click, not a leak, and go from there.
Agree with above and mainly because I borked my build... it was perfect and then I tried a gps fix flash. Can confirm now that wipe in CWM and calks format all does not do crap for aosp, jb, or the like. So long story short, yeah you gotta one click or my guess is best served to clean slate with a stock ROM and in consequently factory wipe and just stay there.....
Wow thanks for the replies guys! I was really getting discouraged there for a bit.
I don't think it's a quiet hours setting, because all sound is cutting in and out *every 5-10 minutes*,
I will use Calk's wipe and start from scratch as suggested.
Although unrelated, surely EK02 is not a recommended modem for CM10, right? I guess I made a naive assumption that a full wipe followed by CM10 install would replace my old modem. I'm just curious what kind of problems might be caused by using such an old modem, even though I know sound is not one of them.
Can anyone recommend a modem for this ROM from personal experience? I understand from the main beta2 thread that the FK modems break 3G...
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
someguyatx said:
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
Click to expand...
Click to collapse
Yes. Do this. Then. Format all is still a good idea if you choose to revert to a GB ROM like el29 and progress.
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
trmitche2 said:
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
Click to expand...
Click to collapse
None, modems are interchangeable between builds with the exception of the fk-- and newer modems, they only work with Touchwiz based JB roms. If your modem is performing well speed and call quality wise then there's no need to change. However you could always test other modems to see if you get any improvement in your location. If you choose to change modems you should be on a touchwiz rom so you can update prl and profile after the modem flash. Modems are a YMMV item each one interacts with different devices and locations differently so to find the best modem for you you just need to flash and test them out if you so choose
Sent from my hand to your eyes!
Samsung: Intercept, Galaxy S2, Galaxy S3, Galaxy Note 2, Nexus10
HTC: EVO4g, EVO 3d
LG: Optimus G, Nexus 4
Asus: Nexus7
Motorola: Photon
Amazon: Kindle Fire, Kindle Fire HD
We are legion, for we are many!
Thanks KoN! Extremely helpful post, as always. All other replies in this thread have been thanked as well. I learned a lot.
Still wish I knew how FB could make my sound cut in and out every few minutes, but if no one else has seen that issue, it must've been a quirk, so I imagine I'll never know. Moving on....

[Q] Random reboots and lock ups (memory leak?)

Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app

Categories

Resources