My Captivate won't stop vibrating. Whenever I use the LED touch pad or access any applications it will vibrate for a minute or so with one long vibrate and then two short. I can't get it to stop and its really frustrating. I have the ATT ROM installed on a rogers phone, no issues until now.
It is rooted, OCLF. I have tried removing the SIM, battery, rebooting it, all with no success. In dmesg I see the following when it happens:
[Warning]
[VIBETONZ] enable_vibetonz_from_user : time = 150ms
[Warning]
[VIBETONZ] ENABLE
[Warning]
[VIBETONZ] DISABLE
the only thing I can think of doing prior to this is I installed the SMS time fix but I have since removed it and the problem continues. Anybody have any ideas?
Force closing, flash back to stock and try again.
I was hoping that somebody wouldn't say that.
Edit: I ended up wiping all user data, which has fixed the problem, it avoided having to flash it again, still annoying.
Related
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
This is not a reason to start a new thread in the Development forums.
Support and Q&A for custom roms should take place in their appropriate threads. Use a bit of common sense, courtesy, and patience -- people will help you.
Please read the rules of posting new threads again here: http://forum.xda-developers.com/showthread.php?t=788800
anoneemooz said:
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
Click to expand...
Click to collapse
1) Lock ups most likely due to removing drm file from system apps.
2) Your using lagfix (I assume) and when you pull battery data corruption is very likely on some configs.
3) Read rules before posting.
TL;DR: My phone is experiencing a very similar problem to the broken internal SD after Froyo update, except on eclair and is fixed (apparently temporarily) with a factory reset. I'm on Telus, bought the phone from somebody off craigslist and have a return receipt. What should I do?
So for the second time in a few days my Samsung Galaxy S (I9000M from bell, bought on craigslist running on telus) was having problems opening an app so I restarted it. (The first time Market would force close whenever I tried to open it, the second time it was Browser). After the app force closed a few times I did a restart. The first time I restarted it (when Market froze) it went to the lock screen, with the default background (it looked like my data was all wiped). After unlocking the screen, I got a perpetual series of force close messages. This happened each time. I had to do a factory reset and lost all my settings, photos, messages and everything (No backups, of course. Facepalm). Then today I pretty much had it back to the way it was before the reset, and Browser force closes repeatedly on opening. I restart the phone again and this time it only gets to the 'S' animation then goes black/restarts after the animation stops. The capacitive buttons sometimes light up. Similar to the issues from the Froyo update I think, except I didn't update to Froyo. I can get to the 3-button recovery screen and do system reset as well which seems to not help the froyo issue, I think. It's currently working but I'm not sure how long that will last. I'm not pleased about having a phone I have to re-setup every few days. (I'm actually pretty angry...)
Anyway, I have a "Mobile Device Repair and Return Receipt" from the seller from craigslist. It's still under warranty. Anybody else experience this? Can I take it to bell and have it fixed with the documentation I have? What would you suggest I do here?
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
good day fellow razr i owners,
my razor i (91.2.26001.XT890.Retail.en.EU) is behaving very strangely since it got it back from support with a new mainboard. Sometimes it just freezes or crashes, and when I reset it, it's often bootlooping around the flashing M-Symbol with a little clicking sound everytime it starts over. I can get it to boot up if I keep resetting it, shutting it down, starting it again aso. I can get into fastboot and even then it's not certain that it boots up afterwards. I managed to get into recovery mode with a process log that started to overlap the lines of text. Sadly I can't manage to get that again for further troubleshooting.
The easiest thing would be to send it in, but I've already done that only to get it back with the comment "couldn't reproduce the problem, upgraded the firmware".
Since then I try to reproduce the crashes so that I can proof the defect even to a service team that starts it up, sees it works, shuts it down, flashing it and sending it back...
Crashes and/or Freezes can appear when I'm handling it or not. When I'm browsing with Chrome, using the camera, use Google Now, play Simpsons Springfield...
Sometimes background processes stop to react spamming me with messages like "the process com.google.process.gapps isn't answering" -> OK (translated from german)
Since these problems started after a motherboard change after a brick (downgrading from 4.1.2 to 4.0.4) I'm thinking it's a hardware problem.
I tried to create a logfile with adb shell dmesg > log but only got "klogctl: Operation not permitted"
It seems to start more reliable when not used for a while after a crash (cache clearing?) and it seems to crash more often when plugged in
factory reset seems to work for a while but after 2 days at most it keeps crashing/freezing again
I would love a fix for the phone, but I don't think there is much I can do when it's really a hardware problem so next best thing would be a way to get a error log, that I can send the support with my device as proof that there is a problem and all that obviously without voiding the warranty...
Thanks in advance for any help
Freeks
Hey all
Having some troubles with my I9305 running 4.1.2 stock and rooted
The phone was factory reset only a few weeks ago and has run well since.
The below problem occurred once before, since the factory reset, however simply resolved itself after 6-8 hours. It has returned and remains
On startup I'm getting the 3 following processes crashing and it's rendering the phone unusable.
Unfortunately, ContextProvider has stopped
Unfortunately, TwDVFSApp has stopped
Unfortunately, SystemUI has stopped
After enough time I'm able to clear these by pressing OK, and enter my lock screen code, at which point the phone simply freezes.
Hitting emergency call at this point results in android.process.acore has stopped.
I'd add that everything is as it should be on the screen, other than no status/notifications bar at the top
I do also have Airdroid working and allowing me to browse
Any thoughts?