Related
My hubby's been having an issues on his mobile that I've never seen before.
Issue 1: His phone would randomly go back to sleep upon waking.
Sometimes this happens while we're just waking the phone and sliding the lockscreen. So it's like the phone is asleep, we hit power, slide the lockscreen - phone immediately goes back to sleep.
Issue 2: Call issues.
I'm not sure if this is subject to software or not but sometimes this phone will not ring when receiving calls. The problem is a bit intermittent but it's still quite annoying.
Issue 3: OS slowing down.
Generally, his phone runs fine in terms of speed but at other times, it can be slow as molasses. The sad part is that his phone has the smaller SD card and the least amount of media in between the 2 of us.
I would just root and flash something on it but it is his phone and he isn't really that comfortable with the idea of messing around with the firmware and such. So I guess my question is does anyone have any advice on how to fix these issues?
I'm not sure if this will work but your best bet is to Odin the stock JFD again to see if it fixes anything. Be sure to back up apps & data.
Wayne561 said:
I'm not sure if this will work but your best bet is to Odin the stock JFD again to see if it fixes anything. Be sure to back up apps & data.
Click to expand...
Click to collapse
If the OP doesn't want to mess around with the phone that much, flashing something through Odin is probably more complicated than rooting the phone (takes one click) and trying One Click LagFix (OCLF).
No matter what you do (to the OP) make sure you use Titanium to backup apps and data just in case
wearmaize said:
If the OP doesn't want to mess around with the phone that much, flashing something through Odin is probably more complicated than rooting the phone (takes one click) and trying One Click LagFix (OCLF).
No matter what you do (to the OP) make sure you use Titanium to backup apps and data just in case
Click to expand...
Click to collapse
Well, it isn't my phone to mess with in the first place, otherwise that thing would be on a Bionix-V ROM like mine is. Even today, the stupid phone crashed and he lost his unlock. It was by pure luck I retained the code we got from T-mobile.
Update it via Kies to KA6, KA6 runs pretty well. Enable USB Debug, and it should go without a hitch.
Root it.
Install rom manager
Load rom manager
clear dalvik cache
Uninstall rom manager
unroot it
t1n0m3n said:
Root it.
Install rom manager
Load rom manager
clear dalvik cache
Uninstall rom manager
unroot it
Click to expand...
Click to collapse
Yeah, I think I'll do this first and see how it runs for the next few days.
Just one q: When I uninstall ROM manager, will CWR also be wiped at the same time or will I also have to find another way to uninstall it?
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
First off, wrong section... should be in Q&A.
One way to fix it was to get SetCPU, and make sure the minimum CPU speed is 200MHz
You should also give more information. Have you flashed eb01 with odin before installing SC? How often do these sod's happen? Do you use the clock app?
Sent from my SCH-I500 using XDA App
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
GizmoDroid said:
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
If you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package ROM from this post
While reinserting your battery, hold both the volume keys and the power button down until a second after you see the Samsung boot logo
You should see CWM recovery now
Flash the SuperClean ROM from this post, Wipe Cache/Dalvik Cache only.
Reboot. If you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot, enter CWM and flash theme, Wipe Cache/Dalvik Cache only.
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
Click to expand...
Click to collapse
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
str8havoc said:
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Are you running setcpu ? And if u are and u have a profile for when the screen is off, disable it. That should to the trick
Sent From My Samsung Galaxy S Fascinate Using XDA Premium App - Running Superclean 2.9.1 - 2.2 Froyo
sneakysolidbake said:
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Thacallmehess said:
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Click to expand...
Click to collapse
Your post isn't helpful to the forum at all, at least there's some community members who like to help keep our forums organized and clean so our Mods aren't overwhelmed. (See how easy that was)
@ OP, there is definitely a SOD patch somewhere in the Fascinate forums that Adrynalyne put out a bit back. I apply it along with the Camera mod every time I flash any new version of Superclean based on EB01/EB16. I'll see if I can post a mirror later when I get back home and you still haven't found it.
The SOD patch is already incorporated in to the latest SC. Gizmodroid's process (based on Adryn's solution to problems with SC2.7 iirc) is your best bet at this stage and worked for me. I would also recommend avoiding TiB as much as possible based on Adryn's comments in the SC2.9.2 thread. If you use Gizmodroid's process, please post your results in the relevant thread. I'd be interested in finding out the degree to which that process solves the issues generally.
I had the same problem. Follow the directions above flashing the stock and then upgrading and avoiding the apps noted above (I think youmail was a big part of my problem) and you should be good to go.
GizmoDroid said:
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
Click to expand...
Click to collapse
Thanks everyone for the fast replies even the one telling me i was in the wrong section. Sorry about that
I use both Youmail and the clock app all the time, so thats probbealy why i'm getting the SOD. I also install my apps from my SD card using Astro File Manager and it sounds like that could be causing my problem to.
I installed SetCPU and set the min. to 200mhz, hope that will fix my problems if not
Q1: can I download another clock app and be ok or will it do the same thing
Q2: is there any way of fixing the Youmail app or should I use another voice mail app.
Just want to thank everyone that keeps XDA up and running you guys rock. Love this Forum!
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
mrjake1970 said:
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Click to expand...
Click to collapse
Are you using the voodoo lag fix?
I think the majority of the incompatibility people are seeing with the fixed cwm is might be some broken compatibility with rfs. It's supposed to be able to handle both, but I think changes in jt's initramfs or changes in the project voodoo files in the kernel that CWM is put into are the root of the problem.
Maybe I'll get some time this weekend to look at it.
In the meantime, everyone should go voodoo/lagfix
yeah giz, im using the superclean "stock" voodoo...
r
tonight im going to go flash happy with the original odin file i used to bump to froyo, and the other old cwm with the broken fixpms and the non fixed superclean 2.9.2 and see if that helps.
i cant be late for work again tomorrow with no alarm from a frozen phone lol
Samsung Fascinate
SuperClean 2.9.2 Voodoo
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
What is the sleep of death?
Update...
I reflashed the original EB01 tar file, modem and the 3/30 red CWM, along with the original copy of the non-fixed superclean 2.9.2 ROM and i am running fine so far with no SOD issues.
As long as this holds true for the remainder of the day I'm going to flash the updated CWM tonight to try and narrow down which of the 3 things i suspect in my previous post is causing it.
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
I downloaded setcpu and put it to 200mhz and been running fine since yesterday. I hope it will last the rest of the day.
Sent from my SCH-I500 using Tapatalk
created a sleep of death..
so, guess what? i created the sleep of death on my phone, and i know exactly what caused it.. not only that, but remembering back to my last sleep of death experience - it was the same exact scenerio..
i was running EC10 debloated, jt's 4/8 voodoo.. i flashed a theme to check it out.. didnt like it, so i re-flashed EC10 over it, with wiping dalvik and reg cache..
booted fine, however i started to notice clock lag almost immediately.. screen went off, and next time i tried to open the phone, i had to hit the power key 4 times before it would light up.. sounded familiar to me from last time, so i let it go about 1.5 hours.. sure enough, would not wake up.. had to pull battery to get it to boot..
i did a nandroid back to prior to the theme flash, and seem to be running ok.. however i am going to do the "clean" flash again tomorrow back to EB01 again just to be sure..
im convinced that is what caused mine both times..i will also be doing that every time i get tired of a theme instead of just flashing a new ROM..im guessing themes are leaving pieces parts behind somewhere that don't play nice with a ROM reflash over it..
I have been having SOD issues ever since I rooted and got set up on SC 2.9.2. However today, I decided to leave my GPS on and since I did that I have not had any SOD. Granted today is not a perfect example because not 45 minutes went by without using my phone, but it seems to have made things better for now, except my battery drains because of it.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/foru...21-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I'm running
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
I did TiB but have since uninstalled and used My Backup (free). I'm using GoLauncher and related apps. I do use YouMail and will not stop. I know its redundant but I installed the SOD patch too.
I'm going to try all the bandaid fixes first before re-flashing everything.
Search adrenalyne's threads. He had one with a sod patch.
Sent from my SCH-I500 using XDA App
Hi all, I don't think most Vibrant users worry about it (at least from what I've seen), but do you worry about losing your baseband/EFS partition/IMEI info when flashing?
For those of you who don't know or forgot, basically some flashes can result in a generic IMEI number and you SIM card would no longer be readable under any custom ROM. You would then have to ODIN to stock and stay there forever, as that is the only way your SIM would be readable.
I know this was a problem a while ago when CM7 or MIUI was flashed, but is it even worth worrying about anymore?
Hopefully someone can inform me and others about the issue. Thank you for your time!
I'm not cause I got my efs backed up. Plus AOSP ROMS are no longer tedious to flash..just flash like any other rom. Though odining back to stock is the only way to leave AOSP I don't really care.
Sent from my T959 using XDA App
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
awebster said:
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
Click to expand...
Click to collapse
Yea...there are three for us VIbrant Owners...
You need to Odin back to stock w/ repartition checked if you want to go back to Sammy based roms coming MIUI and any other CM7 based ROMs.
That's great to know, thanks so much for the info laylovj.
Anyone else?
I think i backed up my efs at some point but i dont worry about it too much... at one point, flashing kernels in gb, i lost.my baseband i had 'no imei' according to my phone... i odined to stock and now im back on cm7 texting 24/7 so idk
... itd prob be aa good idea to have a backup
Sent from a cell tower to the XDA server to you.
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
TheSneakerWhore said:
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
Click to expand...
Click to collapse
I couldn't stand it if I lost my IMEI and was stuck on a stock, Touchwiz ROM. That's the only reason I worry.
younix258, I do have a backup of my EFS folder, but I guess ODINing to stock will also fix the problem like it did for you. Good to know.
Sent from my SGH-T959
I lost my IMEI a long time ago while flashing an unlocker or maybe CM7. I have this generic IMEI that has been working every since though with all the ROMs. Even Tmobile can't identified what phone I am using but they haven't shut down my service probably because I am paying $200 a month on 3 lines,.
Hmm, I wonder how often that's the case though.
From http://forum.xda-developers.com/showthread.php?t=859914,
"In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC"
So I'd definitely like to avoid losing my IMEI, even if everything seems to be fine without it.
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Try fixing permissions in CWM first and see if that helps.
Sent from my SGH-T959 using xda premium
Fix permissions worked for a while, but not anymore. Everything's force closing again. Will the journaling fix help?
Anybody have any ideas? Gonna wipe then install a newer ROM, but I want to make sure this doesn't happen again.
Only titanium the "necessary" apps that you wanna keep your data from. Then uninstall it - often I find that this helps for some odd reason.
Sent from my SGH-T959 using xda premium
chairhome said:
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Click to expand...
Click to collapse
Get into recovery:
wipe dalvik
wipe cache
fix permissions
reboot
wait 10 mins reboot into recovery again
fix permissions
reboot
open rom manager [worth its weight in gold!]
fix permissions
reboot
Thats what I did with my cm7.1.0.1 but I also installed eugenes streamline 110411 ver and [knock on wood] havnt had any more issues with fc's.
And yes even if you follow the installs to a "T" some of us still have the FC issue!
Good luck!
3 weeks later and I'm back to square one. I'll try the above, if it doesn't work, i'll have to wipe and reinstall. thanks. What's eugene's streamline?
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Sugartibbs said:
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Click to expand...
Click to collapse
MIUI's launcher. I'll probably try flashing to stock soon. :-(
No go. I'll have to look into Eugene's streamlined 110411
ok just for future sake, 3 rule's of flashing,
it's better to reinstall your applications manually then to trust titanium when bouncing between roms with different frameworks, versions, partitions, etc.
always flash from stock unless your updating a weekly rom ie cm7/miui
after flashing power off screen and have a cup of coffee/beer/shower. give the OS time to do all it's background configurations and setup.
now if you follow those 3 rules you "should" have no real issues.
I bought device in Europe with German Vodafone 2.3.4/4.5.2A rom.
I get reboots with all roms i tried as well as all custom kernels i tried while these all stuff work on other peoples devices with no issues whatsoever..
Before flashing rom i wipe device with moto-fastboot and cwm like anyone else who is familiarized with the procedure.
I follow all instructions and all but somehow i end up with issues not many people have.
What the hell doing wrong if anything at all?
well this is the wrong section to post in, but have you tried factory resetting from the phone?
Wrong section. It might be that your CPU is getting very hot, so it keeps rebooting.
Tried factory reset off course but i don't have any single issue with stock software. Just with custom ROM's and kernels i want to play with.
Also, I haven't noticed it gets hot that much.
how come it doesn't get hot and reboot that much to other people?
What problems beside the reboots?
Sent from my MB860 using Tapatalk
@schwarzlichtkind, something like widgets missing after reboots, display staying turned on (when talking) when it needs to turn off.. annoying stuff like that..
Which CWM are you using?
Sent from my MB860 using XDA App
when you install a rom do u wipe data, cache, and dalvik cache before flashing the rom?
then do you fix permissions after flashing?
i recommend you do this when you flash a NEW rom, if you are installing an update just wipe cache and dalvik before flashing, then fix permissions after.
latest romracers..i always tend to run latest software, hence the topic
I'm having a similar issue since I got my phone back from repair, no matter what I do faux's kernel 0.2.2 and 0.2.3 cause random reboots and the phone not turning on and heating up. So far 0.2.1 hasn't caused me any problems, hopefully 0.2.1 fixes this and 0.2.4 (in the future) doesn't give problems.
First of all, please post question on the Q&A forum, not on the Android Development one.
Second, please organize your things before asking, and ask a serious question to get a useful answer. Based on your question, 90% of the answers will be guesses.
I reccomend you pick a ROM you like, try it without any custom kernels for a while and see if you get the same reboots. If so, then post a question on the appropriate ROM's discussion thread, don't create a new one just because.
Edit: Post reported btw
Sent from my MB860 using xda premium
Are you sure you fully wiped? data cache and dalvik? if you did you can try using rom manger and official CWM
everytime a flash a rom i use this tool without fail. option 10. then i do the appropriate wipe in recovery. have never had a bad flash. i am anal like that. : )
http://forum.xda-developers.com/showthread.php?t=1314607
I have problems with faux's latest kernels also. Just stick to the stock cm7/blur/MIUI kernels and you should be fine.
Sent from my MB860 using XDA App
try under volting using setcpu. i too had this random reboot issue. but did an undervolt of 100mV (for 1.45GHz). i use faux's 1.45ghz kernel v2.3
have fun!
a possible radio issue i think...
Which radio works better? I have N_01.100.00R