So I've had this problem for as long as I've had the phone. But I never needed to get it resolved until I started hardcore gaming on my phone. My cpu frequency reverts back to either 1.7ghz or lower whenever I startup and play a game. I've tried, (full restore/unroot/start from scratch, new roms, different kernels, deleting the post.boot system file, daemon file mod found in seperate fourm, changing cpu voltage, use the force.) Nothing works. It only seems to happen when I start up a game. The game gets super laggy. I'm currently running x-note rom with beast mode rage kernel. Bear in mind ive tried about every kernel available asside from the old mj4 kernel/rom. Anybody able to help or even point me in the direction of someone who might would be hugely appreciated. Thanks so much,
Matthew Cooksey
mscooksey21 said:
So I've had this problem for as long as I've had the phone. But I never needed to get it resolved until I started hardcore gaming on my phone. My cpu frequency reverts back to either 1.7ghz or lower whenever I startup and play a game. I've tried, (full restore/unroot/start from scratch, new roms, different kernels, deleting the post.boot system file, daemon file mod found in seperate fourm, changing cpu voltage, use the force.) Nothing works. It only seems to happen when I start up a game. The game gets super laggy. I'm currently running x-note rom with beast mode rage kernel. Bear in mind ive tried about every kernel available asside from the old mj4 kernel/rom. Anybody able to help or even point me in the direction of someone who might would be hugely appreciated. Thanks so much,
Matthew Cooksey
Click to expand...
Click to collapse
Go into power savings mode, and make sure that your CPU power saving option is deselected.
I'm nearly certain that is the culprit.
Sent from my SM-N900P using Tapatalk
micmars said:
Go into power savings mode, and make sure that your CPU power saving option is deselected.
I'm nearly certain that is the culprit.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No such luck. Any other ideas?
mscooksey21 said:
No such luck. Any other ideas?
Click to expand...
Click to collapse
If you're on TouchWiz KitKat, MJ4 is a non-starter.
If power saving mode/adjust CPU isn't throttling your upper end, then an app must be setting it at boot.
The power saving mode, CPU option sets the upper end at 1.7 Ghz.
An app may be doing the exact same thing, taking control above all other settings for your device.
Sent from my SM-N900P using Tapatalk
micmars said:
If you're on TouchWiz KitKat, MJ4 is a non-starter.
If power saving mode/adjust CPU isn't throttling your upper end, then an app must be setting it at boot.
The power saving mode, CPU option sets the upper end at 1.7 Ghz.
An app may be doing the exact same thing, taking control above all other settings for your device.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Thats kinda what I imagined also. But I have no idea how to isolate it. I only hace one oc app on my phone. No performance tab in settings. And bear in mind ive already gone back and started from square one multiple times.
mscooksey21 said:
Thats kinda what I imagined also. But I have no idea how to isolate it. I only hace one oc app on my phone. No performance tab in settings. And bear in mind ive already gone back and started from square one multiple times.
Click to expand...
Click to collapse
There's got to be something writing the upper end voltage on boot.
You may have to go completely back to square one.
Sent from my SM-N900P using Tapatalk
micmars said:
There's got to be something writing the upper end voltage on boot.
You may have to go completely back to square one.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yeah. But I've already tried a full unroot, complete factory reset.
mscooksey21 said:
Yeah. But I've already tried a full unroot, complete factory reset.
Click to expand...
Click to collapse
In not a huge fan of wiping one's internal memory, but it seems the next logical course of action.
Either that, or factory reset first, then flash stock NC5 until you get official status, then and only then flash recovery and root.
No need for auto root package.
Sent from my SM-N900P using Tapatalk
micmars said:
In not a huge fan of wiping one's internal memory, but it seems the next logical course of action.
Either that, or factory reset first, then flash stock NC5 until you get official status, then and only then flash recovery and root.
No need for auto root package.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Okay. Could I factory reset then flash nc5 full restore via odin found in other post? Then how can I tell if its got official status?
mscooksey21 said:
Okay. Could I factory reset then flash nc5 full restore via odin found in other post? Then how can I tell if its got official status?
Click to expand...
Click to collapse
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
micmars said:
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Got it. Will report back soon.
micmars said:
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Okay so here's the update. I did a full un root return to stock, wiped data, and re rooted/ installed a game and it happened again. Frequencies reverted back to an even lower 1.4ghz almost instantly. I'm at a loss. It only happens when I start up a game. And I know it didn't do this at one point but I don't remember what was different or what i changed from back then.
mscooksey21 said:
Got it. Will report back soon.
Click to expand...
Click to collapse
Any ideas brotha?
micmars said:
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Any ideas brotha?
mscooksey21 said:
Okay so here's the update. I did a full un root return to stock, wiped data, and re rooted/ installed a game and it happened again. Frequencies reverted back to an even lower 1.4ghz almost instantly. I'm at a loss. It only happens when I start up a game. And I know it didn't do this at one point but I don't remember what was different or what i changed from back then.
Click to expand...
Click to collapse
That game is messing with your phone. I suggest going completely Stockish DeOdex NC5, adding Beast kernel, SetCPU, and try over clocking your device.
No games.
Sent from my SM-N900P using Tapatalk
micmars said:
That game is messing with your phone. I suggest going completely Stockish DeOdex NC5, adding Beast kernel, SetCPU, and try over clocking your device.
No games.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
It does it for any game I play. gta, mc4, mc5,rr3,etc..
mscooksey21 said:
It does it for any game I play. gta, mc4, mc5,rr3,etc..
Click to expand...
Click to collapse
I'm not knowledgeable about games and your inability to overclock your device.
I am quite clear on the process of elimination and gauging your ability to accomplish a task and rule out the root cause.
For now, stock, rooted, DeOdex rom, simple overclocking app, and kernel capable of doing same.
My suggestion stands.
No games, tell us if you're able to overclock your CPU at all.
Sent from my SM-N900P using Tapatalk
micmars said:
I'm not knowledgeable about games and your inability to overclock your device.
I am quite clear on the process of elimination and gauging your ability to accomplish a task and rule out the root cause.
For now, stock, rooted, DeOdex rom, simple overclocking app, and kernel capable of doing same.
My suggestion stands.
No games, tell us if you're able to overclock your CPU at all.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Will do. Thank you kindly.
When I had the "touchwiz dvfs" enabled none of my oc settings would stick. Just a thought if you could disable that maybe it'll help. There's an xposed module that allows for it.
Sent from my SM-N900P using xda premium
Related
I realized that when I using my phone for surfing the internet(using WI-Fi), the back of my phone(bottom) will heating up and it's hot. Did anyone having this problem too?
Yes, have same problem when I'm with stock ROM.
Sent from my GT-I9300 using Tapatalk 2
Yeah happens to me as well.
apisfires said:
Yes, have same problem when I'm with stock ROM.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
U mean that if I install another ROM this problem maybe will "dissapear"?
Fate_Hunter said:
U mean that if I install another ROM this problem maybe will "dissapear"?
Click to expand...
Click to collapse
Try use custom kernel 1st, read before you flashing any custom kernel or you updated your phone or not?
Sent from my GT-I9300 using Tapatalk 2
apisfires said:
Try use custom kernel 1st, read before you flashing any custom kernel or you updated your phone or not?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Yup my phone updated, if I install custom Kernel, when I unroot it and stock ROM can I still get back to my official Kernel version? And can I still get my warranty?
+1, sometimes it gets quite hot, sometimes not. Either has something to do with rooting or stock kernel is bad. Reboot fixes it temporarily here...
Of course it gets warm when you're doing things with the phone, it's what processors (and pretty much everything else in the world) does when doing work.
It's not a bug, nor a problem, just a thing that happens to everything.
High temperature means the CPU is working.
If you're surfing the WEB, it's quite normal with todays heavy usage of Javascript and animations on webpages. Custom kernels can reduce it somewhat by not going to full CPU speed (1.4GHz) directly, but this will naturally reduce the phone's "instant" performance.
I wouldn't say it gets heating up or hot. Just feel warmer. That's all. Nothing to worry about.
Sent from my GT-I9300 using xda app-developers app
Arsaw said:
I wouldn't say it gets heating up or hot. Just feel warmer. That's all. Nothing to worry about.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Ok, thx for this.
d4fseeker said:
High temperature means the CPU is working.
If you're surfing the WEB, it's quite normal with todays heavy usage of Javascript and animations on webpages. Custom kernels can reduce it somewhat by not going to full CPU speed (1.4GHz) directly, but this will naturally reduce the phone's "instant" performance.
Click to expand...
Click to collapse
this make sense too, cuz I reading novel via website.
Dan1909 said:
Of course it gets warm when you're doing things with the phone, it's what processors (and pretty much everything else in the world) does when doing work.
It's not a bug, nor a problem, just a thing that happens to everything.
Click to expand...
Click to collapse
not pretty like "gets warm" it getting hot too.(sometimes)
binaryanomaly said:
+1, sometimes it gets quite hot, sometimes not. Either has something to do with rooting or stock kernel is bad. Reboot fixes it temporarily here...
Click to expand...
Click to collapse
I juz wan to root my phone dun even bother to flash custom kernel, maybe i juz leave it there.Any way thx for you help.
My phone also gets hot even when downloading a file and display off!
IF YOU LIKE MY WORK, THANK ME BY THE BUTTON BELOW
I am in India not Malaysia
IF YOU LIKE MY WORK, THANK ME BY THE BUTTON BELOW
As soon as I shut my screen off, mobile data turns off.
I'm not getting email or FB notifications because of this and I've looked high and low to find a setting for this, but I'm not seeing it.
I'm not using any of the power saving settings.
Anyone have a clue what might be going on?
wolfgrrl said:
As soon as I shut my screen off, mobile data turns off.
I'm not getting email or FB notifications because of this and I've looked high and low to find a setting for this, but I'm not seeing it.
I'm not using any of the power saving settings.
Anyone have a clue what might be going on?
Click to expand...
Click to collapse
What rom are you using? Rooted?
Sent from my SCH-I545 using xda app-developers app
I haven't seen that on mine unfortunately. I wish mine would do that. It turns off instantly as soon as the screen goes off?
Sent from my SCH-I545 using Tapatalk 2
Mightycaptain said:
What rom are you using? Rooted?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Rooted on HyperDrive.
Evocm7 said:
I haven't seen that on mine unfortunately. I wish mine would do that. It turns off instantly as soon as the screen goes off?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
It does.
You can use Tasker to do this, Evo. State->display off->mobile data off.
Juice defender does it natively but I haven't seen a rom do it
Sent from my SCH-I545 using xda app-developers app
could be a bug in tasker? Is this new for you on rls10 or has it been going on for a while? Anyways, I would try and delete tasker and see if that works, then maybe install a different type of tasker...? just a thought
wolfgrrl said:
Rooted on HyperDrive.
Click to expand...
Click to collapse
Safestrap user? Use a different kernel. Sounds like a kernel settings or could be like one of those things that happens after installing a app or editing a certain combination of settings. Dirty flash the rom.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Safestrap user? Use a different kernel. Sounds like a kernel settings or could be like one of those things that happens after installing a app or editing a certain combination of settings. Dirty flash the rom.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Not on SS - MDK baseband.
wolfgrrl said:
Not on SS - MDK baseband.
Click to expand...
Click to collapse
Did you try flashing a different kernel or dirty flashing the rom.
Your sig says your probably on hyperdrive. This is odd behavior for a touch wiz rom. I have seen this on AOSP.
I would almost bet something has gotten stomped on.
Does this happen regardless of toggling airplane mode, or rebooting, or changing mobile network settings?
Mightycaptain said:
Did you try flashing a different kernel or dirty flashing the rom.
Your sig says your probably on hyperdrive. This is odd behavior for a touch wiz rom. I have seen this on AOSP.
I would almost bet something has gotten stomped on.
Does this happen regardless of toggling airplane mode, or rebooting, or changing mobile network settings?
Click to expand...
Click to collapse
I am on Hyperdrive - says that a few posts up, too.
I'm on stock optimized kernel on HD - and have ran that kernel since it's been available. I'm not one for switching around kernels - too buggy for me
What I've done is set Tasker to always keep mobile data on when at cell near work. This works and doesn't appear to have much of a detrimental effect on my battery life.
wolfgrrl said:
I am on Hyperdrive - says that a few posts up, too.
I'm on stock optimized kernel on HD - and have ran that kernel since it's been available. I'm not one for switching around kernels - too buggy for me
What I've done is set Tasker to always keep mobile data on when at cell near work. This works and doesn't appear to have much of a detrimental effect on my battery life.
Click to expand...
Click to collapse
Stock Optimized does run nice on HD.
Honestly I'd dirty flash the rom.
If it didn't clear up, I'd nandroid, back up apps and reflash.
Like you the best I can tell this is not normal behavior on HD so I'd say it has to do with your setup, how it flashed, what you installed, the tweaks that were done, etc...
But you also have a work around in place. I know sometimes for myself I cease to care about what the problem is or what has caused it if I have a viable work around.
I'd say your call all the way on this one.
Or heck if your a flashaholic like me, nandroid and flash something else to see if it happens there too. Eclipse TW 2.0 and Dirty Unicorns are my favorites right now, both running really solid, with exceptional battery life. DU if you like ultra customization like hyperdrive and like aosp as well. I like me some Hyperdrive as well, but those are the 2 that have my attention @ the moment.
Sorry not more help, but that is just one of those weird bugs you could chase forever.
Mightycaptain said:
Stock Optimized does run nice on HD.
Honestly I'd dirty flash the rom.
If it didn't clear up, I'd nandroid, back up apps and reflash.
Like you the best I can tell this is not normal behavior on HD so I'd say it has to do with your setup, how it flashed, what you installed, the tweaks that were done, etc...
But you also have a work around in place. I know sometimes for myself I cease to care about what the problem is or what has caused it if I have a viable work around.
I'd say your call all the way on this one.
Or heck if your a flashaholic like me, nandroid and flash something else to see if it happens there too. Eclipse TW 2.0 and Dirty Unicorns are my favorites right now, both running really solid, with exceptional battery life. DU if you like ultra customization like hyperdrive and like aosp as well. I like me some Hyperdrive as well, but those are the 2 that have my attention @ the moment.
Sorry not more help, but that is just one of those weird bugs you could chase forever.
Click to expand...
Click to collapse
Yeah, the workaround has me satisfied for now. I'm not really a flashaholic, and I like TW too much to even try AOSP. But thanks for your input! It's greatly appreciated.
Been having issues with my sensors locking up. I'm running stock rooted with a few xposed mods. I tried turning off all the mods and I still got it intermittently. Thought it was the gear manager for my Galaxy gear. Stopped having the issues after uninstalling the gear manager but it came back. When the auto rotation stops working I check the sensors with *#0*# and it shows the accelerometer is locked and occasionally other sensors fail like barometer and magnetic. A few searches find other phones with this issue sometimes gets fixed with a reflash. Anyone else have this issue?
Sent from my SM-N900P using Tapatalk
nacron said:
Been having issues with my sensors locking up. I'm running stock rooted with a few xposed mods. I tried turning off all the mods and I still got it intermittently. Thought it was the gear manager for my Galaxy gear. Stopped having the issues after uninstalling the gear manager but it came back. When the auto rotation stops working I check the sensors with *#0*# and it shows the accelerometer is locked and occasionally other sensors fail like barometer and magnetic. A few searches find other phones with this issue sometimes gets fixed with a reflash. Anyone else have this issue?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I just did a Google search of the topic, and I'm finding a full wipe and reinstall appear to be the agreed upon solution for many. I hate those types of answers, since doing it is a lot of work, and if it doesn't solve your issue, you have just wasted a ton of time for little benefit.
Have you tried uninstalling the Xposed modules and framework completely, rebooting, and wiping cache and dalvik partitions? That's the only other thing I can think of that could fully test your theory of it being an Xposed issue.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I just did a Google search of the topic, and I'm finding a full wipe and reinstall appear to be the agreed upon solution for many. I hate those types of answers, since doing it is a lot of work, and if it doesn't solve your issue, you have just wasted a ton of time for little benefit.
Have you tried uninstalling the Xposed modules and framework completely, rebooting, and wiping cache and dalvik partitions? That's the only other thing I can think of that could fully test your theory of it being an Xposed issue.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Haven't tried removing xposed but I have done cache wipes and fix permissions with no result. Is there a file that's being corrupted somewhere? Had a similar issue on my Galaxy S (original) and wipe fixed that also but in that case it was directly after a game crashed in landscape
Sent from my SM-N900P using Tapatalk
nacron said:
Haven't tried removing xposed but I have done cache wipes and fix permissions with no result. Is there a file that's being corrupted somewhere? Had a similar issue on my Galaxy S (original) and wipe fixed that also but in that case it was directly after a game crashed in landscape
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I have no idea as to whether the file is corrupted, as I'm not experiencing your issue. None of the items I read mentioned corrupted files and accelerometers. They did mention running script commands (ie, pinging the sensor to awaken it, but that's above my knowledge base).
I would recommend deleting all Xposed modules and framework if you want to properly test your theory. You can backup the settings on those and just reinstall the apps if it fixes it, and you are going to be reinstalling them anyway if you wipe data. It's the only option of which I can think.
Hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I have no idea as to whether the file is corrupted, as I'm not experiencing your issue. None of the items I read mentioned corrupted files and accelerometers. They did mention running script commands (ie, pinging the sensor to awaken it, but that's above my knowledge base).
I would recommend deleting all Xposed modules and framework if you want to properly test your theory. You can backup the settings on those and just reinstall the apps if it fixes it, and you are going to be reinstalling them anyway if you wipe data. It's the only option of which I can think.
Hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Removed the framework and uninstalled exposed, still getting sensor lockups. If reflashing works after removing all these mods, there has to be a system file that's messing up right? I uninstalled lux also and disabled greenify. It was working fine up until a month ago.
Sent from my SM-N900P using Tapatalk
nacron said:
Removed the framework and uninstalled exposed, still getting sensor lockups. If reflashing works after removing all these mods, there has to be a system file that's messing up right? I uninstalled lux also and disabled greenify. It was working fine up until a month ago.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Agreed, but I would speculate that the reason I found no answer beyond reflashing or pinging the sensors is that you could be searching for the proverbial needle in the haystack.
If wiping data and installing a new rom is the consensus solution, with no guarantee of success, then that is likely your only option.
It takes me hours to get a new rom up and running exactly the way I want, so I feel ya. At this point, I'm also out of answers.
If another can help, perhaps they can chime in.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Uninstalled a bunch of stuff and now the sensors lock up within 10 min of boot. Barometer no longer registers any data. I'll thinking this GN3 has bad hardware
Sent from my SM-N900P using Tapatalk
nacron said:
Uninstalled a bunch of stuff and now the sensors lock up within 10 min of boot. Barometer no longer registers any data. I'll thinking this GN3 has bad hardware
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
funny, after reading this thread, and seeing mic being stumped, i was wondering... do you have this issue on stock? old habit from my computer repair jobs which is rarely applicable to an android issue is "check HW first".
I'm running stock rooted, didn't flash any roms on this, believe me, I'm using all my troubleshooting resources. It's frustrating when a simple thing can mess up an entire device
Sent from my SM-N900P using Tapatalk
nacron said:
I'm running stock rooted, didn't flash any roms on this, believe me, I'm using all my troubleshooting resources. It's frustrating when a simple thing can mess up an entire device
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
So do you have recovery or otherwise trip Knox? If no, reflash via Odin or Mobile Odin the full rom (see Skunk Ape1 thread), reinject root, then you'll know.
I'd go a step further and aver that, based on what you've written, one way or the other reflashing stock MJ4 is the direction this is headed.
Ya take the phone back, it's out-of-the-box clean, and you're likely going to want to do it anyway. Ya don't take the phone back in the hope you find a fix, you still might flash stock MJ4 to eliminate a potential fix. It doesn't work, your phone is that much closer to being brought back for a return.
Unless there is a more targeted solution, this is perhaps your best course of action.
Sent from my SM-N900P using Xparent BlueTapatalk 2
It seems more stable now. It's super weird, for almost all today the barometer read 0 and the other sensors world lock up about 10 min after boot. This was after removing all the mods and clearing cache and fixing permission. We'll see how stable it is tomorrow.
Sent from my SM-N900P using Tapatalk
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
Hi guys,
Can safestrap roms allow for overclocking or underclocking (with the stock samsung s4 kernel)?
Raymondlikesroot said:
Hi guys,
Can safestrap roms allow for overclocking or underclocking (with the stock samsung s4 kernel)?
Click to expand...
Click to collapse
The stock kernel doesn't allow it. You can only use the stock kernel with Safestrap. So, no over/under clocking.
k1mu said:
The stock kernel doesn't allow it. You can only use the stock kernel with Safestrap. So, no over/under clocking.
Click to expand...
Click to collapse
Oh, thanks. Does that mean the Hyperdrive rom CPU settings will not work for me? Thanks! Sorry.. I'm new to andriod. It just that Im confused why hyperdrive would have that CPU settings feature if it doesn't work.
Raymondlikesroot said:
Oh, thanks. Does that mean the Hyperdrive rom CPU settings will not work for me? Thanks! Sorry.. I'm new to andriod. It just that Im confused why hyperdrive would have that CPU settings feature if it doesn't work.
Click to expand...
Click to collapse
I believe those settings only work for a phone with an unlocked bootloader. Those are settings best left alone unless you know what you're doing.
You can mess with some settings on the stock kernel but you shouldn't, Samsung uses a special hotplugging governor dependent on a lot more factors then your usual custom kernel, so unless you really know kernels inside and out then you'll only hinder your kernel. The app will also show you that you changed settings in the stock kernel that really can't be changed.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You can mess with some settings on the stock kernel but you shouldn't, Samsung uses a special hotplugging governor dependent on a lot more factors then your usual custom kernel, so unless you really know kernels inside and out then you'll only hinder your kernel. The app will also show you that you changed settings in the stock kernel that really can't be changed.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
It's been my experience that any developer worth his salt is using a kernel as customized for his ROM as he can make it. He might not get it exactly right the first time or two out the door, but he will get it right.
douger1957 said:
It's been my experience that any developer worth his salt is using a kernel as customized for his ROM as he can make it. He might not get it exactly right the first time or two out the door, but he will get it right.
Click to expand...
Click to collapse
There's a few AOSP developers who build ROMs and kernels but developers usually only work on one disclipine.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
There's a few AOSP developers who build ROMs and kernels but developers usually only work on one disclipine.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I guess I could have been a bit clearer. The developers I've followed over the years will work with the kernel guys to get one tweaked for their ROM. snuzzo over with Rezounds seemed to be a master chef of kernels.
douger1957 said:
I guess I could have been a bit clearer. The developers I've followed over the years will work with the kernel guys to get one tweaked for their ROM. snuzzo over with Rezounds seemed to be a master chef of kernels.
Click to expand...
Click to collapse
Got ya, times are different with this phone since only MDK users can even touch their kernel.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Got ya, times are different with this phone since only MDK users can even touch their kernel.
Click to expand...
Click to collapse
Unfortunately, several people seem to think that Safestrap allows them to flash custom kernels.
Well, in one sense, that's true. You can flash a custom kernel on a MK2/MJ7 phone. When the flash completes, you've bricked your phone and set the warranty void flag. But it did flash, right?
k1mu said:
Unfortunately, several people seem to think that Safestrap allows them to flash custom kernels.
Well, in one sense, that's true. You can flash a custom kernel on a MK2/MJ7 phone. When the flash completes, you've bricked your phone and set the warranty void flag. But it did flash, right?
Click to expand...
Click to collapse
And then the questions regarding Odin begin lol
Sent from my unknown using Tapatalk
Mistertac said:
And then the questions regarding Odin begin lol
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
gathering basic information would prevent 95% of what we see in bricking.....
decaturbob said:
gathering basic information would prevent 95% of what we see in bricking.....
Click to expand...
Click to collapse
When I get a new phone.. I hop on XDA and read read read then I download the factory images I WOULD need in case I need Odin to rescue me. Just seems like people don't ever get prepared in case something goes wrong. I suppose though people learn from mistakes... I sure have
Sent from my unknown using Tapatalk
Mistertac said:
When I get a new phone.. I hop on XDA and read read read then I download the factory images I WOULD need in case I need Odin to rescue me. Just seems like people don't ever get prepared in case something goes wrong. I suppose though people learn from mistakes... I sure have
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I got my phone on Verizon's Edge program. I can get a new phone every six months. I needed to be sure that I could get this thing back to stock before I rooted. I've been reading these threads since I got the phone in September... in fact, I read these threads plus those for the phones I was considering.
douger1957 said:
I got my phone on Verizon's Edge program. I can get a new phone every six months. I needed to be sure that I could get this thing back to stock before I rooted. I've been reading these threads since I got the phone in September... in fact, I read these threads plus those for the phones I was considering.
Click to expand...
Click to collapse
Good deal! I know there's a lot to look through on here and a lot to learn. Luckily there are stickies made that answer pretty much all those kind of questions. You'll be good.. You can always use Odin and get it back to complete stock.
Sent from my unknown using Tapatalk
Mistertac said:
Good deal! I know there's a lot to look through on here and a lot to learn. Luckily there are stickies made that answer pretty much all those kind of questions. You'll be good.. You can always use Odin and get it back to complete stock.
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Once I knew that... and they were able to root the Jelly Bean updates... I jumped in and did the deed myself.
Maybe if they were to sticky a "what you need to know, read this first" thread at the very top of each of the forums, it might cut down on the redundant questions.
douger1957 said:
Once I knew that... and they were able to root the Jelly Bean updates... I jumped in and did the deed myself.
Maybe if they were to sticky a "what you need to know, read this first" thread at the very top of each of the forums, it might cut down on the redundant questions.
Click to expand...
Click to collapse
There is one...
Sent from my SCH-I545 using XDA Premium 4 mobile app