Hello,
Just got my oneplus one and something weird happend (just making sure if something is wrong before I install all my stuff), I was typing a message and suddenly the vibration motor cut out... I powered the device off and there was no vibration on start up, I thought it was broken, after it booted I was looking up people with issues like this when I received a message and my phone vibrated again! It was a weird glitch and I hope it's not a loose contact or something
Running resurrection remix with boeffla kernel!
Is this just a weird glitch or something that needs to be checked out?
Related
Heya
This is the strangest thing ever. I'm using my Vox for around a year now, and it never happened. In the last two days, the vibration in my Vox is almost completely down!
The phone will not vibrate at all, except the regular vibration it shuts down. So I am assuming (and hoping) it's not something with the device that failed. And there is no reason for that, I really keep my cell safe, and I'm sure nothing happened to it in the past two days for sure. It just... decided it only vibrates when it shuts down, which is strange.
It really bugs me because I'm a Vibrate mode person. OK, that sounded bad. But yes - I always put my Vox on Vibrate mode, I just like it better, and since it's always in my pocket I never miss calls. So now when somebody calls it just pops it on the screen, it's like a silent mode.
I'm using Fireburned's WM6.1 CUSTOM ROM v1.0 (STABLE) for Vox. It worked fabulous for the past few weeks - so I'm guessing it's not it...
I did not install anything new in the past few days either, so it's just plain confusing. Rest of the device features seem to work as usual.
Any suggestions?
Thank you guys, so much!
I'm using the same ROM and I also have issues with the phone not vibrating.
Hmm. can you post more details Rudolfje? How long have you been using the ROM before it happened?
Sinds I'm using Fireburned's WM6.1 CUSTOM ROM v1.0 (STABLE), my phone doesn't vibrate (It vibrates only at the boot or shutdown).
I have the samy problem every now and then.
It seems that it stops working after i started some sort of process?? iven then it's random.
For me a reboot works
Could be a conflict with certain software?
I'm using fireburned's custom rom too btw
I had the same problem when I was useing Notifications in Automatic Keylock program.
I started using the Custom Rom a couple of weeks after it was released. Somewhere in January, I think.
I don't use notifications and a reboot solves the problem.
Go to start-Expert-Config Notification choose Enable Script and press OK.
This is how it worked for me.
Could it be that the automatic keylock is somehow interfering with the notification script?
I stopped using automatic keylock & screensaver and all is working well.
Rudolfje said:
Could it be that the automatic keylock is somehow interfering with the notification script?
I stopped using automatic keylock & screensaver and all is working well.
Click to expand...
Click to collapse
I am using them together again and they are working.
I've had this problem occur several times with several ROMS, with and without Keylock and Gonzo's notification scripts. I honestly have no idea what caused it and, in my ignorance, I just reloaded ROMS to fix it. Yes, I know, very helpful. I do know that it isn't happening again, despite using the same ROM as before (Gonzo's latest Rose ROM).
Hey there guys,
For some reason my phone started vibrating during calls like 2-3 weeks ago. I have no idea why it is vibrating but it is starting to get really annoying. It vibrates like every 5-10 seconds during the call and on pick-up and hang-up. Anybody have any ideas how to solve this? would appreciate it deeply.
I am on absolution 1.1 currently
abehbeh said:
Hey there guys,
For some reason my phone started vibrating during calls like 2-3 weeks ago. I have no idea why it is vibrating but it is starting to get really annoying. It vibrates like every 5-10 seconds during the call and on pick-up and hang-up. Anybody have any ideas how to solve this? would appreciate it deeply.
I am on absolution 1.1 currently
Click to expand...
Click to collapse
Check in the settings > calls, there should be some setting there that allow you to mess around with the vibration settings. I know there is an option to have it vibrate on pick up and hang up. If not there, check the CM settings.
You could also flash the newest Absolution Rom. If youre going to do that please follow all steps.
Vibrating
Check your settings and also reread the DEVs thread. It can be a setting related issue and it could also be a rom issue. I know this as I was running a rom that the DEV stated to turn the vibration setting off (uncheck) as it may be a little buggy.
So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.
thexlizardxking said:
So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.
Click to expand...
Click to collapse
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.
bblzd said:
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.
Click to expand...
Click to collapse
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?
thexlizardxking said:
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?
Click to expand...
Click to collapse
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.
bblzd said:
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.
Click to expand...
Click to collapse
That's good. I hit it a couple more times, and it's working right now. I'll see how it progresses.
Thanks
Hey guys
i have a little problem with my Oneplus One. I'm running on Temaseks unofficial build v4.0 with AK kernel 0.76. but the same problem goes on slimsaber.
the problem i have is that often when i get a lockscreen notification from whatsapp + or other applications, the OPO restarts itself. before it does that, the notification light comes on and when i double tap or use the power button to wake the phone, the screens stays black. it takes nearly 3 seconds before it reboots itself and i can't find a solution. it does not happen everytime, mostly when i get a whatsapp notification from whatsapp. but that is not uncommon, since the most nots comes from whatsapp+.
So i guess it is the AK kernel or the 5.0.2. Android rom itself. anyone else got this problem so far?
What i tried:
Fresh installing the Rom, no dirty flash, tried to deactivate the lockscreen notifications, tried to turn off the not light. turned off the notification from whatsapp itself, all that doesn't help.
Sometime it reboots even when the screen is on, after i taped the screen, when i got a notification, but it only appears when the screen is off.
Any solutions? Or someone got the same prob?
Regards Mike
EDIT:
okay i solved the problem myself. Seems to be a problem with AK kernel. tried it now multiple times with and without AK Kernel and without the lockscreen notification works good, with AK it reboots nearly everytime. Would be great if someone could contact the developer, since i cannot answer in his thread itself. sorry and thanks
Hello and pretty much as the title says for some reason I cannot dismiss my alarm. If I dismiss it it turns itself back on a few seconds and sometimes minutes later. I first noticed this on Blisspop but I have since clean wiped (including locally stored files) and put CM12 back on but oddly the problem is still occurring.
Has anybody else had this problem?
PS I did have a good google around but cannot seem to find something that related to my problem :\
loonitic said:
Hello and pretty much as the title says for some reason I cannot dismiss my alarm. If I dismiss it it turns itself back on a few seconds and sometimes minutes later. I first noticed this on Blisspop but I have since clean wiped (including locally stored files) and put CM12 back on but oddly the problem is still occurring.
Has anybody else had this problem?
PS I did have a good google around but cannot seem to find something that related to my problem :\
Click to expand...
Click to collapse
I'm on Blisspop unofficial that include CAF kernel... And i don't facing that kind of problem...
Are you sure that you are dismiss it, instead of just snooze it?
Hello, definitely dismissing it. I decided to wipe every bit of info\data etc on the phone so that nothing is left, installed CM12 again, without GAPPS so that it cant pull any settings that might be stored on my google account and guess what? Even on a pretty much blank rom I am still getting the same issue :\. Now starting to think it could be hardware but it seems very unlikely.
I have been facing same problem. It comes back after I dismiss an upcoming alarm after turn off the screen and turn it back on, it comes back. Any suggestions?
Same issue on CM12.1 ROM I'm using. I dismiss the upcoming alarm, but most of the time it activates back.