Hi guys, I recently installed CM on my N4 and at some point on day one the vibration got completely disabled. No haptic feedback, no vibration when my alarm goes off etc.
Obviously I double checked all options already. Rebooting doesn't help either.
What could the reason be and how to fix it?
I don't think it would be a hardware failure, but to be sure you can try dirty flashing your ROM and that would also reflash the ROM's stock kernel, and if there is still a problem, try flashing a custom kernel. If all fails, flash back to stock.
Sent from my Nexus 4 using XDA Free mobile app
Related
Anyone else had this / any ideas - my s4 randomly reboots. Can sometimes be when I'm using it or other times when it is sitting idle.
Sent from my GT-I9505 using xda premium
if you can go to download mode flash a new stock rom using odin . before it try with a factory reset too :laugh::laugh:
quibble8 said:
Anyone else had this / any ideas - my s4 randomly reboots. Can sometimes be when I'm using it or other times when it is sitting idle.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
yup, i had this after running a custom rom for a few days. i'm sure it wasn't the rom though, i restored back to stock last night just in case, we'll see.
However, in the future, please also post your ROM, kernel, etc.
For example, having your phone OC might result in such random reboots...
okty2k said:
However, in the future, please also post your ROM, kernel, etc.
For example, having your phone OC might result in such random reboots...
Click to expand...
Click to collapse
I didn't change the kernel and I don't want to name the ROM because I'm sure it's not its fault - it was fine for a few days with plenty of reboots and activity/usage. Sounds like others on stock have the same problem (not necessarily related to the camera issue), so I've gone back to my stock backup and will see what transpires.
ch0use said:
I didn't change the kernel and I don't want to name the ROM because I'm sure it's not its fault - it was fine for a few days with plenty of reboots and activity/usage. Sounds like others on stock have the same problem (not necessarily related to the camera issue), so I've gone back to my stock backup and will see what transpires.
Click to expand...
Click to collapse
I understand you, but it is not like blaming the ROM creator. Is that you might have discovered a bug, and you can help to get it solved.
personally, the first thing I would do is to make a factory reset. This is not the case for you any more... but however.
Good luck and please tell us got things go on...
Fair enough, it was slim bean build 6 on Verizon. I reverted to my stock twrp backup last night (10hrs ago) and been fine so far...
Guys plz help me out. I have got a weird problem with my note 3. I am on stock 4.4.2 NA6 rom rooted. I flashed halazsk universal5420 kernel using twrp recovery and cleared dalvik cache...on the first boot after flashing the kernel Everything seems working including Overclocking and undervolting...but eventually my phone starts heating up badly. And once I restart my phone...It has trouble waking up. After I lock and unlock it ..A black screen stays for a second or two...and my phone hotboots and the same problem continues...and the phone heats up really bad...I tried both 13b and 14b versions...none worked...plz help me out guys...I really want to use this kernel
Thank you!
Sent from my SM-N900 using Tapatalk
subham964 said:
Guys plz help me out. I have got a weird problem with my note 3. I am on stock 4.4.2 NA6 rom rooted. I flashed halazsk universal5420 kernel using twrp recovery and cleared dalvik cache...on the first boot after flashing the kernel Everything seems working including Overclocking and undervolting...but eventually my phone starts heating up badly. And once I restart my phone...It has trouble waking up. After I lock and unlock it ..A black screen stays for a second or two...and my phone hotboots and the same problem continues...and the phone heats up really bad...I tried both 13b and 14b versions...none worked...plz help me out guys...I really want to use this kernel
Thank you!
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
And what happens when you DO NOT overclock or undervolt? Some devices frown upon undervolting, lets use the default settings and monitor it from there....
Good luck!
Thanks
I face these problems even on stock settings...just after flashing kernel
Sent from my SM-N900 using Tapatalk
I was on xdabbeb's ROM, and I decided to install Cloudy's G3 rom. I didn't like it, so I decided to clean flash xdabbeb's ROM from scratch. After installing it, I noticed that knockon didn't work but knock off worked fine. I clean flashed it again, it still didn't work. Then I clean flashed Mahdi's July 9th build, and knockon works perfectly fine. Then I flashed Cloudy's G3 ROM again and knockon worked. Then I flashed xdabbeb's ROM and knockon didn't work.
How do I fix this? I want to go on xdabbeb's ROM but knockon won't work anymore on his ROM. I think Cloudy's ROM has messed it up. It's definitely not a hardware issue.
Enter the service menu for your model:
3845#*XXX#
Where XXX is your model, for example I have D802 so I type:
3845#*802#
Go on Settings, and hit "Update Touch Firmware".
Wait a second, and see if it works.
Im sort of experiencing the same issue. I kdz'd to full stock re-rooted, ran a few aosp roms, then flashed cloudyflex and now knockon only works with stock based roms.... If you knock 5 times will yours wake? Mine will after the 5th tap, but that gets annoying pretty fast. And I cannot access the service menu in any aosp roms anymore either. It just inputs my code (being a d801) and never goes into the menu, but it works fine in the stock based roms.
Because the service menu is available and is part of stock ROMs only.
OK, good to know. But has there been a fix for this I know there are others with the same problem. Gonna redo the phone this weekend to test some things, but maybe there is an easier fix than returning to full stock...
Also it affects my recovery. I'm using dr87's custom twrp 2.7.1.0 and I have to knock 5 times to wake from there as well...
Sent from my LG-D801 using Tapatalk
AspenSTi said:
OK, good to know. But has there been a fix for this I know there are others with the same problem. Gonna redo the phone this weekend to test some things, but maybe there is an easier fix than returning to full stock...
Also it affects my recovery. I'm using dr87's custom twrp 2.7.1.0 and I have to knock 5 times to wake from there as well...
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
From what I've read it seems to be a kernel issue. When you restore it gives you a patch kernel and that doesn't support knock on. Does anyone know a kernel that supports knock on? It'd be much easier to update the kernel rather than redo the whole phone and go back to stock.
Not sure what you on about but I've been on stock, Mahdi, Paranoid Android and now Cloudy G3 and my knock code works and I can enter service menu.
curiouscow said:
From what I've read it seems to be a kernel issue. When you restore it gives you a patch kernel and that doesn't support knock on. Does anyone know a kernel that supports knock on? It'd be much easier to update the kernel rather than redo the whole phone and go back to stock.
Click to expand...
Click to collapse
I've tried a few different Kernels while on aosp, all giving me the same results. I'm now on a clean flash of cloudy g3 and will try again tonight to see if it changes anything with an aosp rom. If not I'll go back to full stock just to see what changes and when.
Sent from my VS980 4G using Tapatalk
Fixed it for myself. I kdz'd back to 20a and now knock-on works as it used to. I don't use knock code so I'm not missing anything as of yet... Just thought I'd pass the info along.
The phone turns off randomly and i'm unable to turn it back on unless i'll take out the battery for a moment or connect it to a charger.
When using the charger method, the phone will display the empty battery animation but turns on when i hold the power button.
I can't point a specific scenario that cause the shut down, however, it seems like the phone uses more power than the battery can provide.
For example:
Happens in various battery percentage.
Happens more frequently when using navigation or Bluetooth.
Happened with stock kit kat rom.
Happened with cm12 (philz touch 6 recovery).
Sent from my SM-N9005 using XDA Free mobile app
Sounds like a defect battery to me. Is there a bulge or bubbles on it?
Have you tried a new one?
Sent From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Try a different kernel.
Morningstar said:
Try a different kernel.
Click to expand...
Click to collapse
at my 9005 work fine
CivZ-KK_Xplorer-Rev1.9-sm_n9005-4.4.2
it's very good
but i dont like cm 12
I want to try to replace the kernel, but since i'm using cm12 (5.0.2 lollipop) i can't determine by myself which one to install.
The n9005 kernels page here on xda show only kernel with kit-kat versions in the title or no info at all.
Ultimate kernel page for example doesn't say if it will work.
Olso, do i need to touch the rom or i can just install the kernel from the recovery and then reboot into my already installed cm12 rom.
Thanks for the advices.
Sent from my SM-N9005 using XDA Free mobile app
Hello everyone.
For the past two weeks I have been having this frustrating issue. Since I couldn't find a suitable rom for my canadian note 3, I decided to go back to stock rom but when I flash one through ODIN, back button just doesn't work!
when I went back on flashing custom roms, it works perfectly! what's the problem? I did install the latest official stock rom! :crying:
-----------------
I forgot to mention, the back button works when I use the S-Pen in stock roms. the back button just hates my fingers
There may be a problem of button configuration on the stock room.
Of you have root access then you can change the button layout.
Once compare the button layout of the stock rom with the custom rom.
Sent from my Moto G using XDA Free mobile app
---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------
IIABODEII said:
Hello everyone.
For the past two weeks I have been having this frustrating issue. Since I couldn't find a suitable rom for my canadian note 3, I decided to go back to stock rom but when I flash one through ODIN, back button just doesn't work!
when I went back on flashing custom roms, it works perfectly! what's the problem? I did install the latest official stock rom! :crying:
Click to expand...
Click to collapse
I think below guide may give you some idea.
http://galaxy-note2.wonderhowto.com...-2-for-easier-left-handed-navigation-0146943/
Sent from my Moto G using XDA Free mobile app
@shibaa987 the problem is, the area where the back button is is completely unresponsive. When I touch the back button, not even the backlight turns on.
IIABODEII said:
@shibaa987 the problem is, the area where the back button is is completely unresponsive. When I touch the back button, not even the backlight turns on.
Click to expand...
Click to collapse
I got your problem. Sometimes back I had the same problem on a Sony Xperia phone. Part of the display was not taking touch input.
Initially i thought the digitizer was corrupted. I also changed my ROM but no luck.
And then I just stick to one rom. Finally after some days it just got solved automatically.
I suggest you to check the stock rom with a custom rom kernel which will work with the stock rom.
Sent from my Moto G using XDA Free mobile app
shibaa987 said:
I got your problem. Sometimes back I had the same problem on a Sony Xperia phone. Part of the display was not taking touch input.
Initially i thought the digitizer was corrupted. I also changed my ROM but no luck.
And then I just stick to one rom. Finally after some days it just got solved automatically.
I suggest you to check the stock rom with a custom rom kernel which will work with the stock rom.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
can a custom kernel solve the problem?
See... Different roms are built by different developers and you may not know how much buggy they are.
If you have a custom rom where you don't have this issue and the rom is perfect for you then you can chose one accordingly.
Sent from my Moto G using XDA Free mobile app
shibaa987 said:
See... Different roms are built by different developers and you may not know how much buggy they are.
If you have a custom rom where you don't have this issue and the rom is perfect for you then you can chose one accordingly.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
YES! it finally works. I never thought a kernel would cause the problem. I put too much trust on the stock rom . Thanks man!
Awesome - what kernel did you flash to fix this? I have the same phone with the same problem (SM-N900W8 with Stock 5.0)
ste52653 said:
Awesome - what kernel did you flash to fix this? I have the same phone with the same problem (SM-N900W8 with Stock 5.0)
Click to expand...
Click to collapse
Same, please let us know which? tytytytyty
I had the same problem and the same phone after rooting stock lollipop with cf-autoroot. Back button would not work. So I installed custom recovery and Resurrection remix ROM and back button works again and couldn't be happier!
ste52653 said:
Awesome - what kernel did you flash to fix this? I have the same phone with the same problem (SM-N900W8 with Stock 5.0)
Click to expand...
Click to collapse
Camorda said:
Same, please let us know which? tytytytyty
Click to expand...
Click to collapse
sorry guys i forgot to check this thread, i'll attach the kernel I used. Unfortunately I don't remember which thread i got it from but I hope it helps. Use it at your own risk!