So I undid the OCLF and unrooted then accepted the ota update which got my phone stuck at the Samsung screen. Tried a bunch of steps and ended up using ODIN to go back to stock and update that way. My phone had never lagged so much after that. Once the new lag fix came out I updated and applied it. Now my phone runs better but still lags a little, mainly when using any keyboard to type. I was thinking of wiping my phone to stock using ODIN then running the kies update and seeing if that fixes things. Anyone else seen these issues?
Sent from my Rooted Samsung Vibrant using XDA App
Related
So, two days ago I noticed my accelerometer was suddenly not working.
I also noticed that my version number showed the JI6 update on it. I was surprised because I never got a confirmation or choice to install. I heard that folks were getting this OTA, so I assume that it just went ahead and did it... which is a little scary.
My phone is rooted and has RyanZA's lagfix on it.
After checking it out for a day, I decided to go back to that original factory ROM.
Here is why:
WORSE gps!!!!!
broken landscrape mode
nandroid gone.
Also, what is weird is that I didn't get some of the new features people mentioned such as the battery indicator, HD camera app, and task manager.
So, did I really get the OTA update or something else. Anyone have any ideas?
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
Latest HomeBase (BLUR with kernel). When I first got the phone after a few hours you cannot hear or speak. You have to restart the phone in order to make or take a phone call. Assumed using a new rom would fix it considering the Sprint OTA fixed it but I still have the issue. After anywhere between 2 hours and 8 hours of the phone being on is when the problems start.
It was my understanding this was Software related but after trying a few roms with the same problem I don't know? Should I just go back to stock and install the OTA? Roms are cool but being able to talk is better.
I would. Also you should have posted this in the Q&A section or in the homebase rom thread.
Sent from my MB855 using XDA App
What version of the Home Base rom are you on? I'm on v1.5 with the 4.2 update and have no issues. So perhaps you could try that one? And I had that issue until the OTA update too.
b0r0b said:
Latest HomeBase (BLUR with kernel). When I first got the phone after a few hours you cannot hear or speak. You have to restart the phone in order to make or take a phone call. Assumed using a new rom would fix it considering the Sprint OTA fixed it but I still have the issue. After anywhere between 2 hours and 8 hours of the phone being on is when the problems start.
It was my understanding this was Software related but after trying a few roms with the same problem I don't know? Should I just go back to stock and install the OTA? Roms are cool but being able to talk is better.
Click to expand...
Click to collapse
To start, this isnt any type of development so it should be posted in general....
My question to you is do you have a Sprint airave in your home? That was the issue i had. If the problem is in custom roms try stock again.
xTMFxOffshore said:
What version of the Home Base rom are you on? I'm on v1.5 with the 4.2 update and have no issues. So perhaps you could try that one? And I had that issue until the OTA update too.
Click to expand...
Click to collapse
I've recently flashed v1.5 and updated with 4.2. Loved it except that when I tried to download anything in the market it would tell me that there was insufficient space on my device. I had even reformatted my external and internal storage. Then I tried using the marketfix.zip. It would say it was downloading and then disappear from my notifications. I was wondering if you were having this problem at all?
The only time I have had a market issue was when I first flashes the ROM and it was the old market then it dud a little song and dance and ypdated to the new market at which point anything I was downloading prior was gone. But after that haven't had any issues. Is this the issue you are having? If not.....try to reflash the ROM
Sent from my Photon via XDA
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.
Hey all,
I have been unable to update my sister's bolt to ICS since it started rolling out a couple days ago. The phone is stock rooted with S-on and has an unlocked 1.05 hboot. I have done nothing to the phone except debloat. The recovery is stock. When I go to settings/software update and select check new, it appears as if it checks for a couple seconds but the popup saying whether or not it has new software to download never appears. I know with the galaxy nexus I was able to force pull the update by clearing the data for settings and turning airplane mode on and off of something ridiculous like that. Is there anything I can do with the bolt to get this thing to update? When I gave my sis the phone I tried to set it up so it could take the big ics update once it arrived (back in September ) so this is bothering me that the phone won't update.
Thanks for any help.
The reason is because you debloated. The update requires that ALL stock apps be on the phone at the time of the update. If they aren't there it will fail. If I were you I would get s off and flash the ics that Santod posted in the dev section.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The reason is because you debloated. The update requires that ALL stock apps be on the phone at the time of the update. If they aren't there it will fail. If I were you I would get s off and flash the ics that Santod posted in the dev section.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Oops. Bloatware interferes even when it's gone. Figures. Yeah I'll probably just go the S-off route and do it the better way.
efffin' verizon.