Hey all,
I'm still a newbie, so I wasn't able to follow-up directly in the Das Bamf 1.5 Remix thread.
First off, awesome ROM and thanks for all your hard work. I love the recent apps replacement and battery enhancement.
However, I'm noticing that my phone has randomly shutdown a few times today. Does anyone have any insight on that?
Thanks
Are you overclocking? What kernel are you using?
Nope and I was running Adrynalyne's 4.4.2 experimental kernel (stock speeds), but I just downgraded to 4.3a.
In hindsight, maybe it was just a symptom of using the experimental kernel, however I didn't see the random shutdowns while using Bamf Remix 1.4.
Thanks for the quick response.
I had one as well... it happened only once so far. I'm running 4.4.2 kernel with the remix as well.
MoshingPanda said:
Nope and I was running Adrynalyne's 4.4.2 experimental kernel (stock speeds), but I just downgraded to 4.3a.
In hindsight, maybe it was just a symptom of using the experimental kernel, however I didn't see the random shutdowns while using Bamf Remix 1.4.
Thanks for the quick response.
Click to expand...
Click to collapse
Try running "fix permissions" in RM?
Sent from my ADR6400L using XDA App
I've have had no reboot, wiped all on install, oc at 1200+ on smartASS gov.....
Sent by my ThumperBolt
Thanks for the comments I'm going to give a full wipe a try
If your going to use something other than 4.4.2 I strongly recommend 4.3c. Very stable OC kernel.
4Geezy ON DopeDiculous's ROOTED TBeezy!
Hi,
I just installed BAMF Remix 2 days ago, and I did a full wipe and am not running any different Kernel's other than what came with it. And I and getting random reboots and shutdowns.
Thoughts???
I ended up unrooting my phone to exchange it with Verizon for another reason. However after getting my new phone, I rooted it, flashed the radio RUU and then Das Bamf and haven't gotten any reboots since. A clean wipe seems to fix it.
ive never had a random reboot on this rom until this morning. been pretty stellar so far
Yeah, I had the Radio he recommended and wiped everything, followed all the instructions, and this has been the worst ROM to date for me. Im not one to enjoy Sense in the first place. I used it for about 48 hours, it was pretty sluggish, and titanium backup took about 3 hours, when it takes about 20 minutes on other Roms. I got the random shutdowns, where it would just turned off without notice. I fixed the Permissions and it just wouldnt turn around. So im back to boLTEd .35 and part time CM7 - alpha
Related
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
Ok so i've done just about everything i can think of to stop these reboots except ask and now i'm at that point.
I'm running:
das bamf remix 1.8 ROM
2.6.32.21_bamf_4.47 KERNEL
I used to use 1.7 and still had reboots, switch to bamf 2.1 for GB, and still had reboots, and have tried all 4 radio downloads from the obligatory radio thread. The reboots are truly random. I've had them while charging, idle, browsing web (went and downloaded another browser (which im thoroughly enjoying)) and using pandora.
So what's left at this point? I doubt it's the kernel, but i really don't know, and i want to download the control freak 2.1 kernel because i had it on 1.7 and loved the battery life.
Should i look for more updated radio downloads or just wait and see what happens with verizon?
Go back to stock, call Verizon and get a refurb. Then start new from there. If you have done that much already it may be a hardware problem.
I see. I have a warranty on mine, i can probably take it back to the store. I made a backup of my phone just after i finished rooting, if i wanted to go this route should i just flash that backup and unroot? Or just install the stock rom, kernel and radio?
Follow this
http://forum.xda-developers.com/showthread.php?t=1009423
thank you for that
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
What gingerbread roms have you tried? Also, what kernels were you using?
Sent from my ADR6400L using Tapatalk
don't have this issue on Synergy 3.0 running the latest ziggy kernel
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
I would try wiping, then installing the setup in my signature, but don't restore any apps at first or sync with Google so they're downloaded automatically. I think that you've got an app and a kernel that's interfering with one another. Try the ROM bone stock before you start restoring apps and see if the problem is there.
Rooted Thunderbolt on BAMF Sense 3.0 RC 4 with MR2 radio and latest dreamKernel.
Silentdawn3 said:
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
Click to expand...
Click to collapse
when you say both kernels are you referring to the radios? cause mr2 and mr.5 are radios not kernels
Silentdawn3 said:
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
Click to expand...
Click to collapse
I share your pain with this exact problem. I have been doing all types of testing these last two days to see if there is any combination of ROMS and Kernals that would work for me.
I can flash any ROM I want, and the only Kernal that I can successfully use is this one:
Imoseyan GB Stock Kernal
With this Kernal, I can use my phone all I want, let the screen go black, hit the lock screen button and I have never had a reboot.
I have run Thunderstick, BAMF 2.1, BAMF 3.0, Gingertheory, with this kernal and it will run fine.
When I change to any of these Kernals, I get the constant reboots when my screen goes off, just like the OP described.
* Imoseyon Lean Test
* Imoseyon 184mhz
* Imoseyon USBfix
* Imoseyon 2.5.3 test 7
* Nerozehl's dreamkernal 2.3.2
Of course, when flashing any ROMS and Kernal combinations, I would do a complete wipe before doing so. I should also mention that I am using MR2 radio. I can also use MR2.5 with the GB Stock Kernal and it runs fine.
So like the OP, it seems to be something to do with the kernal that my phone does not like and can't figure out. Anything other than the stock kernal, and my phone will constantaly reboot after the screen goes black.
I should also mention that I have used the speektweah.sh in terminal emulator and tried all of the different voltage settings and it had no effect. Also disabled it and tried using SetCPU and no luck either.
I have also tried all of the ROMS without allowing any apps to update by skipping the google account sign in. So basically all of the ROMS were running in their native state, and the outcome would be the same.
FOR THE OP
Try running the stock kernal and let us know if that works for you. You should just be able to flash it in CWM, reboot and you will know right away if it is working correctly.
The real question I need to figure out is this. What is different about the GB Stock Kernal from all the others that would be having this impact on our phones?
I've tried all of this except installing the above kernel. I'll give that a shot, thanks.
As for installing without apps, I've tried that. Tried everything. Lets hope the stock kernel works!
I've been running Das BAMF Gingerstripped with Imo's kernel and never had this issue. It sounds like maybe something is bad with the cpu profiling becoming unstable when screen-off profiles kick in.
sg1dan said:
don't have this issue on Synergy 3.0 running the latest ziggy kernel
Click to expand...
Click to collapse
I can confirm that this one worked for me too. Synergy 3.0 running Ziggy's Kernal and everything works well.
Anyone know where to grab just the Kernal? Can't seem to find the latest download.
I should also add, that when I do flash the Stock GB kernal so that my ROM will be stable.... my camera freezes everytime I try to take a picture. Happens in every ROM I mentioned above. However, it works fine before I flash the stock kernal.
running "stock kernel" it looks to be fixed. Looks like I tried this before as I already had the file but.... works now for some reason
Thanks.
Will report back if it ****s up
I'm hoping I can provide information that may be helpful to developers about the Thunderbird's random rebooting problems.
For my phone it seems related to the ROM I'm running, so maybe this will help ID the problem?
ROMS w/o reboots:
Got the phone, got the OTA update, no reboots. None.
Rooted the phone, configured and ran PG05IMG_MR1_upgrade.zip, no reboots.
After bad experienced, unrooted, back to stock, no reboots.
OTA update again, no reboots.
Re-rooted, again ran the updated rooted ROM, no reboots.
Several listed below caused problems so I'm on Synergy with no reboots.
ROMs with reboots:
Liquid 1.5, reboots 2-3 times/hour
Liquid 1.4, reboots several times/day
Liquid 1.6, reboots several times/day
PUR3A05PTH3ORY v 1.2.2 reboots several times/day
Gingervitis 1.2, no reboots, powers off and won't come back on until I do a battery pull!
I'm really hoping this will help someone take a stab at fixing the problem! Changelogs for Liquid should help, why is 1.5 worse than 1.4 or 1.6? What's included or missing in the ROMs that fail as compared to the roms that work?
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
For example, I used Gingeritis based off of the GB leak and was getting a lot of reboots, but I tried BAMF and wasn't getting any. Meanwhile others get reboots on BAMF and don't on Gingeritis. Android is some trial and error before everything works just how you want it, IMO.
I was getting a lot of reboots almost non-stop from PUR3A05PTH3ORY. and I get 1 once in a while with CM7.
I know some TB's even rebooted a lot with the stock rom unrooted. My first one was like that.
I've flashed the mr2 radio and have used it for all roms and I've had no reboots
Bolted Down....
g00s3y said:
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
Click to expand...
Click to collapse
Partially true but there are common factors such as many having reboot problems with Liquid 1.5, etc.
Okay, I was running infection 2.5 for about 2-3 months. I tried to upgrade to 2.8.1 infection last week, but kept getting random wifi/date drops constantly. I tried Tron for a few day, but that kept hanging up. I tried Xenion??, but that also had the wifi/date drops. Now I have tried Vanilla. It was running fine all day yesterday and today, but now it stuck in bootloop.
What gives. Any advice? Should I reflash an RUU and update?
I am S-off; H-boot 2.28 and radios 2.23....
I never had this many issues with different ROM before. FYI, I have tried different kernals, different governors, etc... It also seems my phone is running hot with battery temps over 110* constantly.
Please help.
(Edit: Before someone asks, I have wiped, and wiped, and wiped even more, total clean install of apps, etc...).
Nappyloxs said:
Okay, I was running infection 2.5 for about 2-3 months. I tried to upgrade to 2.8.1 infection last week, but kept getting random wifi/date drops constantly. I tried Tron for a few day, but that kept hanging up. I tried Xenion??, but that also had the wifi/date drops. Now I have tried Vanilla. It was running fine all day yesterday and today, but now it stuck in bootloop.
What gives. Any advice? Should I reflash an RUU and update?
I am S-off; H-boot 2.28 and radios 2.23....
I never had this many issues with different ROM before. FYI, I have tried different kernals, different governors, etc... It also seems my phone is running hot with battery temps over 110* constantly.
Please help.
(Edit: Before someone asks, I have wiped, and wiped, and wiped even more, total clean install of apps, etc...).
Click to expand...
Click to collapse
Did your issues start after flashing the latest firmware?
kc6wke said:
Did your issues start after flashing the latest firmware?
Click to expand...
Click to collapse
No, my wifi/data was going in and out before, so I update to the latest firmware.
Nappyloxs said:
No, my wifi/data was going in and out before, so I update to the latest firmware.
Click to expand...
Click to collapse
I was having similar issue on New firmware with older roms
That's why I decided to make my own from the latest ota.
I havent had an issue since.
kc6wke said:
I was having similar issue on New firmware with older roms
That's why I decided to make my own from the latest ota.
I havent had an issue since.
Click to expand...
Click to collapse
I wish I knew how to. One day I may learn. I just switched to a Sense rom (Nils 4.0), just because I could not get out of bootloop earlier. I am going to let that run until it a) either acts up or b) until I have time to toss on a new rom, RUU, etc...
Go for a cm9 ROM maybe. There super stable, I used them before cm 10.1
I use the unofficial cm 10.1 rom now
Sent from my ADR6425LVW using xda app-developers app