Alright, so a little bit of background is in order. I've been pretty active with flashing cm7 nightlies and RCs. After my first couple of days on cm7, out of no where all of my haptic feedback stopped working. Tried everything. Restoring backups, and wipes. nothing worked. i unrooted and brought the phone to sprint figuring it was a hardware defect. they do a hard reset, which at the time i didnt know the difference between that and a wipe in recovery (going to bootloader and clearing storage) i think is what they did. fixed the haptic feed back. rerooted, jump back onto cm7 and everything is smooth sailing until i wipe and reflash onto cm7 stable. day or two and good, then haptic feedback is gone again.. before raging too hard.. i try the bootloader clear storage, and BAM the white screen vibrates for the first time.. go to reflash, do so, then haptic feedback is gone.i try to repeat process but now there is no success ;(
any help would be forever appreciated.
Try flashing a different rom, specifically, a Sense-based rom just to see if you have haptic feedback. If so, then you'll know it is a CM7 issue.
posting & replying via the XDA Premium app
I have done so. Just like the previous time when i restored to other backups and tried fresh flashes of other sense roms. ive seen a couple others with the issue, but not much info on trying to establish a logical reason for it.
http://forum.cyanogenmod.com/topic/...163228__hl__haptic__fromsearch__1#entry163228
i hope someone knows whats up :\
Well hopefully there is a guru out there smarter than a sprint tech
Related
I've been rooted for about a month now, playing with various roms and loving it.
However, today, I decided to try FrEak's newest rom using netarchy/toasts latest kernel. Things were going pretty well for a while, then all of a sudden, everything either quit responding or is taking at least a minute to respond, i.e. notification bar, menus opening/closing, touchscreen, etc.
So I did a complete wipe, cache, etc. and flashed the latest BakedSnack rom, again, with netarchy kernel, and same issue.
Does anyone have any suggestions? I'm wondering if going back and re-rooting would help....but if I do, should I use SimpleRoot or the newest unrevoked?
This is killing me!!!!
Last good responding rom I had was Fresh 3.1.0.1, but haven't tried reflashing that to see if it's the roms I'm using or something wrong with my phone.
Thanks in advance.
try a different kernel.
EDIT: Problem Solved
Downloaded Stock Sense 2.2 from here, flashed into that, Reset Data Connection in EPST (Like Here), rebooted and flashed back to CM7. Simple as that!
I realize this may be a bit of repeat thread, But I haven't really got an answer yet.
For reference: I'm running Cm7
Sometime during the day last Thursday, I lost the ability to receive texts. I can send texts, as well as make/receive calls, and data works fine as well. I just can't send them.
Things I've tried include:
Flashing to Stock Sense 2.3
Updating PRL/Profile
Manually installing Radio/PRL/Profile updates
Flashing to a fresh CM7 Install
I also feel like I should add that I tried to open EPST to reset data, but when I enter the code(##3282#) in Phone I get nothing.
Any help would be appreciated, and I'll be on until late tonight as to not keep responders waiting. Thanks.
Go to stock rooted 2.2 or MikG or a custom ROM with the old EPST, the new EPST features less. I just do it on stock 2.2 to avoid any problems when doing the restore. My radios are working, did you flash them individually?
Sent from my PC36100 using XDA Premium App
Okay
Downloading MikG right now, going to give that a try.
And I think that may be part of my problem, I just can't get the radio to update. I've attempted to install them as a combo, and separately in both ClockworkMod and Amon_RA several times. I never get any error messages, it just installs, and tells me to reboot, but nothing ever changes.
That's why I'm going to try to Reset Data in EPST. I had heard elsewhere that my MSL doesn't match what Sprint has on file, or something like that, and that resetting data should fix this.
Anyway, Thanks a lot, I'll be back in 10-15 minutes with results!
Partial Success
As soon as Stock 2.2 booted up and got to setup, the texts started pouring in. Not sure what caused this, but it seems at this point like a Gingerbread issue. For good measure I opened EPST and did a data reset and updated PRL/Profile. I'm about to flash back to CM7 and see if the changes carried over.
It worked! It was that simple all along! Thank you! Just sent myself a text via email that I received on CM7!
foxtrotftw said:
Downloading MikG right now, going to give that a try.
And I think that may be part of my problem, I just can't get the radio to update. I've attempted to install them as a combo, and separately in both ClockworkMod and Amon_RA several times. I never get any error messages, it just installs, and tells me to reboot, but nothing ever changes.
That's why I'm going to try to Reset Data in EPST. I had heard elsewhere that my MSL doesn't match what Sprint has on file, or something like that, and that resetting data should fix this.
Anyway, Thanks a lot, I'll be back in 10-15 minutes with results!
Click to expand...
Click to collapse
If you rebooted in between installing each one, the radios should've updated. You might not notice any difference, but it should work. Glad to hear that your problem is solved!
Everything has been fine until yesterday morning, when at work I realised my phone was rebooting every 3 or 4 minutes.
I hadn't changed anything, I hadn't flashed anything, I don't O/C my phone. I'm usins AOKP Milestone 3 with Immoysen Kernel.
I've tried -
Reflashing AOKP with no custom kernel
Wipe & flashing CM9 Kang
Wipe & flashing MCR
When I tried to make a Nandroid of MCR (as it seemed to be okay for an hour or so) it gave an error when it got to backing up the data partition. Could their be a corrupt bit of memory there?
Also, at one point I think it might have reset while in recovery, which makes me think it's hardware, not software.
Today I've tried -
locking and unlocking the bootloader
Android_Revolution_HD_Super_Wipe_Lite
Wipe and flash AOKP B23
Generally it seems to be better after a wipe and a fresh install, for a little while, but then seems to start rebooting again later.
I locked and unlocked again around an hour and a half ago and all seems good at the moment, but I thought I'd post still to see if anyone else has had this happen or see if anyone has ideas of how to de-bug it should it come back?
I had this problem after upgraded to 4.0.2. Fresh install did solved this somehow but last week it came back again when dial starts...
Tho it seems un-checked all options in location services would not reboot during or after the call
Hope this info could help u
Thanks. Well, 6 hours since I locked the bootloader and unlocked it again (to wipe everything, including the SD storage) and it's not rebooted once. Looks like it's fixed *touch wood*
I have random turn offs... dunno if it relates. Its a little unnerving...and annoying. No roots, no unlocks, just vanilla 4.0.2.
Sent from my Galaxy Nexus using XDA App
Ok, I'm at a total loss. For some reason my gnex running liquidsmooth started rebooting randomly today. I tried wiping cache/dalvik and that didn't work, so I did a factory reset. That also didn't help, as soon I was asked to choose a wifi network the phone froze and rebooted. So I tried restoring to a previous working version of liquid. I still had the same problem. It rebooted every 5 minutes! Then, I tried wiping everything and installing a fresh copy of liquid,but I still couldn't get past choosing my wifi network w/o a reboot. So I finally tried restoring to a really old aokp backup and it STILL is rebooting. what the heck is going on? Can anybody give me any help? Is this a hardware issue? I've also tried two different batteries by the way.
Some more info. It seems to be tied to notifications. I got it running on the AOKP rom on airplane mod, but when i received a text from my wife it rebooted 3 times. I only got it to stop by putting it back into airplane mod. Could it be a radio issue? I'll try flashing some.
why dont you flash back to stock and see if that works fine. that will tell you everything.
Zepius said:
why dont you flash back to stock and see if that works fine. that will tell you everything.
Click to expand...
Click to collapse
Good point. I'll probably try flashing muzzy's rom really quick, since it's supposed to be so stable to see if that does the trick. If not I'll try going back to stock. I've never had to go back to stock with this phone, so I wouldn't mind avoiding it if I can, but anything is worth a shot at this point.
I really just need to nurse it along until the VZW one or Moto X come out. I'm holding out for those at this point.
I wouldn't recommend flashing another custom ROM. You should flash the factory images.
I was trying to activate the AOSP lockscreen on the HTC ONE M8 on Verizon. I succeeded in that, but when I read through the walkthrough further it said there was a way to keep the Touch Twice to Wake and fast charge features. So I continued on to flash the Bulletproof Kernel. I, sadly, didn't pay attention when it said it worked on everything except the Verizon version. Now, I lost my soft buttons and have to reboot anytime I want to switch applications. I've found similar problems, but they were unique to settings found in Cyanogen and other roms. I'm mostly completely stock. It's been suggested that I try flashing Cyanogen or something, but I'd really like to keep the camera and IR functionality.
Solutions I've tried.
Rebooting 20+ times. Didn't work.
Draining the battery, and recharging, and rebooting. Didn't work.
I found a stock kernel and flashed that. Didn't work.
Loaded the backup I had from when I installed CWR. Didn't Work.
Wiped all cache and factory reset. Didn't work.
I'm now out of idea's and need some help. Anything guidance in the right direction would be greatly appreciated.
This was the how-to I was following: htc-one.wonderhowto.com/how-to/activate-hidden-aosp-lock-screen-your-htc-one-m8-0154651/
EDIT: I just put a ROM on it. Fixed my problems for now. I still have no idea what happened though.