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
Related
Hi guys,
I am new to the XDA forums so forgive me if this is really stupid or if someone has posted the same problems. I searched for an answer but couldn't seem to find someone with my problem. Forgive me if this is long. I just want to make sure you guys know all the details so we can figure out what went wrong.
I recently flashed the Evil Fascination 3.6 Rom from a modified stock version of ED04 (debloated/debinged). I believe that my version of CWM recovery was 2.5.1 or something like that (w/ voodoo lagfix). I am pretty new to the Android world but I do believe I did everything correctly. I wiped Cache and Dalvik Cache and Data multiple times and made nandroid backups etc.
I flashed the Rom with no problems and everything worked just fine. I was trying out Regina 3D launcher at the time (I regularly use Launcher Pro), and for some reason it seemed a little slow to load up (I figured it had to do with it being the first time with the new rom). I kept having loadup problems with the launcher so I uninstalled it and went back to Launcher Pro. Launcher Pro even seemed like it was acting weird but I didn't take much notice to it.
Now yesterday I downloaded the OTB 1.6 Touchwiz kernel. Everything I've read said it was compatable with Evil Fascination. I tried to flash it from CWM recovery and it didn't work. My phone stayed stuck on the Evil Fascination boot up screen and finally I just popped the battery out. I went back into CWM and just wiped everything and reflashed Evil Fascination. It seemed to work fine with Launcher Pro (again a little glitchy at times, but I took no notice really).
I again tried to flash the OTB 1.6 kernel. This time instead of doing it from the recovery I downloaded an app called SGS kernel flasher. I did what it said and it flashed the kernel for me with no boot up problems like CWM did. I rebooted and then booted into CWM to check it and it was changed from version 2.5.1 (voodoo) to 3.2.0.0.otb. I figured this meant that the kernel flash was sucessful. I went to reboot my phone and when the home screen came on it was a froyo style launcher with only 2 or three icons on the page. I pressed the app drawer and none of my apps showed up that were on my sd card. finally i pressed the home button and it asked for which launcher to choose : LauncherPro or the default and I chose LauncherPro. My regular setup appeared and my apps were in the app drawer. I found it weird that my apps showed in LauncherPro but not in the default launcher.
Now with doing phone reboots my phone always goes to the default launcher with no apps from my sd card and I have to wait to press the home button for LauncherPro to appear. I set it as my default launcher but it never loads when my phone is rebooted.
I was just recently (within the last hour) doing regular things on my phone (texting, internet , email etc) ad all of a sudden I got the shut down boot animation from my rom and my phone turned off. I went to turn it back on and my phone stayed stuck on the boot screen again. Now you can figure what I did again. I went through and did everything over and reloaded the rom and kernel. I am still having the same problems with the launcher as I did before and I have no idea whats going on. I just want to avoid going through this again. Anyone have any idea what the heck is going on???
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
I'm also no expert but after running into constant force closes and random problems with launcherpro I decided to go with go launcher and its been a great switch for me.
Sent from my SCH-I500 using XDA Premium App
Hey guys, still no luck. I don't know what it is. I wish I knew more about hacking and doing all this kind of stuff
Try flashing a PBJ kernel!
can you get into CWM with the three finger salute?
[hold down the two volume buttons and the power until your phone reboots and you see samsung then let go]
See if you can mount as usb to get the kernel on there, if that doesnt work go to staples get a microsd card reader [under $15] and toss the pbj on your card then flash that.
When i was on EF and Comm Rom my phone didnt like the OTB kernels
Good Luck!
My recovery menu works fine and I can boot into it from the ROM without problem. My problem is that when I reboot the phone the ROM's default launcher is setup (and it is missing all of my apps) even though I set Launcher Pro as my default. I have to reset all my defaults in Launcher Pro every time my phone is turned off or rebooted. I would be on PB&J but I like to overclock my phone and PB&J doesn't support voltage control and I don't want to pay for and overclocking app.
efan450 said:
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
From what I've read many people have disagreements on whether 2.5 supports Edify or not....because a lot of people have success with it while others don't so I really don't know. Its never given me problems in the past. I actually had more problems with 3.X recoveries (It wouldn't allow me to make nandroid backups and other things that were essential) so I flashed 2.5 and it worked perfect (again I've read about people having the same problems with 3.0 versions of CWM).
Okay what I've found is that this has nothing to do with Launcher Pro. I downloaded He Launcher and when I reboot my phone everytime it asks me to pick a default launcher. And when I'm using He Launcher, none of the apps on my SD card show up in the app drawer (they don't show up in the default ROM launcher either, they only show up in launcher pro)
Efan450 I tried what you said and it worked! I odined a 3.X recovery and wiped everything oof my phone then flashed the ROM and kernel and everything is working perfectly now. Thank you very much!!!
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
lexx210 said:
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
Click to expand...
Click to collapse
Fix permissions with Rom Manager, or in CWM under advanced, then set up your widgets again. You shouldn't have problems after doing that.
I Also noticed in ADW if I installed a backup configuration within ADW I ran into this problem. If I loaded my widgets after re-loading ADW I did not run into this problem. Caelan's post is also spot on!
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
lexx210 said:
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
Click to expand...
Click to collapse
Fix permissions, reboot, then set up widgets again if you lose them. You shouldn't have any more problems unless you flash another ROM, and possibly another kernel.
Then just do the same thing again if you happen to do that.
This is probably stupid, but you don't have the Widgets installed on the sdcard do ya?
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
lexx210 said:
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
Click to expand...
Click to collapse
Same problem here and only after faux's kernel...I tried all the fixes (fix permissions, wipe cache first before flashing kernel) and the only the thing that worked is to go back to the stock kernel.
Oh man, you may be on to something because EVERYTHING was working fine before last night when I flashed faux123's OC kernel. I'm gonna try and go back to stock and see. Thanks man!
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Swiftks said:
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ok perfect then I'll just wait for his next version and hope that fixes the problem. I need his kernel to flash ROM's since I'm on a international phone. It's weird saying that since I'm just in Canada...
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
No problem man....yeah I've made some comments on the the kernel thread about the issue. Hopefully it gets fixed in an updated version.
in the kernel thread (dev) faux is asking INTL users about this issue, for INTL users on his 1.6 unified kernel. some report the widget issue, others do not. its the kernel causing. I am using unified OC 1.6 kernel and am lucky enough to have no issues, and WAY better batter life then stock kernel.
I also encountered this issue, however I don't have an international version of the Atrix.
Using 2.3.4 (pudding version for AT&T) with Alien ROM #4 and faux123's 1.6unified kernel.
Also using Launcher Pro.... I just reinstalled everything after doing a hard reset to try and isolate the problem, and it did occur after the kernel flash.
Same problem here, luckily I just reboot my phone few time a month..(why do I need a reboot, anyways?)
The widget is left blank white with Problem loading widget warning..
I'm not using an INT Atrix, only AT&T (I don't know if there's any other Atrix version) using faux123 1.6, piecrust, romracer cwm ..
any luck, guys?
would there be an update of 1.8 of faux?
I think I'm going partially nuts over this problem. I have tried every thing mentioned in any post. Fix permissions with different CWM's.
I thought was going to win today today when I formatted everything, installed gobstopper 2.3.4 w/ deodex update then setting up my screens with ADW it glitched and would go to the screen preview whenever I touched the screen. a reboot and those damn black boxes are all over the place.
Order of operations:
- format internal/external
- factory reset
- fastboot flashed tenfars CWM which wouldn't mount the internal sd so I couldn't flash
- fastboot erase/flash romracers CWM
- installed Gobstopper 2.3.4
- reboot and used it for an hour or so to let it level out
- installed the deodex update
- reboot and another hour of use with a bunch of reboots to make sure everything was cool (it was)
- used Diviances EXT4 User Journal script
- used it for a few more hours without issue
- installed ADW Ex and while setting up my screens it glitches and goes to the screen preview with every touch.
- reboot... no widgets with a string of expletives
so now what...
Same problem here. I am using latest Aura Rom with latest faux Kernel for International users.
I did everything: Wiped cache, reseted factory, installed rom again, changed kernel to older versions, stock versions, fixed permissions and always lose my widgets configs after a reboot.
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.
To allow Q&A to be separated from bugs/development - this is the Q&A thread for the I9100 Hellraiser found at http://forum.xda-developers.com/showthread.php?t=1335377
I intend to put FAQs here, along with keeping a list of tested ROMs. Keep general discussion here, and only use the other thread for bug reports and development.
In general: If it's listed as a known issue, and you don't have a fix, keep it out of the development thread. If you're not sure if it's Hellraiser-specific and common to multiple ROMs, keep it out of the development thread. In short, if you ask "Is this a bug?" in that thread, I will report it to the moderators. If you report a bug that is ROM-specific and not a Hellraiser issue, I will report those to the moderators starting tomorrow.
Tested ROMs:
I9100 XXKI3 Based:
SensatioN 1.8 by Crysis21 - Tested by myself with Alpha 0.2.1 - Fully working except 0.2.1 Known Issues, defaults to "good" AT&T APNs except for it has the "Broadband" APN which may cause the Tether Police to nail you if you tether. I suggest deleting that one.
VillainROM 3.0 + JKay Deluxe Themes v12 - Tested by myself with all versions, and my current "testbed"
I9100 XXKI4 Based:
CheckROM Revolution HD 2.0.0 - A few user reports indicate this may have WiFi issues when Hellraised similar to UCKJ2/J4 for I777
I9100 XWKJ2 Based:
CriskeloROM V30 + JKay Deluxe V12.1 - Reported by simpl3lang, seems to be working
If you have a report for a ROM, please indicate which I9100 firmware it is based on (XXKI3, XXKI4, etc.)
Also, I have seen reports that XWKK5 bases (like the latest CheckROM as of 1/8/2012) have the same issues with Bluetooth HID not working as UCKK6 - even when not Hellraised.
If someone posts a good, in-depth review of a ROM, I may link to it from this list. (Time permitting...)
Frequently Asked Questions:
Q: The home button lag is back, why?
A: The ROM has the annoying Vlingo double-tap support. Either smali it out (look for tips in the UnNamed ROM git repos, or look for a fix for that ROM.) - A commonly available fix may be flashing a JKay Deluxe Theme appropriate for the base of your ROM
Q: Home button haptic feedback is not working, why?
This is something that can't be "universally fixed" with Hellraiser. It must be modified in an individual manner for every ROM in android.policy.jar with some smali magic. It was the same deal with I9000 ROM ports to the Captivate.
Q: Where do I find themes/mods?
Look through the I9100 Themes/Apps forum for mods/themes appropriate to your ROM. Nothing I do in the Hellraising process should break any of these compatibility-wise.
i finally jumped on board and installed an i9100 rom. so far so good. im loving it. first install went smooth. root working and all. i dont know about battery life (my phone still plugged in while testing this out).
okay here is the rom ive installed "CriskeloRom V30-S-BAR-12/7-Tog-BLN-CallREC-Overscroll-7Locks-PWR-M-Esxt-(XWKJ2-2.3.5)"
http://forum.xda-developers.com/showthread.php?t=1168836
i have also installed JKAY DELUXE SETTINGS v12.1 <--great addon. lets you have multiple slide to unlock (AOSP lockscreen). option to remove home double tap. option to customize power options (extended). crt off/on animation. overscroll glow. all these options and more on this DELUXE SETTINGS app. http://forum.xda-developers.com/showthread.php?t=1154278
so far im loving it. this will be my rom for now. thanks ENTROPY for the great HELLRAISER.. you the man
edit: alright i have tried wifi tether. its not working. i know its mentioned in the known issues. the workaround doesnt seem to work for me at least ......i enabled changed ssid and password. but once i exit settings, it reverts back to borkness lol. any other workaround? thanks
Edit 2: nevermind i figured it out. I rmmbered i replaced the Settings.apk with one that has a theme i like. That borked wifi tether for me. I returned the settings apk i replaced, rebooted, and all is good
I just wanted to bump this to the top... this thread needs to be stickied! How do I ask a mod to sticky it?
Sent from my GT-I9100 using xda premium
Good question - I know in the Infuse section some ROM Q&As were stickied, but they don't do that in other forums.
Plus at least this is CLEARLY linked to from the main Hellraiser thread.
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
selfassembled said:
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
Click to expand...
Click to collapse
You must be doing something wrong... I am running 1.9 and have been since the test build.. I will post some screen shots in a moment
Sent from my GT-I9100 using xda premium
Here are some screen shots... check out my battery life ..
I did have it hooked to a computer while 1.9 downloaded and that's why you see that slight bump...
Sent from my GT-I9100 using xda premium
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
selfassembled said:
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
Click to expand...
Click to collapse
I had 1.8 flashed 1.9 on top without wipe.
Mounted system and data and then flashed hellraiser on top. And haven't had any issues.
Sent from my GT-I9100 using xda premium
An i9100 modem/kernel will NOT work, that's for sure.
In fact some of the behaviors you mention sound kind of like a classic example of accidentally running an I9100 modem. The rest sound like a classic example of not wiping or doing an improper TiBu restore.
I'll try to test tonight.
It may have been titanium backup, I also didn't remount before hell raising. I'll get it working if he did
Hi Entropy, do you have any idea why the tethering settings are not persistant?
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
amtrakcn said:
Hi Entropy, do you have any idea why the tethering settings are not persistant?
Click to expand...
Click to collapse
Not yet, haven't had time to mess with it yet.
selfassembled said:
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
Click to expand...
Click to collapse
Titanium backup always give me problems so I just don't use it anymore...
Have you tried a fresh install without titanium backup?
Sent from my SGH-I777 using xda premium
CheckROM RevolutionHD v3.1.1
I tried raisin' hell with CheckROM RevolutionHD 3.1.1 last night. This is an XWJK3 based ROM, and seemed to work fine. I was intrigued with the idea of having a kitchen in the ROM to customize it and wanted to check it out. Everything seemed to run and work ok. Home button lag and lack of haptic feedback were known and expected. There were a couple of things though -
1) The phone ran really hot. Like skin singeing hot. There was another post on the CheckROM thread that talked about the phone running hot. But I noticed the same problem with a hellraised VillainROM as well. So not sure if that is a hellraiser issue or a ROM specific issue. I do know about the media scanner crashing due to incompatible codecs between Samsung derived ROMs and CM7/MIUI, I didn't get a chance to see if getting rid of my media would fix it because of issue 2...
2) The kitchen app while great in theory, isn't quite there in practice yet it seems like. I tried installing a few mods from the kitchen, but a lot of times downloads failed. I tried installing the BlueMonkey theme from the kitchen and it caused the phone to bootloop. There are quite a few people talking about bootloops on the ROM page, so I am leaning towards this being a ROM or kernel incompatibility issue. I have never had bootloops or anything nearly as funky with any of the native I777 ROMs. I had to flash back to bone stock to recover. Thank god for Nandroids
So, I guess it is ok to the add XWJK3 based ROMs to the compatible list if Entropy thinks both of the above two issues are not hellraiser related.
I've never had heat problems on VillainROM hellraised.
I've been starting to hear that CheckROM 3.1.1 has a lot of issues with the kitchen app - as in 3.1.1 has issues in general. I've seen lots of comments about people sticking with 2.0.0 until it matures.
I only tried CheckROM VERY briefly - enough to confirm that wifi worked (as there was a negative report on wifi with CR 2.0.0)
I'll update the list later this week.
GingerMod
Thank you for this awesome tool, Entropy! You can add GingerMod (http://forum.xda-developers.com/showthread.php?t=1220283) to your list of XXKI3 ROMs that work well Hellraised.
I've quickly tested out everything I can think of from a fresh install (wipe everything, format/system) and no problems to report. Wifi tethering has the minor problem of reverting to default settings, but they work, so it's not an issue in the slightest for me. Default APN settings are the same as on UnNamed--ATT Phone and ATT WAP. Home button haptic works out of the box--I didn't do anything.
For those interested, some quick hits about this great ROM:
- Most Samsungyness removed, really convincing AOSP feel. It's not just a theme, it's rebuilt. Just a few niceties such as Camera, Browser, FM Radio remain. You can add back whatever Samsung features you want.
- Small, 1/2 size compared to stock ROMs
- There is no lengthy screen on delay during calls when removing phone from your face (present in UnNamed)
- Customizable via included "Extras" settings and JKay app
- Been stable for awhile. Over at the thread, you won't notice a lot of random issues or people clamoring for "fixes". It's just really complete.
I'm not really sure where the issue really came from but I have a potential starting point. All was running well for sometime, phone has been getting slower and slower. I did a CwM backup, cache dump, factory reset, and restore. Titanium notification regarding SU build not up-to-date displayed and following a SU update/fix (3.1.1 ?) the phone locks up and nothing works... hard or soft buttons. I'll pull the battery and reboot. Attempting to access the phone, the lock screen appears but is unresponsive and once it closes the cycle begins again. I've searched the threads and haven't found any similar posts. Just wondering if possibly PWGB is incompatible with the latest SU?!?!
it shouldnt be...although I would odin back to stock eh03 then update to a newer rom! If your not a fan of aosp then give geewiz a shot.
I did try GeeWiz 2.9 just recently and this first happened after loading and updating. That was one of the reasons I went back to PWGB thinking it was something with GeeWiz. But since it is happening with PWGB, I'm not entirely sure what the issue is. I just know that after installing Titanium and updating the outdated SU binary, I get this error.
Ok- I used ODIN again to flash PWGB. I updated SU(chainDD) to v3.1.3 (binary 3.1.1), installed BusyBox(Stericson) v8.9.6 (BB v1.19.0) using the Smart Install. I downloaded Titanium and Root Checker, where both appear to be endlessly Asking for or Checking for Root access. I ran the CwM 2.5.1 fix permissions and that also did not seem to work. I feel that I'm closer to a working phone again, but it's still not there.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Binary 3.1.1 is breaking GB root on GeeWiz 2.9 and possibly any TouchWiz GB based ROMs. There's a fix for 2.9 in the OP of the GW 2.9 thread.
Sent from my SCH-I500 using xda app-developers app