I flashed Trigger 3.0 when it first came out, I was so happy with the rom that I took a abreak from flashing different roms. A week ago I started to get some force closes and they became a bit more frequent. Over the past couple of days I have been looking for a new rom to run. I started with Explodingboy's Simply Honey 3.6, then tried Simply Honey v1.0XE and Heathen's Private stock 2.0. Each time I flashed a rom I came started by odin-ing to JDF first.
With all of the roms I got the same problem, which leads me to thing it's hardware based rather than the roms. I would flash the rom, the rom would work fine for a few hrs then the phone would freeze while asleep. The only way to wake the phone was to do a battery pull. This sleep freeze would happen 30-40% of the time the phone would go to sleep.
I'm going to try to flash a 2.2 rom and see if my phone does any better, the others were 2.3.3 or 2.2.1
What kernel are you running?
Hardware takes quite a bit of abuse to deteriorate. In fact, most "hardware parts" will just simply die, not slowly deteriorate.
Sdobron said:
What kernel are you running?
Click to expand...
Click to collapse
With Trigger 3.0 I was running overstock OC/OV, with no problems for many weeks.
Once I started looking for a new rom, a few days ago, I always used the default kernel.
Do you mean ODIN to JDK?
Thats the stock base for Vibrant.
Side note: I have been unable to use my screen while device is plugged in, to dosent make the right touches and bounces around the screen...I was thinking I needed to ODIN to JDK, so I did... nothing changed, now I'm thinking I might need to get a new phone... #FYI
Thats actually pretty interesting. For awhile I had the same problem it just wasn't as frequent as yours. I'm using the Overstock kernel which I think it was what mine was related to. I had my sleep profile in setCPU set really low, I bumped it up and havn't had any problems since.
studiozeroseven said:
Do you mean ODIN to JDK?
Thats the stock base for Vibrant.
Side note: I have been unable to use my screen while device is plugged in, to dosent make the right touches and bounces around the screen...I was thinking I needed to ODIN to JDK, so I did... nothing changed, now I'm thinking I might need to get a new phone... #FYI
Click to expand...
Click to collapse
Actually the phone ships with JFD, so your wrong haha. xD
Longcat14 said:
Actually the phone ships with JFD, so your wrong haha. xD
Click to expand...
Click to collapse
Java Development Kit
To the OP, maybe you've restored some corrupt titanium data. Only restore apps and no system data after a fresh flash and see what happens.
How about u coding to stock and leave it alone see if u have same problem if not then its not hardware related
Sent from my SGH-T959 using XDA Premium App
hotadef said:
How about u coding to stock and leave it alone see if u have same problem if not then its not hardware related
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
I second this. Go back to stock, and see what happens. Also, do NOT restore any backups at all, leave everything clean.
Also you can try and use System Panel, and see wich apps are running in the background, and then Titanium Backup to freeze app by app (not system apps of course) and see if any of these are causing you the FCs.
Hey all thanks for all the responses. I was reading them all yesterday but did not want to reply and jinx my trigger 3.2 flash. I've now been running trigger 3.2 for close to a day and no FCs.
I can say I did anything different with this flash to make it more stable. I went back to JFD via odin and use Ti to restore user apps and system apps (ONLY: wifi, bluetooth, user dictionary, and MMS)
thanks again for everyones help.
Glad to hear it is worked out.
Related
Ever since I flashed EB01 I have been having problems with screen responsiveness, It will seem to work fine then after awhile will work selectively.
When I had voodoo installed, it started to do it I was running superclean 2.4
I flashed today back to EB01 Stock rooted non-voodoo, was still seeing it after awhile.
I also just flashed MIUI to play with today, and still am seeing it.
Baseband. EB01
Kernel: 2.6.32.9 [email protected] #1
I have the same problem, with any ROM that is not an official ROM from Verizon. It seems to be happening as soon as I root it. It is intermittent and locking and then unlocking the screen fixes it.
Sent from my froyo'd Fascinate
Mine works fine.
glenniosaurus said:
Ever since I flashed EB01 I have been having problems with screen responsiveness, It will seem to work fine then after awhile will work selectively.
When I had voodoo installed, it started to do it I was running superclean 2.4
I flashed today back to EB01 Stock rooted non-voodoo, was still seeing it after awhile.
I also just flashed MIUI to play with today, and still am seeing it.
Baseband. EB01
Kernel: 2.6.32.9 [email protected] #1
Click to expand...
Click to collapse
First...post questions in general. Second did you wipe data prior to instal?
dalrym05 said:
Mine works fine.
Click to expand...
Click to collapse
And what was the purpose of your response in this thread?
What launcher are you using? I had this problem and switched launchers from Zeam back to Launcher Pro, when I did that, all my lag issues with screen responsiveness were fixed.
jenisiz said:
And what was the purpose of your response in this thread?
Click to expand...
Click to collapse
Same as yours pointing his out. Seriously many people here need to take a chill pill. In all reality his did help as it shows that he does not have the problem. The more people that have the problem the bigger it is. This helps weed it out.
I had this problem last night trying to press the h key. I am running SC 2.4
Sent from my SCH-I500 using XDA App
happens to me also. I wonder why it dosnt happen to everyone??? And yes, i wiped and flashed.
Happens to me too. Seems to get worse with time. I was running superclean but flashed back to stock because the responsiveness got so bad my phone wasn't really usable. Happening again with debloated froyo too
It's happened to me on every Froyo ROM, even vanilla on occasion. It's probably just Samsung's ****ty kernel and so there's nothing much that can be done until there's source to work with.
Sent from my SCH-I500 using XDA App
I think I might have found a solution. I went into stock recovery and wiped cache. After a reboot I no longer have the responsiveness issues.
Edit: unfortunately I still have the unresponsiveness issues...seems it was temporary fix. Also, it is always the middle of my screen from top to bottom which becomes unresponsive. How about the rest of you guys?
Sent from my froyo'd Fascinate
cstrife999 said:
Same as yours pointing his out. Seriously many people here need to take a chill pill. In all reality his did help as it shows that he does not have the problem. The more people that have the problem the bigger it is. This helps weed it out.
Click to expand...
Click to collapse
His post contributed nothing as it provided no useful information to the op. He's looking for an ans...who cares if it worked for him. If that's the case we would have over a hundred posts pop up in here saying "mine works". If that's what you're going to say then at least provide some information the op cam use.
I too have been perplexed with this problem. Posted up in general but no solution has been found. I usually get so annoyed I go back to eclair for a while till I get ambitious enough to try again.
I will also point out that I loose all screen sensitivity when the charger is plugged in. Yes, stock charger and does not do this at all on eclair.
http://forum.xda-developers.com/showthread.php?t=957150
My phone and girls phone do this, mine is on sc2.4, hers is on sc2.2.
Its only slightly annoying at the moment for me, but she texts a lot and complains about the keyboard not working all the time.
The only unresponsiveness that I've noticed is that when I need to end a call, I find that I frequently have to tap "End" multiple times.
I'm also running Beautiful Widgets, so I assumed that that might have something to do with it.
Since BW requires an extra screen tap when coming out of a locked screen, I was assuming it was just a bug with the widget until I saw these posts.
Ok look if your useing set cpu and you set it to on demand your going to see lag but if you have this app and set it to conservative you will not have lag. If you are useing this app this will help you if thats your prob. If not them I suggest you DL'ed it to help your over all speed. I'm useing go launcher ex. Also as a side note I don't have any prob with my phone.
hmmmmmmmmm
calebv2 said:
Ok look if your useing set cpu and you set it to on demand your going to see lag but if you have this app and set it to conservative you will not have lag. If you are useing this app this will help you if thats your prob. If not them I suggest you DL'ed it to help your over all speed. I'm useing go launcher ex. Also as a side note I don't have any prob with my phone.
Click to expand...
Click to collapse
That's a great point. I never thought of that but I had also been noticing some lag while set cpu was set to on demand. Switched to conservative and did seem to notice a difference. Thanks.
I've always had SetCPU on conservative, 1GHz max and 200MHz min. Maybe I don't see it as much as you all say but it's enough for me to notice.
Sent from my SCH-I500 using XDA App
A week ago I Odin'd back to stock and upgraded to the official 2.2 VIA Kies Mini. I have not rooted since or really even restored any of my old apps. No mods, just a stock Vibrant now. While I was playing WordFeud the phone locked up for about 20 to 30 seconds then on the screen it stated a screenshot has been taken. I then checked the Gallery and sure enough there was a picture of the screen. My question is has anyone seen this or know what happened. I checked the WorFeud app help and it didn't mention anything about a screen capture feature. Is there some sort of button combination on the new 2.2 Release that allows for screen captures to be taken? I was pretty confused by this, please let me know your thoughts and/or experiences.
OK, I see others have encountered this too and I would of found that if I searched correctly, as in spell correctly. OK, I see that people are saying to hold the back button and hit the home or menu button. I have tried these methods and have yet to make it work again. Either way, since this is sort of covered already, without a clear answer though, MODS feel free to delete.
Crap, didn't see your thread.
I encountered the same thing today and it was pretty nice. Still trying to figure out how to do it. Its a nice feature!
I did it too....im not rooted at this time. Cant figure it out.....
Sent from my SGH-T959 using XDA App
Yeah I've done that too accidentally. Don't know how though.
Updating to Stock 2.2 from Kies is probably your first mistake, that ROM is so bad I couldn't stand it for more than a day. Flashed Trigger and reborn I was. Plan into getting a custom ROM for your phone because screenshots are not the only thing you will encounter annoying from Samsung's Froyo.
I ended up with screen shots in my gallery and I have no idea how they got there. There was never a notification or anything.
There is something built in, but I don't think the Vibrant really supports multitouch on the capacitive buttons. My girlfriend can do this on command, but only in the mms app. She clicks back, and when she feels a delayed haptic feedback, she pushes home and it works everytime.
Sent from my SGH-T959 using XDA App
Yes I have had the same thing happen, it definitely a timing thing I tried to master but only get 10% effective so I stay with shoot me,, just a weird glitch in the phone
roumenjr said:
Updating to Stock 2.2 from Kies is probably your first mistake, that ROM is so bad I couldn't stand it for more than a day. Flashed Trigger and reborn I was. Plan into getting a custom ROM for your phone because screenshots are not the only thing you will encounter annoying from Samsung's Froyo.
Click to expand...
Click to collapse
Yeah, I was rocking Macnut R14 for a while after trying a few others. I updated to Samsung 2.2 to test out because a friend was thinking of trying it and asked if I would try it first. I was bored of it within a hour I think but gave it a few days. Bionix and DOW Kernal on it now.
I updated the phone at tmobile because it wouldn't update from my computer at home. I was running stock j16 and now the phone has these problems, any help would be appreciated
gps no longer works wont lock and takes a long time to find sats thirty minutes or more. I cleared the caches and still no worky, worked fine on j16.
alarm clock wont work?
ringer will work and then not work?
Phone is lags and is glitchy, it has not froze like it did when new.
I am thinking about loading a rom on this phone as it is my third vibrant, and the other two had issues and this one worked fine with a little lag. and now it sucks as bad as the two that got returned. I did load a rom on one of them before I returned it and it kept freezing up to the point that I had to pull the battery.
any suggestions would be appreciated
I've heard of issues with phones that upgraded form 2.1 -> 2.2. My father's being one. He refuses to root his phone or install a custom ROM but he said that the Samsung GPS Restore app from the market helped him.
Not sure about the alarms or ringer issues. Make sure you go into settings and set the ringtone for each one again.
However, I would recommend installing a custom ROM. It will give you a fresh install (always good!) and more than likely a much faster/more enjoyable phone .
Root the phone and install a custom rom there is benefit using the stock.. If it is giving you problems just abandon and load something decent like, Axura, EDT, Trigger or Bionix
I was thinking of loading honey 2.4, but when I read all of the info on the roms, it gets confusing with all of the different kernals and lag fixes etc. I tried axura (I hope I spelled it right) and it was really buggy on the phone I sent back. It kept freezing and falling a sleep to where I had to pull the battery and re boot. I have been hesitant ever since. I use this phone a lot and really depend on it for business. My G1 was a lot mor dependable. lol.
Jusr root it and install a custom rom. Bionix-v 1.3.1 is great. And you cannot brick these phones unlesss your a complete idiot... phone is worth owning once a custom rom is on. Before that these things are grass
Sent from my SGH-T959 using XDA Premium App
I just read that a GingerBread ROM was leaked to the Galaxy S 4G. I also know that the Vibrant has slightly different GPS hardware than the other Galaxy S series phones, which is why Captivate ROMs had functional GPS long before the Vibrant.
However, if the Galaxy S 4G has the same GPS as the Vibrant, this could save the developers a lot of time and headache if they just rip off the drivers and lib files from this new leaked ROM. See this link: http://forum.xda-developers.com/showthread.php?t=1125747
Have you been asleep the last couple of days? Those files were already pulled and are working on gingerbread jvp ports.
Sent from my GT-I9000 using XDA Premium App
explodingboy70 said:
Have you been asleep the last couple of days? Those files were already pulled and are working on gingerbread jvp ports.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yep. It will be soon when GPS will work on 2.3 base.
I haven't been asleep, I just didn't realize that the GPS fix they were working on came from the Galaxy S 4G leak. I just found out about that leak today, and figured I'd try and make someones' life easier. I go through the Gingerbread ROMs every couple of days to check their progress, because as much as I want Gingerbread and working Netflix, I can't lose my GPS. Thanks for answering!
alright Thanks guys.
netflix does work already and its on the market
New_Guy777 said:
I haven't been asleep, I just didn't realize that the GPS fix they were working on came from the Galaxy S 4G leak. I just found out about that leak today, and figured I'd try and make someones' life easier. I go through the Gingerbread ROMs every couple of days to check their progress, because as much as I want Gingerbread and working Netflix, I can't lose my GPS. Thanks for answering!
Click to expand...
Click to collapse
I have been on Gingerbread Blitzkreig for 3 days now. Did the GPS fix and gettin quick lock. I am very pleased with this Rom
http://forum.xda-developers.com/showthread.php?t=1121862
Problem with Stepping Back...
lapdog101 said:
I have been on Gingerbread Blitzkreig for 3 days now. Did the GPS fix and gettin quick lock. I am very pleased with this Rom
http://forum.xda-developers.com/showthread.php?t=1121862
Click to expand...
Click to collapse
I, too, went with the Gingerbread Blitzkrieg today. Had to do the full smash since I was coming from a 2.2 ROM. Unfortunately, it seems to have killed my entire ability to do ADB. USB Debugging is activated, but plugging it into my computer doesn't allow me to "see" my phone, despite multiple reboots of both devices.
So far, everything is fine, but it keeps me from being able to use either ODIN or HEIMDALL.
I feel really vulnerable without these safety nets. I'd love to try again by flashing my Backup Restore in CWM, but I can't find anything that says whether or not that's safe when you have GB bootloaders and a GB Kernel...
*sigh* More Research.
Are you sure your computer can't see the phone when its in download mode? I would give it a shot.
Also a nandroid restore should work fine, but you'll have to flash a froyo kernel before or after the restore.
Got it...
mattb3 said:
Are you sure your computer can't see the phone when its in download mode? I would give it a shot.
Also a nandroid restore should work fine, but you'll have to flash a froyo kernel before or after the restore.
Click to expand...
Click to collapse
Yes, it wouldn't see it at all. Finally got it to work after about the 10 reboot. My computer finally did the whole installing Samsung Device Drivers (as if it hadn't done that 50 times). Probably just my computer, which is not entirely what I wish for...
Anyway, I'm going back because I need to have control of my camera, even at the end of the battery. I use it for tutoring, and I need to know I can use it until the very end.
Something will be worked out soon, though, I'm sure.
Thanks for the responses and the care, guys. You're all that makes XDA such a wonderful resource.
New_Guy777 said:
Yes, it wouldn't see it at all. Finally got it to work after about the 10 reboot. My computer finally did the whole installing Samsung Device Drivers (as if it hadn't done that 50 times). Probably just my computer, which is not entirely what I wish for...
Anyway, I'm going back because I need to have control of my camera, even at the end of the battery. I use it for tutoring, and I need to know I can use it until the very end.
Something will be worked out soon, though, I'm sure.
Thanks for the responses and the care, guys. You're all that makes XDA such a wonderful resource.
Click to expand...
Click to collapse
Had the same happen to me. Unplug, disable USB debugging, enable, plug back in. Voila.
Also, update 2 includes a hacked cam that will work below 15%
I've gotten real pissed at my phone, for rebooting 3-4 times in a row. By that I mean, once it boots back up, it reboots again. I have no clue what's causing this issue. I'm running the ViperS rom (the one that was took down), and the faux kernel (v23 b6, since v24 won't install in my recovery) with it. I'm thinking of flashing Stock RUU again, so everything can be 'out of the box' sort of. It might be an application I installed, I have absolutely no clue. I'm also thinking of un-rooting and rooting it again, so a fresh start. Do you guys have any tips/solutions that might help out my problem, before i go berserk?
hmm im pretty sure your rom wasn't flashed properly if your experiencing reboots... but why would you want to flash a rom that isn't being supported and then post problems lols... why not go with a current stable/nightly rom lol..?
Ninjistix said:
hmm im pretty sure your rom wasn't flashed properly if your experiencing reboots... but why would you want to flash a rom that isn't being supported and then post problems lols... why not go with a current stable/nightly rom lol..?
Click to expand...
Click to collapse
I always flash the superwipe zip right before i flash a rom, is that properly ?
and I flashed that rom because its the only one that catches my attention , but Eclipse's bulletproof is very similar to the ViperS rom, so I might try out that rom lol, and I'm more into Sense, TouchWiz, and stuff like that.
kevinrubio1 said:
I've gotten real pissed at my phone, for rebooting 3-4 times in a row. By that I mean, once it boots back up, it reboots again. I have no clue what's causing this issue. I'm running the ViperS rom (the one that was took down), and the faux kernel (v23 b6, since v24 won't install in my recovery) with it. I'm thinking of flashing Stock RUU again, so everything can be 'out of the box' sort of. It might be an application I installed, I have absolutely no clue. I'm also thinking of un-rooting and rooting it again, so a fresh start. Do you guys have any tips/solutions that might help out my problem, before i go berserk?
Click to expand...
Click to collapse
i dont think its the rom, happens to me a lot as well, and i am on EnergyRom 8/1 stock kernel.
then why not just run stock.. thats as close to sense as your going to get .. or android revolution hd
xXchrizhurtyXx said:
i dont think its the rom, happens to me a lot as well, and i am on EnergyRom 8/1 stock kernel.
Click to expand...
Click to collapse
thank god, I'm not the only one
Ninjistix said:
then why not just run stock.. thats as close to sense as your going to get .. or android revolution hd
Click to expand...
Click to collapse
stock is a bit slower lol
I think its the kernel... Reflash the viper s Rom without wiping and it will put the correct kernel in place. Also are you overclocked or underclocked? Those could be problems.too
Sent from my epic amaze 4g
ziggy46 said:
I think its the kernel... Reflash the viper s Rom without wiping and it will put the correct kernel in place. Also are you overclocked or underclocked? Those could be problems.too
Sent from my epic amaze 4g
Click to expand...
Click to collapse
I'm not sure which one I am, I dont have system tuner or setCPU installed so the settings are whatever v24 faux kernel is.
UPDATE: Its not the kernel, because i tried it on eclipse rom and i still had the same problem
This is a total pain in the ass, my phone reboots upwards of 10 times a day, and with the Amaze's unamazing boot time, it really sucks.
I've tried everything. Stock RUU's, Custom Rom/Kernels. Everything. Nothing is working.
First I tried overheating tests. I wrapped the phone in blankets and ran a couple benchmarks with things running in the background. No fail.
Next I tried a discharge test. Charged to 100, let the phone sit idle while logcat was running, found nothing.
I've ran memtests = nada, no reboot
HOWEVER, I found that if you have only the Amaze on you, and you are on a lunch break waiting to pay for food and you need to make a transfer, the phone will crash.
I've used logcat and tried to capture what is happening, and all it shows is a cutoff, nothing happens, the battery just dies.
Something is messed up with the hardware itself, or the batteries, although I've never heard of the Dopods or Sensations (They use the same batteries) dying like this, so I don't know.
This is my second Amaze, by the way. My sister has the same problem, she is running stock.
My results: The Amaze is a ****, and all it wants to do is waste my time.
steamdnt said:
This is a total pain in the ass, my phone reboots upwards of 10 times a day, and with the Amaze's unamazing boot time, it really sucks.
.
Click to expand...
Click to collapse
That happens to me and i so agree with you! it really does suck but i have a update for everyone.
UPDATE: I see the reboots happening after my battery pasts the 40 percent, could this be a clue to a solution?
For some odd reason, batteries going bad has been a very common issue with the amaze. That could very well be the source of your problem. There has been a few people here in the forums that have had multiple batteries go bad on them. Not sure if its something this phone does to them or what but ya that might be the prob
sent from my
NRGized amaze
powered by Faux
aj_2423 said:
For some odd reason, batteries going bad has been a very common issue with the amaze. That could very well be the source of your problem. There has been a few people here in the forums that have had multiple batteries go bad on them. Not sure if its something this phone does to them or what but ya that might be the prob
sent from my
NRGized amaze
powered by Faux
Click to expand...
Click to collapse
Do you recommend me to get a battery thats not stock? or just get a replacement stock battery?