I've been using CM10 for a while now, so that's what I'm on. Usually using Erickwill's nightlies - currently 12/06. And yet lately, my service will just go out. I mean, completely randomly, as far as I can tell. I haven't been able to pin it down to any possible cause. As far as radios go, I've been switching between UVLH1 and UVLI1, but that hasn't helped. It's really frustrating because rebooting won't help, so I have to reflash.
Can anyone think of what might cause this? I realize this is a tough question to answer with so many possible variables, but I'm just wondering if anyone has seen/heard of this and/or can think of any possible causes and what I can do about it. Thanks.
Edit: I just toggled 2G/3G and that "seemed" to make it work. I wonder if that could be the reason.
Related
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
Hey guys I've been away from the forums for a while now and I wanted to see if I could get a quick answer. I searched and am still unable to come up with a fix for this loss of data. I am running cm9 a4. I have been toggling on/off airplane mode for a quick fix, but I was hoping for an easier way to work around this. Thanks guys
Sent from my SPH-D710 using xda premium
I've only seen this complaint on cm9 and aokp and it happens to some people sometimes. I suspect once source is available this problem will be fixed but until then I would try installing the latest leak or a tw based rom and see if you still have the same problem.
Dont forget the A in cm9a4 = alpha
Are there any other threads related to this problem? I just got an E4GT two days ago and I pretty much immediately flashed it to AOKP, but the signal icon is almost always grey until I toggle data even though it shows 3G/1x. Does anyone know what exactly causes it to happen? Does data stay connected as long as I'm actively using it? I'd hate for it to cut out while I'm doing something (like using navigation, streaming music, etc).
Alright so not even a week ago got my Nexus coming from a Charge so don't know if maybe there's something I'm missing or overlooking, but when running stock then Liquid Smooth 1.4 I have a signal and data (even though I have poor signal strength, don't know if that might be part of the problem.) So when trying to flash any other rom/kernel combination I won't have a signal and I'll start roaming and won't connect to data. I've looked and couldn't find anyone else with the same problem. I've tried AOKP, MIUI.us, Black Ice with Franco, IMO Lean, Popcorn etc. I did a clean install and have the newest radios (even tried the leaked 404 radios) but to no avail. I'm hoping there's something I overlooked but I dunno. ANY help would be MUCH appreciated as I would definitely like to try out some of these awesome roms (not that there's anything wrong with LS) because that's the whole reason for getting rid of my Charge (lack of development) And no, none of the roms I flashed were GSM versions. Thanks in advanced to anyone who can help!
Well that's interesting... my first thought would have been that the activating screen at the beginning after every flash takes a little more "juice" or power to get a reliable signal, but if you're going back to LS and it connects fine every time, then it couldn't be that... have you tried going back to stock and seeing how your phone reacts to that?
anton2009 said:
Well that's interesting... my first thought would have been that the activating screen at the beginning after every flash takes a little more "juice" or power to get a reliable signal, but if you're going back to LS and it connects fine every time, then it couldn't be that... have you tried going back to stock and seeing how your phone reacts to that?
Click to expand...
Click to collapse
I know that before I flashed LS there were no signal/roaming issues. That's actually a thought I had today at work and was going to use my nandroid from before LS when I was still stock. Also I am going to try flashing from stock. Didn't think it would be an issue coming from LS as long as I wiped everything but we'll see. Got my fingers crossed and if anyone else can think of something it might be please feel free to let me know. It's frustrating to want to try out some new rom goodness and can't get service/roaming... Thank god for nandroids
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
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.