I was having some issues with my phone, so I decided to go back to the beginning and odin the first froyo rom using the atlas and re partitioning. I then followed gizmos directions to get to the ec01 rom, radio and kernel. Now my phone randomly goes into back button hell. It will just keep vibrating and go back like I'm hitting the back arrow on the bottom of the phone. I tried do search but with this app I want having much luck. Any ideas on how to fix?
Sent from my SCH-I500 using XDA Premium App
Others have the same issue. I got a new phone, it stopped for about two weeks but then resumed again. So, it either means this phone went bad, too, or it is a bug in the Froyo release itself. I've had this issue since Froyo came out, so it is likely just a Froyo issue.
Sent from my SCH-I500
Related
I have two Samsung Fascinates. Both were wiped clean and Odin flashed with DJ01. I followed all the steps to install SC 2.92 Voodoo. One of the phones works fine. The other phone occasionally stops responding in the middle of the screen.
I went ahead and flashed it back to stock and it doesn't seem to have this problem. I have gone from SC to Stock 2-3 times now, and after a few minutes of use it keeps doing this. Is anyone else experiencing anything similar?
Which odin package did you use to return to stock?
There are a few of us on here who have screen response issues. It's even worse when the phone is charging. No known solution. I think it's a problem that carried over from the i9000 which our current kernel is from. I was going to pull the thread for you but the search function is down.
Some work arounds:
Reboot. It will work for awhile repeat as needed
Don't root...
Try my guide, if it doesn't work still.
http://forum.xda-developers.com/showthread.php?t=1001064
Let me know by posting in guide.
Your guide is what I did twice. It appears that this is a known issue with only certain phones. I also noticed that the display is brighter on the fully functional super clean fascinate.
I went ahead and flashed it to stock took it to the Verizon store showed the person that it wasn't as bright at max settings, they said it looks like a manufacturer defect they will send me another phone and just to mail back the one I have.
I also have 2 FC n other one had that so b4 flashin di01 I flashed eb01 stock rom then flashed di01. Now its working flawlessly
Sent from my SC2.9.2Voodoo/EC10 kernel/Nitro Ultra Honeycomb v3.1 using XDA Premium
I am one of the unlucky ones too. I don't think its kernel related. It does it on the OEM mesmerize kernel too (ec10). I think the only real solution is to wait for our OEM update and if it still does it take it in for an exchange.
Very frustrating! !
Sent from my SCH-I500 using XDA App
I had this problem, but once I wiped data, cache, dalvik, and flashed the newest SC 2.9.2, it went away.
a newbe i am wondering what is the differences between eb01 and di01????
newbe here what is the difference between eb01 and di01???
I haven't had a problem since flashing the jt's new kernel. Not yet anyways
Sent from my SCH-I500 using XDA App
mrtonee said:
newbe here what is the difference between eb01 and di01???
Click to expand...
Click to collapse
EB01 is a 2.2 froyo release (not official)
D101 is an early 2.1 eclair release (oem)
thank you...........
Switched the phone out problem gone
that'll do it..
How did you go about exchanging your phone? Did they make you replicate the problem?
Sent from my SCH-I500 using XDA App
I told them that it does it sometimes and it's completely random. I showed them the phone they made sure it wasn't rooted.... and then they said...ok, we'll mail you a new phone just send yours back
Shinebox said:
I told them that it does it sometimes and it's completely random. I showed them the phone they made sure it wasn't rooted.... and then they said...ok, we'll mail you a new phone just send yours back
Click to expand...
Click to collapse
Just spoke with a VERY nice man at VZW tech support. I explained my problem (leaving out a few particulars of course). He had me boot it in safe mode and wants me to run it that way till Monday. Hmmm, yeah. . .that is not going to happen. He said he will call back at 3:00pm Monday and see if my problem went away. I plan on telling him that it made no difference. Am I being unethical?
I would suggest Gizmo Droid's fix for CWM. I flashed through ODIN and checked Repartition like he said. I followed all of his instructions and my phone no longer gives me a headache. Since doing so, I do experience lag, but I no longer need to lock and unlock my phone to make it work.
Update: Downloaded official froyo and had same screen responsiveness issues. Called Verizon and they are sending me a replacement!!
I've been having pretty good success with Imanut's 100mV voodoo kernal with cpu clocked to 800mhz. However, the screen is still unresponsive when the charger is plugged in
Sent from my SCH-I500 using XDA App
so on the tbolt. if im making a call put the phone next to ear it turns off which is fine
but after a bit if I take the phone off my my ear like if I want to hang up the screen stays off
till I hit the power button and then press end call is that normal I didn't have tthat issue with the x any input please
thanks in advance
I have the same issue, I thought it might be the rom or something, I am running the newest senseless VirusROM B3...but I cant remember if it did the same when I was running Perfect Storm or not , I guess I could flash it back to see...heck I cant even remember if It worked correctly stock
you guys are not running Ziggy's kernel by any chance are you? That was a known issue with it.
I believe that the VirusROM ver that I am running is using Ziggys kernel...I could be wrong, I will have to look. I wonder if that is something that is being worked on....
If this is a constant issue, try a different ROM. Ive had this happen occasionally and i think its the sensor not picking up that the phone was moved.
That is correct.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
Hey guys, bit of a weekend brain teaser for you guys...
My rotation function just stopped working completely a day or two ago. I dont know if its worth mentioning but I actually never use auto-rotation (I just personally dont like/need it much). However, certain programs; Youtube, games, have usually served their proper rotation function when in use.
I've been running SC 2.9.2 with jt's ec10 kernel for quite some time now without any flaws. No changes were made to the phone before the issue.
Kinda sucks not being able to watch Youtube in full screen...
Any ideas?
Interesting. Mine stopped working a couple of days ago as well, also using SC 2.9.2. I'm using jt's 4/7 kernel. I've tried reinstalling both the rom and kernel with no success. In addition to the rotation my compass also does not work, so both the accelerometer and magnetometer have failed. It happened while using Google Nav in walking mode, where the phone froze and became unresponsive. After about 10 minutes of no response I pulled the battery and afterward noticed the problem. I'm planning to revert to stock to see if it helps tonight.
whereas im relieved to know that someone else is on the same boat, i really hope that it doesnt come.down to doing a full back to stock wipe :/
it would be nice to know what caused the malfunction...
Sent from my SCH-I500 using XDA App
Mine's working again after going back to EB01 briefly before going to EC01. I was planning to try out EC01 anyway and the brief revert to EB01 is part of the procedure.
So no matter what Rom or kernel I'm using, my phone goes through phases daily where it seems as though someone is pushing the back button oved and over, but the phone is by itself and nothing touching it. Has anyone experienced anything similar
Sent from my SCH-I500 using XDA App
Yup, I am currently having the same issue, it's at its worst while in navigation. My question was asked here:
http://forum.xda-developers.com/showthread.php?t=1364512
Hope this helps.
I know there are several posting about Vibrants shutting down on its own even when it is fully charged, but, most of the posting are about rooted phones. I am experiencing the same problem but with a stock Vibrant upgraded to 2.2 Froyo. Is there a fix for this problem? I just experienced this problem twice today already and I'm hoping stock Vibrant owners might have a solution.
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
cashmundy said:
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
Click to expand...
Click to collapse
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
dustinkh said:
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
I have put my phone back to JFD via Odin quite a few times, let alone resets, so I wouldn't expect much from that. There will apparently never be a stock ICS for the Vibrant. If the underlying problem is indeed fixed in ICS, the OP may want to make the leap to a good rom at some point.
My GF's phone was on stock 2.2 Froyo and shutdown incidentally, it actually just cut power, black screen suddently. Tried two battery and did the same, reflash to VJI6 and JFD and didn't help at all, but after flashing to Bionix 1.3.1 somehow the problem is gone, weird though
Spontaneous halts and reboots indicate a bug in the kernel or drivers. I don't know what bionic uses. ICS kernels are from the 3.x series of Linux, and are incompatible with older roms. Changing ketnel amd/or radio driver might be a way of attacking the problem short of changing roms. I've changed radios with CM7 but still get the halt/reboots.
A spontaneous shutdowm could also be cause by the battery making bad contact.. try smacking or dropping the phone and see if it happens
sent from the xda app on my android smartphone.