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.
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 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.
Gads. I've waited 2 years to root my phone and the first ROM I flash toasts it. I downloaded the Skyraider Zeus 1.3 and everything looked fine. When it rebooted, though, I realized I'm not able to do anything.
I slide the lock to get into the phone and I'm greeted by a dialog about in-call volume. All I can do is hit the Silent button and it switches between that and bluetooth volume. I can't figure out how to get past it so I can actually do anything.
Ideas?
ETA: Now I'm really sick to my stomach. I decided to restore from backup. Neither one of the backups I made prior to flashing are working.
Error while restoring /data!
WTF? Now I'm dead in the water.
4pm Update: I figured I have a brick now so I wiped data/factory reset, wiped cache. Now I'm trying to re-install Skyraider. I'm not holding my breath.
You're not bricked.
Go back into recovery...
Wipe data/factory reset 3x, wipe cache, and then wipe dalvik cache.
Flash the ROM.
You should be good.
Sent from my ADR6400L using xda premium
RBarnett09 said:
You're not bricked.
Go back into recovery...
Wipe data/factory reset 3x, wipe cache, and then wipe dalvik cache.
Flash the ROM.
You should be good.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Thanks. I did that and it worked. I guess I have to reinstall everything.
Why would two different backups fail to restore? The first I did manually last night through Titanium. The second I did when I flashed through ROM Manager.
That's your problem using rom manager. Download 4ext in the play store and you wont have backup issues.
Sent from my SHIFTAO5P using Tapatalk 2
Dark Jedi said:
That's your problem using rom manager. Download 4ext in the play store and you wont have backup issues.
Sent from my SHIFTAO5P using Tapatalk 2
Click to expand...
Click to collapse
Will do. What a debacle it started out to be. I think I'm ok now. I got the ROM working and for some reason although I wasn't able to boot into recovery and restore I have been able to restore my apps and data through Titanium. I have to say buying the Pro license was worth not having to acknowledge each install. :laugh:
One thing I noticed is that I used to be able to slide the task bar down and have two options. Initially it was set with notifications but I could select a tab to make quick selections like enable/disable the hotspot, etc. I'll have to figure out why I only see notifications now. Maybe that's just part of the ROM behavior.
JaxDroidGuy said:
Will do. What a debacle it started out to be. I think I'm ok now. I got the ROM working and for some reason although I wasn't able to boot into recovery and restore I have been able to restore my apps and data through Titanium. I have to say buying the Pro license was worth not having to acknowledge each install. :laugh:
One thing I noticed is that I used to be able to slide the task bar down and have two options. Initially it was set with notifications but I could select a tab to make quick selections like enable/disable the hotspot, etc. I'll have to figure out why I only see notifications now. Maybe that's just part of the ROM behavior.
Click to expand...
Click to collapse
That's strange that you don't see the quick settings tab.
Usually after flashing a ROM through recovery, I flash it an extra time so that I know it gets all the files through.
I know when I flashed Gingeritis 3D, I couldn't get the music player to stop force closing when I changed the music sound effects. The only way to fix these issues and a few others was to flash it a couple more times, without wiping anything at all. Dirty flashes (not wiping) could possibly fix any issues as long as you haven't changed any of the ROMs settings or set up anything.
Sent from my ADR6400L using xda premium
RBarnett09 said:
That's strange that you don't see the quick settings tab.
Usually after flashing a ROM through recovery, I flash it an extra time so that I know it gets all the files through.
I know when I flashed Gingeritis 3D, I couldn't get the music player to stop force closing when I changed the music sound effects. The only way to fix these issues and a few others was to flash it a couple more times, without wiping anything at all. Dirty flashes (not wiping) could possibly fix any issues as long as you haven't changed any of the ROMs settings or set up anything.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Ha! I was just trying to grab a screenshot and found Quick Settings. I accidentally tapped the top of the window and now I see it. However, it only lists Wi-Fi, BT, GPS, and media volume. I really hope I can figure out how to add the hotspot.
ETA: Found it in Skyraider settings! I'm getting closer to where I wanna be!
JaxDroidGuy said:
Ha! I was just trying to grab a screenshot and found Quick Settings. I accidentally tapped the top of the window and now I see it. However, it only lists Wi-Fi, BT, GPS, and media volume. I really hope I can figure out how to add the hotspot.
Click to expand...
Click to collapse
To change those settings in that menu you would probably have to look in the skyraider settingsm
Sent from my ADR6400L using Tapatalk 2
This is getting better. Now I'm posting from my netbook connected via WiFi tethering an not using the Verizon hotspot! This will save me another $30/mo.
So far this ROM seems to be much faster jumping between apps than stock. I'm going to play with it a few days and then throw caution to the wind and try the Skyraider ICS ROM. :silly:
Skyraider ics? I wasn't aware that they had an ics rom for the bolt.
Sent from my ADR6400L using Tapatalk 2
My bad. I followed it from the Skyraider download but it's the ICS leak for HTC.
JaxDroidGuy said:
My bad. I followed it from the Skyraider download but it's the ICS leak for HTC.
Click to expand...
Click to collapse
That rom blows. If you want a working decent sense 3.6 get nusense from the infectedrom forums.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
That rom blows. If you want a working decent sense 3.6 get nusense from the infectedrom forums.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Nusense is actually on my list. These are what I was initially looking at trying:
Liquid Smooth AOKP
SkyRaider Zeus 1.3
NuSense
I think I'm like most Tbolt users that are tired of waiting for ICS. I wasn't sure about Nusense because I was believing that Sense was the source of a lot of my problems. However, SkyRaider (even though it's neither ICS nor Sense-less) is running considerably better. My phone was next to useless. It might take 1-2 min just for the stupid thing to dial a # once it was selected. I'd tell people if I ever needed 911 I'd be dead before it even dialed. I also had a lot of problems with messaging and general performance. So maybe it was just a bloatware problem that was dragging me into the mud.
Now that I'm having a positive experience with SR I think I'm going to make NuSense my next one. It looks very promising. I appreciate the warning and help to steer me clear.
JaxDroidGuy said:
Nusense is actually on my list. These are what I was initially looking at trying:
Liquid Smooth AOKP
SkyRaider Zeus 1.3
NuSense
I think I'm like most Tbolt users that are tired of waiting for ICS. I wasn't sure about Nusense because I was believing that Sense was the source of a lot of my problems. However, SkyRaider (even though it's neither ICS nor Sense-less) is running considerably better. My phone was next to useless. It might take 1-2 min just for the stupid thing to dial a # once it was selected. I'd tell people if I ever needed 911 I'd be dead before it even dialed. I also had a lot of problems with messaging and general performance. So maybe it was just a bloatware problem that was dragging me into the mud.
Now that I'm having a positive experience with SR I think I'm going to make NuSense my next one. It looks very promising. I appreciate the warning and help to steer me clear.
Click to expand...
Click to collapse
You should try Twisteds version of Liquid ICS AOSP . Only problem is Netflix and video can don't work. But other than that its a great rom --> http://forum.xda-developers.com/showthread.php?p=33076925
Sent from my ThunderBolt using Tapatalk 2
Thanks. I'll give it a shot. I don't use Netflix much from the phone so that's not a deal breaker.
How is it with data? I flashed NuSense yesterday morning and flashed back to SkyRaider last night. I couldn't stay connected. The data drops were horrible. It was odd. I'd have the 3G/4G icon like I was connected but couldn't surf/email/etc. Then other times I'd lose the 3G/4G altogether. Sometimes resetting the mobile data would work and other times it would just laugh at me.
I guess I didn't give it much of a chance since it only lasted <12 hours but it was driving me nuts. Nothing like spending time with family and not being able to surf and escape.
Any liquid based ics rom is plagued with data drops.
Sent from my SHIFTAO5P using Tapatalk 2
Dark Jedi said:
Any liquid based ics rom is plagued with data drops.
Sent from my SHIFTAO5P using Tapatalk 2
Click to expand...
Click to collapse
I'm not getting them that bad. Maybe twice a day at best. Have you tried pulling your sim for a little bit.
Sent from my ThunderBolt using Tapatalk 2
disconnecktie said:
I'm not getting them that bad. Maybe twice a day at best. Have you tried pulling your sim for a little bit.
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
I have done it all. New sim pulled sim and all different radios.
Sent from my ThunderBolt using Tapatalk 2
Dark Jedi said:
I have done it all. New sim pulled sim and all different radios.
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
You don't get data drops on other builds? Have you checked the gold tabs under your battery door and bald sure they aren't damaged? Maybe check to see if they are making good contact too.
Sent from my ThunderBolt using Tapatalk 2
Dark Jedi said:
Any liquid based ics rom is plagued with data drops.
Sent from my SHIFTAO5P using Tapatalk 2
Click to expand...
Click to collapse
Ugh. That's not good. SkyRaider has been rock solid on data. The only thing I've really run into is it seems flashing my apps with app2zip only works on some things. I end up having to re-flash Kindle, Lookout, and a few other apps once I'm up and running again.
I was really looking forward to ICS but not if data drops are the norm.
Everything was fine until I flashed PAC-man and Paranoid Android a while back. I went back to stock after and then realized my proximity sensor wasn't working. It was 100% fine before that. In a phone call, my screen turns off and then doesn't come back on unless I stick the phone under light. Somehow my proximity sensor turned into a light sensor. I have tried everything since. I read somewhere that Perseus kernel would help. So I unlocked again, flashed CleanROM (which I liked very much) and Perseus v30. It seemed to work again. I was happy... Until I flashed the latest Perseus v31 a few days ago. It's broken again and I can't get it back. Went back to stock again, unlocked again, flashed a stock rooted rom, flashed beans deodexed rom, flashed CleanROM, flashed perseus, nothing. NOTHING works. What the heck is going on here!? Should I just finally give in and go the warranty route, or can someone identify this problem and come up with a fix. And I know about the temporary setting in call settings, I want my sensor to work though. I know it's not just me, I've seen this in multiple threads for other devices as well, also happening after flashing PA or another AOSP ROM. I wonder what else broke that I don't even know about? I'm tired of dealing with this issue. Thoughts?
I'm not surprised this happened in PAC. All the Asop ROMs are based off of cm10 build we have which has a known big of proximity not working. If you had success with Pegasus 30 and clean ROM, try flashing that again. I guarantee someone else on Xda can come up with a better solution so don't waste your root by getting a new device with a new boot loader in it XD
Sent from my SCH-I605 using xda app-developers app
Sounds less like a hardware issue and more like a custom rom issue.
Yeah....better warranty that.
/s
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
Sounds less like a hardware issue and more like a custom rom issue.
Yeah....better warranty that.
/s
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Exactly why Verizon wants these things locked down. ... Oh and they suck
Sent from my SCH-I605 (AKA NOTE 2)
Exactly. The guy troubleshooted his own post and doesn't even know it.
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
Exactly. The guy troubleshooted his own post and doesn't even know it.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
he just doesn't want to take responsibility for breaking his own stuff.
Sent from my SCH-I605 (AKA NOTE 2)
So I realized WiFi is causing my Screen of Death issue on EVERY KitKat ROM, and only KitKat ROM's. So what is my next step? Does anyone have a fix on this or anything? It'll either Screen of Death my phone or my data won't work until I turn off WiFi and then I can't turn it back on. Any help would be appreciated guys. I'm desperate now. 15 battery pulls a day are just ridiculous.
Why did you make a new thread? :what:
Anyways...I'm in the same boat as you. Take a few screenshots of your app drawer so I can see if we are using any of the same apps, it's possible one of them are the problem.
Sent from my SCH-I545 using Tapatalk
Well OP isn't very active, so I thought I'd get a logcat. I was connected to WiFi until I noticed it wasn't receiving any data (but still showed connected to WiFi). I turned the screen off and then it would not come back on anymore, but the phone was still responsive. I could turn torch on and off and even took a screenshot, but the screen still refused to come on. I'm guessing that whatever is happening, usually does so while the screen is off, and that's why I get a BSOD.
I'd like to add I've tried a bunch of different modems, clean flashed CM11, even restored no apps...yet the problem persists.
I've attached it to this post, if anyone has time to check it out I would be very grateful.
thesoldier said:
Why did you make a new thread? :what:
Anyways...I'm in the same boat as you. Take a few screenshots of your app drawer so I can see if we are using any of the same apps, it's possible one of them are the problem.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I screenshot my drawer but don't have access to a computer till tomorrow. So I'll send em over. But yeah I just made a new thread because I wasnt getting any answers on the other when I discovered that WiFi was the issue.
I'm just so frustrated with my phone because I can not figure out a fix. At first I installed a clean kitkat ROM with full wipe, and didn't restore apps to see if it was an app but it still did it. Then I even completely unrooted my phone and rerooted, still did it.
Nwwolf1 said:
So I screenshot my drawer but don't have access to a computer till tomorrow. So I'll send em over. But yeah I just made a new thread because I wasnt getting any answers on the other when I discovered that WiFi was the issue.
I'm just so frustrated with my phone because I can not figure out a fix. At first I installed a clean kitkat ROM with full wipe, and didn't restore apps to see if it was an app but it still did it. Then I even completely unrooted my phone and rerooted, still did it.
Click to expand...
Click to collapse
That's alright, if it also did it for you without restoring any apps, its gotta be something else. But what... I have no idea.
It seems that WiFi is crashing while the screen is off and that is resulting in a BSOD. Why the hell is it crashing though... :banghead:
Sent from my SCH-I545 using Tapatalk
thesoldier said:
That's alright, if it also did it for you without restoring any apps, its gotta be something else. But what... I have no idea.
It seems that WiFi is crashing while the screen is off and that is resulting in a BSOD. Why the hell is it crashing though... :banghead:
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah. I'll notice my WiFi is no longer sending data so I'll turn it off then it won't turn on. Or I'll try to turn it off and it won't then I know that if I lock my screen it won't turn on without a battery pull.
I'm not sure where to go from here if nobody can decipher that logcat.
All I can think of is to back up my SD card and completely format the phone.. then see if it persists.
Sent from my SCH-I545 using Tapatalk
Has anyone come up with any solutions to the problem at all?
Nwwolf1 said:
Has anyone come up with any solutions to the problem at all?
Click to expand...
Click to collapse
I have yet to find a solution to this... It seems like nobody else has this issue.
Sent from my SCH-I545 using Tapatalk
So I just odined the stock MDK image, wiping everything. The only thing I copied back over was my pictures. Flashed back to KitKat and it STILL happens. WTF. This is beyond aggravating.
Sent from my SCH-I545 using Tapatalk
Okay I hate to speak too soon. But I MAY have found a temporary fix. I noticed that the screen only freezes and shuts off on the lock screen. Never any other time. So I turned off the android lock screen and put up widget locker instead (set up exactly the same way) so far it hasn't happened. Here's hoping I'm not jynxing myself though!
Never mind. I did speak to soon...ugh we need to find a fix for this and soon. Is it only on the vzw gs4?
Nwwolf1 said:
Never mind. I did speak to soon...ugh we need to find a fix for this and soon. Is it only on the vzw gs4?
Click to expand...
Click to collapse
I've googled and don't see any mention of WiFi causing a bsod.
I'm gonna test my next theory, not let Google restore anything from my Google account. That's the only other thing that is being restored.
Sent from my SCH-I545 using Tapatalk
Well I tried that....still happens. Officially out of ideas.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
Well I tried that....still happens. Officially out of ideas.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I tried that a while back too. I've tried everything I could possible think of. I had to go back to CM10.2 because I just couldn't stand doing a battery pull 10 times a day, killing my battery.
Anyone have any luck with a fix yet?
Nwwolf1 said:
Yeah I tried that a while back too. I've tried everything I could possible think of. I had to go back to CM10.2 because I just couldn't stand doing a battery pull 10 times a day, killing my battery.
Anyone have any luck with a fix yet?
Click to expand...
Click to collapse
Have either of you tried flashing KToonsez kernel with whatever ROMs your on??? Worth a shot. I didn't see either of you mention kennel, you've Odin back to stock and still happens though huh? Maybe bad WiFi antennas idk
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Have either of you tried flashing KToonsez kernel with whatever ROMs your on??? Worth a shot. I didn't see either of you mention kennel, you've Odin back to stock and still happens though huh? Maybe bad WiFi antennas idk
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
That's what's confusing me so much. I know its WiFi but its only on kitkat ROMs. That means that the WiFi antennas must have changed on 4.4 right?
Nwwolf1 said:
That's what's confusing me so much. I know its WiFi but its only on kitkat ROMs. That means that the WiFi antennas must have changed on 4.4 right?
Click to expand...
Click to collapse
So if u have WiFi toggled off during the day you don't have this problem at all?? I'm not really sure myself if anything with wifi has changed in 4.4
How many different kit kat ROMs have you tried? And you said you're in the latest modem?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
So if u have WiFi toggled off during the day you don't have this problem at all?? I'm not really sure myself if anything with wifi has changed in 4.4
How many different kit kat ROMs have you tried? And you said you're in the latest modem?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, it never happens when Wifi is off. I've tried it on CM11, OmniRom, Jelly Beans, PA, Gummy Rom, and I think one other. And what is modem again?
Nwwolf1 said:
Yeah, it never happens when Wifi is off. I've tried it on CM11, OmniRom, Jelly Beans, PA, Gummy Rom, and I think one other. And what is modem again?
Click to expand...
Click to collapse
The modem (baseband) is something you can flash in recovery..
It controls the cells hardware that communicates with the actual cell towers.
That isn't going to mess with your WiFi though.. How about kernels have you tried another one maybe KToonsez ?
Sent from my SCH-I545 using Tapatalk