Related
My girlfriend's HW003 Nova EVO is in a state of random reboot. I have run out of ideas.
It is not OS dependent, meaning I have gone through 3 different ROMS including stock rooted.
There are 6 log files below. They are logcat files right before the phone kills the connection.
Knowing that the ROM is not the cause, I am down to Radio, WIMAX, GPS, WIFI, or CPU/MoBo.
I executed the gpsclrx command and it had no effect on the random reboots.
Is anyone else having the same issue? Have you exchanged your phone at a Sprint location? What have you done?
http://www.andrewdefilippis.com/uploads/Documents/Restart_1.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_2.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_3.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_4.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_5.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_6.txt
Sent from my HTC EVO via XDA App
003 / Nova
I have some random reboots as well, thought it was related to temp but after a while that seems to not be the case. Happens on every ROM and seems to happen 9/10 times when browsing. Stock Browser / Dolphin HD. Reason I thought it was a temp thing was I started noticing a light spot on the screen, evidently above the processor, and so I figured something had to be happening with it all.
Have been meaning to start calling around about it and see if it's something Sprint can replace or not. Am more than prepared to pay the deductible, but I haven't really made steps to get to the bottom of it.
It's strange because when I think I realize what is doing it, it ends up not really seeming to be the case. It all started happening when I had a bad wipe / flash (clockwork) and it started happening then. Lost my RSA Certs (not a huge thing, obviously something I'll need to address at some point but currently using CM6 so I'm not really "missing it." But that's when it all started happening. So I guess in that regard, the WiMax shouldn't necessarily be an issue ... or so I would think. Happens when on WiFi and off, happens whether GPS has even been turned on at any point or not so I figured it had to be some CPU issue but not necessarily due to heat.
Know this probably doesn't help, but I thought I'd post.
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Exchange the phone?
Sent from my PC36100 using XDA App
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
conqu1stador said:
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
Click to expand...
Click to collapse
If you have setcpu installed, I need you to go to the info tab, scroll down and tell me what value is next to memtotal. It should be 425000.
Let me know what yours is.
Sent from my HTC EVO via XDA App
omegasun18 said:
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Click to expand...
Click to collapse
This issue is ROM/APP independent. There is no connection to 3rd party software or os.
Sent from my HTC EVO via XDA App
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
lgevo said:
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
Click to expand...
Click to collapse
Gah, just saw this sorry for double post. Issues all starred after bad flash after bad wipe with clockwork. Using amon now, 1.7. Have yet to update to 1.8.
sent from my SUPASONIC
conqu1stador said:
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
Click to expand...
Click to collapse
The reason why I was asking you to check the info tab for the memtotal value, is because on my phone, currently I am not having a problem and the value is 425000kB , but on my girlfriend's phone, it registers only 424840kB.
Sent from my HTC EVO via XDA App
Alright, will look for the one on these boards.
Hate to even go here, but I really never used a logcat before; but my phone just rebooted and I went immediately into the logcat and just like when I launched it at first there is just a wealth of information. I see it says ;
D/alogcat ( 521): stopping ...
D/alogcat ( 521): resumed
Might sound dumb, but am I to assume that's the point the log stopped and began again, due to the reboot? Would think it is .... on to that setcpu I guess.
edit: seeing that stopping and resuming in multiple spaces, guess that's not it. =/
setCPU - memtotal; 424828 kB
conqu1stador said:
setCPU - memtotal; 424828 kB
Click to expand...
Click to collapse
Alright. I need more people with HW003 Nova EVOs to check the same, and say if they are having reboots. This could be corrupted or bad memory.
Sent from my HTC EVO via XDA App
i have hw 02 but my memtotal is 424832... does that matter?
????
i have hw 02 but my memtotal is 424832... does that matter?
I think this may be a HARDWARE issue...
Hello xda folks,
Long time reader, first time posting...
I'll try and condense this down, everytime I try to post something xda says I'm not logged in, so I'm keeping it short out of re-writing frustration.
I'm HW003, I lack setcpu, so I can't really check my memtotal, but I believe that in short the flash mem/nand memory may be getting damaged or corrupted by flashaholics like myself. I'm curious to see in any non-root users have experienced the completely random reboots like some of us here.
Let me be clear about one thing, I'm describing random rebooting, not consistent bootloops, at least they weren't at first.
Initially, I thought this problem was a byproduct of OC'ing, or overheating the unit, but I have flashed every combination of rom, kernel, OC/stock, hboot ver, etc, virtually anything I have some control over, and the phone still reboots. Ive even rolled back to stock unrooted, and tried bone stock 2.2 but the phone keeps throwing a fit.
Everything on this phone hardware wise screams "I was manufactured on the cheap, and put out to stores on the quick", so it stands to reason there is some kind of failure taking place.
I'm no expert, but I've flashed this thing A LOT. Probably around 100 times.
It also seems to be getting worse, as it often sticks in bootloops now, not just random reboots. Causing me to have to flash it on an even more arbitrary basis!
Next step for me, is rolling back to stock 2.2{Again}, and sending this bad boy back to where it came from, and wait for my POS replacement and its new set of shenanigans. I will root the new one once, pick one rom, and flash it once...
It will be difficult, but I will be attending Flashaholics Anonymous.
We can do this together.
Anyone have a more logical answer?
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
bbecker42 said:
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
Click to expand...
Click to collapse
The force closing is probably due to not having Journaling on.
I believe in the SRF 1.2 OP, there is a JournalingOn.zip, flash that (no wipes) and that should stop the force closing.
If it still is unstable for you, I recommend just reflashing the ROM.
Hope this helps.
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
nikon120 said:
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
Click to expand...
Click to collapse
Exactly right
Sent from my SPH-D700 using XDA Premium App
I had friend who had the same issue. He went back to SFR1.1.1
then installed ACS updater and flashed SFR 1.2. That fixed his problem. I did it that way too and have not had any issues. Calibrate battery after flashing.
Sent from my SPH-D700 using XDA App
That sort of worked. It made it take longer for things to get hosed over again.So I tried resetting it to stock then flashing EG22, but each time I flash EG22, it doesnt do anything.The version stays at 2.2.1. What am I doing wrong?
What did you flash that is EG22?
Sent from my SPH-D700 using XDA Premium App
In order to better assist you, can you give us a step-by-step listing of everything you are doing? The files you are using with version #'s and your computer OS (with bit version).
I would recommend a full wipe of the phone, to remove any corrupted data
then do a clean install of SRF 1.2
then install the zip to turn on journaling
note: DO NOT use the reboot option until AFTER you have turned on journaling
What I did last night was returned it to factory stock EC05.
Im working with Windows 7 Home x64 on a Mac Pro, because for some reason neither Epic I've ever had will work with my custom built computer.
I flashed the EG22modem.bin with Odin 1.61. That didnt seem to do anything.
So later today, I am going to try this
http://forum.xda-developers.com/showthread.php?t=1184134
The modem only changes the baseband..
regardless, imo it sounds like the problems you are having are due to restoring backups.. is that the case?
I installed this
http://forum.xda-developers.com/showthread.php?t=1205024
and everything is hunky dory in the hood. Thanks for all the help
Hello all... Forgive me if this has already been asked and answered, I've searched for a few days and have not been able to find a solution. Since installing this mod, my phone has been rebooting randomly, at least twice a day, but it does it similarly to the reboots that would happen when long pressing home before the update. Like when using fast reboot.it seems to only happen when waking the phone up out of deep sleep. For instance when I hop in the car after a ten hour work day, plug my aux cable in and use I heart radio.it will act as if the app is buffering, as soon as I unlock the phone and go to check if it is just buffering the phone reboots. At first I thought it was just the app so I switched to pandora, but yesterday and today while on my lunch break I go to the xda app (in an attempt to find a solution to this issue) and go to my favorites and it reboots again. I am using the pulled stock kernel with Crawrj's stock eg30 deodexed rom. I flashed the mod with Chris41g's eg30 cwm plus stock without root and then I flashed back to pulled stock kernel. I've tried uninstalling and reinstalling twice. Any help will be appreciated.
Sent from my SPH-D710 using XDA App
Bump
Sent from my SPH-D710 using XDA App
I know this is the appropriate area, but you might get a faster response by posting your issue in the mod thread. The Dev is pretty responsive.
Just an FYi, I run this mod with Midnight ROM, stream 7 hours or so a day and have no issues.
.....
I know id really like to but unfortunatly I can't post there yet. Since the captivate came out I've never had to ask for help I've always been able to find solutions by reading and paying very close attention.this is the first time I've ever had to ask for help Because everyone is so awesome
At what they do here.thanks for the advice anyways.
Edit: I've also noticed that with this mod I get excellent battery life. UsuallyI get maybe 8 hrs total without it. Even with android os being so high.
Right now I have 81% at 8.5hrs
Sent from my SPH-D710 using XDA App
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...
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....