I cant pinpoint at all whats going on. I get at least 5 screens of death each day. I full wipe and everything before I flash a rom on my phone. I'm currently on Turkbey v7. Someone please help me out
Return to stock, if it happens still probably best to return it if you can.
LiLChris06 said:
Return to stock, if it happens still probably best to return it if you can.
Click to expand...
Click to collapse
oh no... i just got a replacement a few weeks ago..
Did you mess with clocks/voltage at one point? There may be an init.d script or some other kernel settings leftover from those that you gotta get rid of. Flashing back to stock should fix that if I'm not mistaken.
Can you still return your replacement?
afrojoc said:
oh no... i just got a replacement a few weeks ago..
Click to expand...
Click to collapse
that jus tmeans you'll need another
Did you clean out the kernal settings between ROMs/Kernals?
No I didn't mess with any overclock or voltage settings.
I can still get another replacement phone until a year has passed since this phone has been released since thats when I got the first phone.
And tomorrow I'll try flashing back to stock and then flashing a rom afterwards. I have to study for my summer class tonight.
Thanks alot everybody!
afrojoc said:
oh no... i just got a replacement a few weeks ago..
Click to expand...
Click to collapse
well replacements are usually refurbished, if im not mistaken. Theres probably a higher chance that something is wrong with a refurbished phone over a brand new phone. So maybe not that unexpected that something will go wrong, especially with custom software
I would try running the kernel cleaning script and flashing a new kernel. I known NEAK didn't like me and locked up several times a day. But its so darn fast....just giving an example. What kernel r u running now?
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I would try running the kernel cleaning script and flashing a new kernel. I known NEAK didn't like me and locked up several times a day. But its so darn fast....just giving an example. What kernel r u running now?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
NEAK...
NEAK is working great here with UCLD4. I used to have tons of SoDs with LD3 on the stock kernel, just about every time I turned the phone off it would SoD within a couple minutes.
So because I felt too lazy to go to stock, I found the kernel cleaning script and wiped everything off my phone and flashed the script. Then I reflashed the Turkbey rom since I just like it and so far I haven't gotten any SODs as of yet.
afrojoc said:
So because I felt too lazy to go to stock, I found the kernel cleaning script and wiped everything off my phone and flashed the script. Then I reflashed the Turkbey rom since I just like it and so far I haven't gotten any SODs as of yet.
Click to expand...
Click to collapse
Yayz! If I wasn't such a fanboy of AOKP I'd try it. I just totally fell in love with this ROM. maybe one day....glad things are working for ya.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
Yayz! If I wasn't such a fanboy of AOKP I'd try it. I just totally fell in love with this ROM. maybe one day....glad things are working for ya.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Its not bad. Im mostly on it cause i thought i got the least amount of SODs on here hehe. Its my safe zone to be at.
But anyway thanks for your help and everyone else who spent time and effort to help me solve this stupid problem! I love this forum..
Voltage
Min volts may be set too low. Bring first step up to 200. Allot of times its too much deep sleep.
Related
Any one know of anything else I can do with my fascinate. Running 1.1 Zinc with no kernel. My phone does not approve. Anything I'm missing out on?
zachsx said:
Any one know of anything else I can do with my fascinate. Running 1.1 Zinc with no kernel. My phone does not approve. Anything I'm missing out on?
Click to expand...
Click to collapse
I wouldn't approve of that, either!
Seriously, if you were able to flash a ROM, and you did it through Clockwork Recovery/ROM Manager, then you are running a modded kernel.
Voodoo seems to be causing some people more trouble than they feel it's worth, so I'd suggest one of jt1134's or Dirrk's non-Voodoo kernels, or Birdman's once it's past the testing stage.
Non-voodoo? I must have missed those. Search is not being my friend. Care to link a guy up? The only kernel threads I can find are their voodoo kernels.
Sent from my SCH-I500 using Tapatalk
PhoenixPath said:
Non-voodoo? I must have missed those. Search is not being my friend. Care to link a guy up? The only kernel threads I can find are their voodoo kernels.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
swing by irc #samsung-fascinate on freenode.net. check topic for kernel links
My phone started lagging badly 3 days after the vodoo lagfix...how ironic. When I disabled it, it nearly bricked my phone. Desperate to get my phone up and running, I did a wipe. It killed the phone's internal memory. Had to reflash back to stock and since then my phone has been running really well w/o the lagfix even. Maybe my phone had a bad image like a computer. Not doing anything else to my phone til froyo comes out. I am rooted though.
Sent from my SCH-I500 using XDA App
You could try more cow bell. I heard it's the only cure for some fevers.
I've been semi-bricked three times when I've disabled Voodoo, and I did it right. So I use a non-voodoo kernel now. I'll wait until these bugs are ironed out. Join the irc chat and jt and the other devs commonly post kernel links.
Yup.. Using jt's 1031 test kernel now (novoodoo). Running beautifully.
Sent from my SCH-I500 using Tapatalk
Technically voodoo hasn't bricked a single phone. User error and then likely a small error in the proccess itself have caused some ugly problems but it can be overcame with a little work
Sent from my SCH-I500-Fascinate using XDA App
ksizzle9 said:
Technically voodoo hasn't bricked a single phone. User error and then likely a small error in the proccess itself have caused some ugly problems but it can be overcame with a little work
Sent from my SCH-I500-Fascinate using XDA App
Click to expand...
Click to collapse
I said semi-bricked. It wouldn't get past the boot screen. It couldn't have been user error two of those times, because I used reboot button to do it.
Kamar234 said:
You could try more cow bell. I heard it's the only cure for some fevers.
Click to expand...
Click to collapse
Thank you for this. Seriously though, I've been running jt's voodoo kernels since their release with only minor problems. I've disabled voodoo and flashed other kernels no less than three times without issue. Granted it does take a while to boot after enabling/disabling voodoo. The first few times I thought I screwed up, but it always boots for me.
Sent from my SCH-I500 using XDA App
Mean Bro Greene said:
Thank you for this. Seriously though, I've been running jt's voodoo kernels since their release with only minor problems. I've disabled voodoo and flashed other kernels no less than three times without issue. Granted it does take a while to boot after enabling/disabling voodoo. The first few times I thought I screwed up, but it always boots for me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think it's a phone to phone thing. Some people have no problems just turning off voodoo when they flash ROMs and kernels. I have to use adrynalyn's voodoo uninstaller and wipe completely if I want to change ROMs or kernels.
Weird.
Yea when I tried to turn voodoo off it took 4 reboots before it took. No issues after that though.
*EDIT* Posted in wrong thread...my apologies
Used the "reboot button" app to disable Voodoo. It hung on "Samsung" for over an hour after robot women said "operation completed" or whatever. i finally admitted defeat and did a battery pull. Restart resulted in a boot loop. I was able to recover following the "remove Voodoo" thread and flashing the stock Nandroid. From there I flashed jt's v.4 Super Clean ROM with Frost's theme. Having had the stones to try Voodoo again but honestly my phone is running good with just the Super Clean ROM. Having a recent Titanium backup really helped get my phone back in order quickly.
While it was an unpleasant experience it ended well and resulted in a nice clean and fast Fascinate. Best part though is that I'm no longer afraid to flash my phone since I now know I can recover fairly quickly.
Martian21
martian21 said:
Best part though is that I'm no longer afraid to flash my phone since I now know I can recover fairly quickly.
Martian21
Click to expand...
Click to collapse
...that way lie the dragons...
Yeah, that's pretty much what destroyed any hope I had of *not* being a total ROM-a-holic. I have owned this thing for no more than 2 weeks and have pushed over a dozen different roms/kernels on it.
I cannot even imagine what this poor phone will be going through once we start getting things like Cyanogen's up and running.
(currently using jt's 1031 USCC non-voodoo kernel...at least until I get home.)
I'm a little hesitant re-flashing Gingerbread because of the little scare we had, but I hear that now just two people got bricked.
So how many of you are back on Gingerbread?
I am. It has always ran really good for me. I'm using gingivitus IX. The only problem I have with this Rom is that the battery takes forever to charge. No other complaints.
Sent from my ADR6400L using Tapatalk
I'm using no-frills CPU to Overclock. I have HTC inspire 4g running coredroid 6.6 what would be a good starting point for my
Min. Clock freq? And my max clock freq? And also what do the freq's do? Help please trying to get the most out.
Also if someone would explain what the governers are....
Smartass
Interactive
Conservative
Userspace
Ondemand
Performance
Help pleas
Sent from my Desire HD using XDA App
And also what is the correct way to use a different kernel than the one that is in the ROM? I have the ext4 wipe. Not used it. I just clear everything from recovery mode.
Basically what's the correct way to flash a new kernel?
Sorry for the double post.
Sent from my Desire HD using XDA App
Sent from my Desire HD using XDA App
yatyas2141 said:
And also what is the correct way to use a different kernel than the one that is in the ROM? I have the ext4 wipe. Not used it. I just clear everything from recovery mode.
Basically what's the correct way to flash a new kernel?
Sorry for the double post.
Sent from my Desire HD using XDA App
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Wrong forum....
>--The Game--<
superchilpil said:
Wrong forum....
>--The Game--<
Click to expand...
Click to collapse
Hahaha, yeah I know seriously.
I'm going in
Flashed GB successfully last night then flashed back to Fro ...on GB now so far so good DAS BAMF rom... HTC Thunderbolt rooted...
Tbolt101 said:
Flashed GB successfully last night then flashed back to Fro ...on GB now so far so good DAS BAMF rom... HTC Thunderbolt rooted...
Click to expand...
Click to collapse
I just flashed that and I'm loving BAMF 2.0 Remix.
Is there any news on GB radio causing bricks I would like to try it. The firdt post said it was only two phones that got bricked.
wooddale said:
Is there any news on GB radio causing bricks I would like to try it. The firdt post said it was only two phones that got bricked.
Click to expand...
Click to collapse
I heard that it was just two phones out of thousands, but I don't know that's a risk you take every time you flash anything.
wooddale said:
Is there any news on GB radio causing bricks I would like to try it. The firdt post said it was only two phones that got bricked.
Click to expand...
Click to collapse
After I flashed GB to my phone my wife left me, dog ran away, and I got pregnant, twice.
Hasn't phased me though. Flashing LiquidGingerSense tonight, just because.
Sent from my super duper deluxe rooted re-romed Thunderbolt. ( and yes, it can also wash my car AND do the dishes)
I was hearing from Jcase that it was more than just a few phones
I heard around 30 were bricked, but considering how many TB's there are out there, not a bad ratio. How many of those 30 were caused by user error?
I am not sure this was posted or not, however if it has, please point me to the right direction as I am not able to find it.
Situation:-
Using the phone as per normal. It auto lock or manual lock it. Wanna unlock/wake up the phone it doesnt. This happened once in awhile not sure when as unable to determine the cause as sometimes running a game and I lock it and sometimes lock it without running anything i.e. back to home. To wake up, I reboot the phone by long pressing on/off button. Was using CheckRom ICS... And at one occurance the phone really died on me and unable to reboot no matter what I did. Sent in to SC and got back a new Motherboard.
Now it is happening again. Now in JB 4.1.2 (OmegaRom). The phone just fell in to a deep sleep and cant wake up unless I reboot the phone. I hope I dont get the forever slumber/sudden death situation again.
Anyone can give guidance or advise on how to check what is the matter or anyone having the same experience?
Flash back to stock and check if it occurs. If it does use triangle away and send it back in mate
Sent from my GT-I9300 using XDA Premium HD app
firstknightfirst said:
I am not sure this was posted or not, however if it has, please point me to the right direction as I am not able to find it.
Situation:-
Using the phone as per normal. It auto lock or manual lock it. Wanna unlock/wake up the phone it doesnt. This happened once in awhile not sure when as unable to determine the cause as sometimes running a game and I lock it and sometimes lock it without running anything i.e. back to home. To wake up, I reboot the phone by long pressing on/off button. Was using CheckRom ICS... And at one occurance the phone really died on me and unable to reboot no matter what I did. Sent in to SC and got back a new Motherboard.
Now it is happening again. Now in JB 4.1.2 (OmegaRom). The phone just fell in to a deep sleep and cant wake up unless I reboot the phone. I hope I dont get the forever slumber/sudden death situation again.
Anyone can give guidance or advise on how to check what is the matter or anyone having the same experience?
Click to expand...
Click to collapse
I am experiencing exactly the same thing , so unrooted and back on stock ics now and even that doesn't seem stable...planning to sell it off next week... desperately hoping it doesn't slìp into deep slumber when I am selling it...
Sent from my GT-I9300 using xda premium
tommy2601 said:
I am experiencing exactly the same thing , so unrooted and back on stock ics now and even that doesn't seem stable...planning to sell it off next week... desperately hoping it doesn't slìp into deep slumber when I am selling it...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Oh no... I like the phone and I hope I dont have to sell it off.... So I am hoping someone here woudl be able to help me out.... I am backing up nearly everyday with TiB....
Even I love my s3 but I love note 2 even more and I am buying a note 2....the main reason I am selling it is if it conk out one day here in India it's very difficult to claim warranty we really need to slug it out with Samsung India and I don't have the time or patience to do that...
Sent from my GT-I9300 using xda premium
happened to me too
I don't recall it happened to me while using stock touchwiz roms.
However, since I've moved to AOSP roms (first AOKP M1 and then JellyBam), it happened to me 3 or 4 times now.
Do you get it also on touchwiz roms? Which OmegaRom are you using?
Wich kernel are using my mates? Maybe that is problem, combination firmware and kernel...
Regards
using latest OmegaRom... as mentioned... first happened in CheckROm and even in Wanam...
Was using siyah kernel... so now testing Perseus and see wtr this happened or not...
Just happened when I have monster warlord running and locked it.. when I unlock... it happened again... must be something like not enuf ram or went into deep sleep... very strange indeed. Nevertheless change to Perseus to test out different kernel for now...
tommy2601 said:
I am experiencing exactly the same thing , so unrooted and back on stock ics now and even that doesn't seem stable...planning to sell it off next week... desperately hoping it doesn't slìp into deep slumber when I am selling it...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
If u sell a broken phone,that is such a douchebag move no offence to u but really i wud feel sorry for the man u sold it..
Sent from my GT-I9300 using xda premium
Download this app https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en and post the screenshot. It might be SDS
Same happened with my phone. Go to see what it's up to and suddenly its not responding. The only option is to hold power down until it reboots.
It would also do it on in coming calls and managed to delete a text which arrived shortly before it froze.
Hoped upgrading to the latest firmware would help, didn't. Going without root, nope. Freezing apps in Titanium, still no joy.
Finally this morning I had enough and went for a full wipe. Very little installed but no problems since.
Would suggest doing the same, especially if you plan to sell the phone anyway.
CHEVYbarracuda1 said:
If u sell a broken phone,that is such a douchebag move no offence to u but really i wud feel sorry for the man u sold it..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi buddy, selling a dying phone at a good price and buying something u love even more is douche bag move....then I really petty ur retarded and douche bag thinking
Sent from my GT-I9300 using xda premium
Have the same problem with mine, using the latest wanam stock rom and every now and again the phone will either just restart or lock with the screen off (led notification will keep blinking however).
Just trying the official Vodafone rom now through Odin. If this doesn't solve it I think the phone will have to go back.
To note: issue appeared after installing some root apps. Notably adfree and beats drivers. Anybody else have either installed?
tommy2601 said:
Hi buddy, selling a dying phone at a good price and buying something u love even more is douche bag move....then I really petty ur retarded and douche bag thinking
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I said no hard feelings.. U said that u hope that it doesnt slips into deep slp when u r selling it.. so bassically u r trying to sell broken phone for a price of good one usable...also i havent insulted u before so why r u insulting me??That my friend is called lack of culture..
Sent from my GT-I9300 using xda premium
CHEVYbarracuda1 said:
I said no hard feelings.. U said that u hope that it doesnt slips into deep slp when u r selling it.. so bassically u r trying to sell broken phone for a price of good one usable...also i havent insulted u before so why r u insulting me??That my friend is called lack of culture..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Please keep this on topic:
Seems like a common issue, I've now unrooted my phone and loaded stock 4.1.2 from Sammobile using odin, reset the binary counter, removed SD card and i'm still having crashes and hangs. Seems my phone is on the way out?
THEsirloin said:
Please keep this on topic:
Seems like a common issue, I've now unrooted my phone and loaded stock 4.1.2 from Sammobile using odin, reset the binary counter, removed SD card and i'm still having crashes and hangs. Seems my phone is on the way out?
Click to expand...
Click to collapse
Just return it to the nearest samsung store for repair.. I believe it is hardware failure
Sent from my GT-I9300 using xda premium
Mine has just started doing this, literally a matter of days ago - coincidence??
TimmyRaa said:
Mine has just started doing this, literally a matter of days ago - coincidence??
Click to expand...
Click to collapse
When did it happen? Was it around Wednesday last week? Just thinking that maybe an updated app or something?
I have now updated again using kies with the official 4.1.2. I have no problems with restarts when using the stock apps. I have however had issues with the google servers and now believe this to have been the main reason for the crashes earlier (Christmas new phone activation traffic?).
Out of interest, have you been running adfree or the beats audio driver? I had mine working all day yesterday, installed both and then the hangs started coming back again.
Also worth noting that adfree now states that a newer version is available when loading up, but non exists (that i know of?)
CHEVYbarracuda1 said:
I said no hard feelings.. U said that u hope that it doesnt slips into deep slp when u r selling it.. so bassically u r trying to sell broken phone for a price of good one usable...also i havent insulted u before so why r u insulting me??That my friend is called lack of culture..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I am not selling it to some innocent 3 person I am exchanging it with note 2 by paying the difference amount at a local Samsung retail store (just sending back there own Frankenstein to them)
And about culture my friend I don't need a lesson from a person who doesn't even have the sensibility to understand that his comments can hurt others(u started It fIrst)..
As today Is my last day in the s3 forum I don't want to sign off on a bitter note so sorry if I have hurt u in anyway.
Sent from my GT-I9300 using xda premium
THEsirloin said:
When did it happen? Was it around Wednesday last week? Just thinking that maybe an updated app or something?
Click to expand...
Click to collapse
I can't say for sure, but around Wednesday isn't unreasonable.
Out of interest, have you been running adfree or the beats audio driver? I had mine working all day yesterday, installed both and then the hangs started coming back again.
Also worth noting that adfree now states that a newer version is available when loading up, but non exists (that i know of?)
Click to expand...
Click to collapse
I do run AdFree, and yeah, I saw the notice about the new version - it's a different app entirely... still called AdFree, uninstall the old one, and install the new one. Not sure why they did that.
I'm at a loss - I just reinstalled XELL4, and it's still doing it. Short of doing a full wipe and starting afresh (which I really can't be bothered with), I don't know what else to try. Was working fine up until now.
Hello xda
I'm getting a problem..
Sometimes my phone heats up while charging that it starts bootlooping!
But today battery was about 15% and I didn't put it on charge.. then also it started bootloop. My dad put it on charging and it keeps on rebooting and it was so hot when I came back!!
Actually, why is it rebooting again n again? It was working so fine from 2-3 days n I did nothing!
I'm using foxhound 2.4 on stock kernel.
I just wanna know that is it a hardware issue?? or what?
as it's a new phone so it tenses me.. and I didn't started development on it yet
bought around 2 weeks ago
Try re-flashing the rom but with Siyah kernel. This is what i run and it's perfect. I run overclock @ 1.7ghz and get no excess heat. Also 20 hour batrery life under standard use.
Search before asking, Ask before acting and you will succeed.
jonniboi1985 said:
Try re-flashing the rom but with Siyah kernel. This is what i run and it's perfect. I run overclock @ 1.7ghz and get no excess heat. Also 20 hour batrery life under standard use.
Search before asking, Ask before acting and you will succeed.
Click to expand...
Click to collapse
So u mean it's not an hardware issue?
And its just a kernel or rom issue?? Right?
Sent from my GT-I9300 using xda premium
I can't see it being a hardware issue, no. Especially if all was fine before flashing the ROM. It May be issues with the rom and stock kernel.
Search before asking, Ask before acting and you will succeed.
jonniboi1985 said:
I can't see it being a hardware issue, no. Especially if all was fine before flashing the ROM. It May be issues with the rom and stock kernel.
Search before asking, Ask before acting and you will succeed.
Click to expand...
Click to collapse
After flashing rom also.. its working fine..
Only sometimes it happens..
I can't get! Why does it bootloop without any reason?
Sent from my GT-I9300 using xda premium
Did you take a back up before flashing? Hopefully you did.....?
If so, then flash your stock back up and leave for a few days. If problem persists then you have an hardware issue. If problem is fixed then it was the rom and kernel issue.
As i said i akso use Fox hound 2.4 but with Siyah kernel and my handset faultless.
Search before asking, Ask before acting and you will succeed.
jonniboi1985 said:
Did you take a back up before flashing? Hopefully you did.....?
If so, then flash your stock back up and leave for a few days. If problem persists then you have an hardware issue. If problem is fixed then it was the rom and kernel issue.
As i said i akso use Fox hound 2.4 but with Siyah kernel and my handset faultless.
Search before asking, Ask before acting and you will succeed.
Click to expand...
Click to collapse
Lol
Yes I have backup!
Seriously, after using foxhound I dont wanna go back to stock
Ok.. thanz for ur support..
Lets see what happens!
Sent from my GT-I9300 using xda premium
Just run stock for a few charges. You have to find the fault. If no fault running stock thdn go back to Foxhound but try a different kernel. Goodluck!
If it works please press thanks
Search before asking, Ask before acting and you will succeed.
Rooted, Unlocked, running Beans 18 w/Faux Kernel. Recently my Note 2 has been turning off randomly and won't turn back on unless you pull the battery first. I haven't made any voltage changes and don't have any Verizon software installed. I have seen in other forums that people say it is a hardware issue. However, I never had any issues in the months of ownership until I started installing custom Roms. The Screen of Death (SOD) is becoming an issue across different phones so I am wondering what the common denominator could be. Something in Android? Can't be a hardware issue due to the variety of people using different phones, different roms. Suggestions? Done the factory reset, fix permissions, re-install Beans, different kernels...
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Which version of Faux were you running? V4 I believe had problems with lockups.
Lodingi said:
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I've tried MeanBean but I am sort of a crack flasher so I didn't stay on it long enough to know. I always clean install everything to avoid problems. I'd really hate to think it could be the Beans. It's been very reliable. Then again...I never had this problem before either...
RemnantKing2 said:
Which version of Faux were you running? V4 I believe had problems with lockups.
Click to expand...
Click to collapse
I am running V3. I believe that is the one that Bean's has an an option. But it happened using Pegasus too. There is no rhyme or reason either. It could just be sitting there and I go to use it and find it off. Which sucks for obvious reasons...
S0UTHPAWK1LLA said:
I am running V3. I believe that is the one that Bean's has an an option. But it happened using Pegasus too. There is no rhyme or reason either. It could just be sitting there and I go to use it and find it off. Which sucks for obvious reasons...
Click to expand...
Click to collapse
Have you tried reverting back to stock and seeing if it persists? And if does can you send it back through warranty?
RemnantKing2 said:
Have you tried reverting back to stock and seeing if it persists? And if does can you send it back through warranty?
Click to expand...
Click to collapse
Man..what a drag..but no, I haven't gone stock yet. I guess it makes sense to go ahead and go stock and maybe even un-root to see if it helps. I definitely can take it back with the BB extended warranty. What gets me is that as you start researching this random turn off issue, you start to see a pattern with more and more sites registering more and more complaints. I get the sneaking suspicion that Samsung knows something.. Possibly hardware issues with the Exynos chipsets. Pure conspiracy theory fodder naturally...Thank you for your suggestions...
Lodingi said:
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
It's not an issue with Beans. I've had beans on my phone since it was an S3. I've run every build from 3 on this up until now. As daily drivers. So don't imply Beans' ROM gives BSODs.
It's your kernel. The first thing you need to do before you do ANYTHING else is wipe dalvik/cache and flash a new kernel. Dirty flash the ROM again to get aroma. Pick anything other than what you did (faux) and see if you can reproduce. If you can't? There you go.
First step to troubleshooting.
P.S. faux released v5 and I haven't had one lockup. I got them hourly with v4.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
It's not an issue with Beans. I've had beans on my phone since it was an S3. I've run every build from 3 on this up until now. As daily drivers. So don't imply Beans' ROM gives BSODs.
It's your kernel. The first thing you need to do before you do ANYTHING else is wipe dalvik/cache and flash a new kernel. Dirty flash the ROM again to get aroma. Pick anything other than what you did (faux) and see if you can reproduce. If you can't? There you go.
First step to troubleshooting.
P.S. faux released v5 and I haven't had one lockup. I got them hourly with v4.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah..yesterday I flashed Faux v5. It was wonderfully smooth, but I did have one BSOD requiring a battery pull. As of this morning, I am going stock, rooted, unlocked to see what happens. I loved Beans and I don't mean to imply anything about the rom.
S0UTHPAWK1LLA said:
Yeah..yesterday I flashed Faux v5. It was wonderfully smooth, but I did have one BSOD requiring a battery pull. As of this morning, I am going stock, rooted, unlocked to see what happens. I loved Beans and I don't mean to imply anything about the rom.
Click to expand...
Click to collapse
Try stock or PB&J kernel with Beans. Bet you'll be good.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
Try stock or PB&J kernel with Beans. Bet you'll be good.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I went stock rom and stock kernel. I am really crossing my fingers hoping not to pick up my phone and find a black screen looking at me. I love being rooted and unlocked so worse case is I set the phone back and have it replaced. Thank God for the BB extended warranty at this point cause I don't have to deal with Verizon on the replacement. Samsung should come clean though...I feel like they are holding out on us about this.
S0UTHPAWK1LLA said:
I went stock rom and stock kernel. I am really crossing my fingers hoping not to pick up my phone and find a black screen looking at me. I love being rooted and unlocked so worse case is I set the phone back and have it replaced. Thank God for the BB extended warranty at this point cause I don't have to deal with Verizon on the replacement. Samsung should come clean though...I feel like they are holding out on us about this.
Click to expand...
Click to collapse
I don't, I have seen a few incidents with this but not enough to call foul on Sammy's part. 9 times out of 10 it is the users fault for doing something they shouldn't, and most of these complaints you have found are from the same people with the same screenames on different websites.
There will always be a few phones with issues because nothing is perfect, just because you may have gotten a faulty phone doesn't mean Samsung is sending out defective products. If we were in the Nexus forums with all the **** that went down there I would agree but we aren't. Nothing is perfect.
Sent from my SCH-I605 using XDA Premium HD app
Well...I went a whole day on stock without an issue. Not that that means anything, but that my note 2 may be finicky about custom roms. I have always done clean installs and don't mess with voltage on kernels. I am gonna try Beans again to see if I can figure out what I enabled that could've caused my black screen of death. The only thing that I can say for sure that I know was on was Bluetooth each time. Thank you all for your help. It is what makes XDA the go to site.