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?
So as the title states, my Epic has been plagued by random reboots since installing EG22. The unit was a new replacement, not a refurbished replacement that tech support normally gives. I've had it all of four weeks now. It ran EF02 pretty perfectly. I have tried reloading EC05 (with ODIN) then loading EG22, and no dice. Before I flash EG22 I wipe the phone, cache, and dalvik 3 times. I've also redownloaded and hash checked the EG22 update I use (using the stock/deodexed EG22 update.zip from the development forum). Still no improvement, the phone will randomly reboot every 1-2 hours. Any advice on what I could try next is appreciated.
radugb out
UPDATE: also I cannot get into the "SYSTEM UPDATES" menu in the Settings/About Phone menu. Each time I try I get a forced close then a system reboot. Could the phone just not like EG22?
I have experienced reboots on both EE03 and EF02. I haven't tried EG22 as of yet. I hae never had it happen on EC05. I figure I'll just wait until the release because my phone just doesn't like the beta/leaked stuff.
Any test software has a chance that it will not work 100%
All Gingerbread leaks crash and reboot in low signal areas. I am assuming this is one of the reasons official hasn't been released yet.
Sent from my SPH-D700 using XDA App
Ok, but one I have an airave about 12 ft away from my phone so I get a great signal. And two, I'm still getting FC's when I try to enter the system updates menu. So I still think it could be something wrong with my phone.
radugb said:
Ok, but one I have an airave about 12 ft away from my phone so I get a great signal. And two, I'm still getting FC's when I try to enter the system updates menu. So I still think it could be something wrong with my phone.
Click to expand...
Click to collapse
How did you install EG22? If you did it through CWM it could have just been a bad flash. For the system menu problem. The crashes occur for me too, like above post low signal areas are not a gb leaks friend.
Sent using TouchPal Curve Input
I have been flashing zip versions thru CMW. I'll look up an ODIN-able EG22 tar or md5 and try it that way. But I will ODIN back to EC05 (with repartition to wipe the phone) then update to EG22. I'll let you all know.
As far a signal goes though, I'm getting full bars right now because my Airrave is so close to me.
radugb said:
I have been flashing zip versions thru CMW. I'll look up an ODIN-able EG22 tar or md5 and try it that way. But I will ODIN back to EC05 (with repartition to wipe the phone) then update to EG22. I'll let you all know.
As far a signal goes though, I'm getting full bars right now because my Airrave is so close to me.
Click to expand...
Click to collapse
You are right, that shouldn't happen with an Airave. A reflash may fix the issues you are having. Also don't use any CPU managers like SetCPU or Voltage Control on GB until source code and custom kernels show up.
Sent from my SPH-D700 using XDA App
Yup. That was it. Bad flash. This time I d/l'ed a .tar version of EG22 to flash with ODIN. Much better than before. No more FC's from the system menu and its been running 8 hours straight with no reboots. Muchas garcias.
radugb out
Glad to help.
Sent from my SPH-D700 using XDA App
Spoke too soon. I've had two random reboots, one yesterday, one today. So it definitely fits with what all y'all said that leaked GB ROMs tend to crash. Still not as bad as before, and I no longer get the FC's from the system updates menu.
I had one last night and one tonight at my house which I get a crap signal at in what Sprint describes as an "excellent coverage area" No other problems anywhere else.
I've had my first random reboot. Phone was WIFI connected, and forced roaming (Sprint has a tower down in my area, going on 7 days now). It was in the middle of a content update for an application I run, so I'm wondering if there is a memory leak for the network user or kernel space.
Does anyone know of an application that will keep a log of memory usage to track if a process is not releasing its resources?
Yup, same here. About once every two days I get a reboot. I haven't been able to connect anything I'm doing to the reboots, and it usually does it while the phone is just sitting.
Trouble is, Gingerbread is soooo much better than Froyo I don't want to go back
I really think it is the modem crashing.
You may want to try another modem.
also, i realised that on my wife's epic with eg22, it rebooted about 5 times a day, most of the time, it was right after using the slide out keyboard.
i deleted the keyboard counter slide apk thingy, since then, 1 reboot a day.
not great, but definitely better than 5.
x130844 said:
I really think it is the modem crashing.
You may want to try another modem.
also, i realised that on my wife's epic with eg22, it rebooted about 5 times a day, most of the time, it was right after using the slide out keyboard.
i deleted the keyboard counter slide apk thingy, since then, 1 reboot a day.
not great, but definitely better than 5.
Click to expand...
Click to collapse
Are you sure it is not a loose battery connection? My phone would do that with the extended battery and case. Had to put a little piece of thick paper in there to hold it tighter.
Definitely was the modem. I flashed the EE02 modem & now no random reboots. Signal(s) & battery life have gotten better too. I would have flashed the EF02/EF10 modem but that downgrade notice is oh so damn annoying!
Me and my friend have the same issue on our Epics OP, Its annoying but Im dealing with it cause these roms are so much better than pre eg22.
I dont have any random reboots but I get a random double vibrate. I have no idea where that is coming from
I've had two random boots since I've odin'd from EC05.. though I feel it was memory leak,and the phone just shutdown without sufficcient ram.
SchizioPunk's Epic Experience 2.1 Eclair -> Odin to EC05 Froyo. Rooted. Bloatware Removed. Voodoo Sound V9 Module Loaded. TouchWiz4. Enjoying my Customized Stock Experience.
Yeah well I tried the EH06 modem and it broke the 4G (amongst other things). So I got ol' reliable EE03 to fall back on.
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
willjr0k5 said:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
Click to expand...
Click to collapse
I'm having the same problem with the stock ff18 rooted...started out of the clear blue, can't place my finger on a consistent pattern. I'm gonna try installing a new kernel and see if that helps. If it works I'll let you know.
I disabled facial recognition security and cleared dalvik and normal cache with clockworkmod. My phone hasn't rebooted basically all day so far.
Something must have been stuck in the cache possibly that was causing issues.
Sent from my SPH-D710 using xda app-developers app
So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?
Bump. Any help? Still happening, though not as common, when I flashed stock
Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?
Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium
Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium
I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.
Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..
@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.
+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2
I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag
Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?
Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app
SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.
solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you
Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be
anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.
Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!
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....