[Q] Wifi Dropping on AOSP/CM ROMs - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...

oscooter said:
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
Click to expand...
Click to collapse
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.

ak29 said:
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
Click to expand...
Click to collapse
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)

oscooter said:
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
Click to expand...
Click to collapse
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.

ak29 said:
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
Click to expand...
Click to collapse
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.

oscooter said:
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
Click to expand...
Click to collapse
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.

Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.

I've been running CM10 nightlies with the CM10 kernel since late November and haven't had any issues with WiFi. I am on my 2nd GS3, first one returned due to phone speaker (not the speakerphone on the back) and on that one my WiFi was sketchy. Not sure if it was a hardware problem, or CM10 merged a fix close to when I swapped out devices. Either way, I use the latest twrp recovery flashed from GooManager and Formula84 10/12 Gapps. I update daily with the CM Updater, and haven't had any issues other than what is already reported to be a bug on CM (which in all reality is, nothing, since I NEVER use Bluetooth)
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...

goodtimes50 said:
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
Click to expand...
Click to collapse
Avoid poor connections is always unchecked for me. I also make sure wifi is set to never sleep.
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
thacounty said:
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
Click to expand...
Click to collapse
I'm using the linksys e4200v2 router. Never had any issues with any of my devices except after I flash AOSP/AOKP based roms. I have 8 devices connected wirelessly with no issues.

My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app

oscooter said:
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I just tried two roms (liquid smooth and tasks aokp). Had wifi issues with both of them after reboot. I decided to try two custom kernels (underwear and ktoonsez). Still experienced wifi saying not in range. The issue seems to be with the latest cm base which is used in all AOSP and AOKP roms. I hope this issue is fixed with the new cm 10.1 base. I guess I'll be stuck using only touch wiz roms now.

Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.

ak29 said:
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Click to expand...
Click to collapse
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app

ak29 said:
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
Click to expand...
Click to collapse
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
guitarpunk8403 said:
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app

oscooter said:
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
No prob. I'm finally able to enjoy tasks aokp now that I got the wifi issue solved with using smart wifi toggler. It's a great rom, with tons of features and customizations.

Related

Anyone else having complete "fail" on latest CM7?

Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Haven't had any issues gonna try the latest stable build of cm7 I always use amon 2.3 for a full wipe a lot of the time that fixes issues for people .
ginjeet said:
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Click to expand...
Click to collapse
Well, n66 after a day on tiamets 4.0.1 kernel seems stable. Let me know how the undervolting goes. I tried vipers v2 and it started freezing after about 20 minutes. The -50 script did the same thing. -25 actually worked out pretty well right up until this morning. My alarm went off and I hit snooze and it threw it into constant reboot.
I'm going to run just n66 with 4.0.1 all day no script and see what I get. I dunno what has changed for my phone but it seems to have leveled out. *knocks on wood*
Sent from my PC36100 using XDA Premium App
So far on the 7.0.3.1 build GPS works like a champ market mms and everything camera and such you tube app plays everything on hq. Picky at time at times tho on HQ.
blizzard1017 said:
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
Click to expand...
Click to collapse
Are you u using amon 2.3
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Update* just received an mms with 7.0.3.1 and it worked
A1Lonestar said:
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Click to expand...
Click to collapse
What recovery are you using man? Anything better using nightly 66 advantage wise?
reaper24 said:
What recovery are you using man? Anything better using nightly 66 advantage wise?
Click to expand...
Click to collapse
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
teh roxxorz said:
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
Click to expand...
Click to collapse
Well, I just went back to Koni's..............again. I was running 66 all morning with 4.0.1 and no script and while everything was working ok the battery was draining somewhat fast. It wasn't a wake issue and I even tested an hour or so on PRI177 with the same results. The battery was tolerable because Mondays are really busy for me so I know on a normal day I wouldn't complain but my data connection still drops to 1x a lot and I think the drain might have something to do with the connection searching constantly.
If I can get that Viper script moving along and figure out the data and signal drop I think I am getting somewhere.
@reaper, yes I am using Amon Ra latest and greatest.
Off topic, I love the Nand backup option. My Vibrant only uses Clockwork and even then it was not fully functional. Some of the basic options would brick the phone.
The latest cm7 stable works great.
Sent from my PC36100 using XDA App
flashing back to sense after "GPS FIX"
I have a few issues with CM7 and I keep switching back to Sense roms because they have been stable. If I do the GPS fix and stay on CM7 will my GPS still work when and if I go back to a Sense ROM?

Better JB stock rom? Black or Jelly?

coming from cm10 nightlies, i want stock back. i miss some of the cool features that came with the phone.
what am i going to be missing from going from asop to stock?
what rom seems to be the most stable with decent battery life?
I have the exact opposite question, oddly enough. I see that CM10 nightlies are in a somewhat unstable state, as they are nightlies. I cant complain about their instabilities because of this, and that is fine. Some people say they are stable, Others tell me that since they are nightlies I shouldnt be using them as daily driver, and yet others (those posting in the thread) are having bugs and issues of the exact sort that I dont want to be encountering (like not being able to get wifi working, or google account sync issues).
So how did you figure out which nightly to put on your phone, especially when the preferred install method is full wipe/clean install?
I am also interested in the jellybean stock rom question. I dont really care for updates all the time but I'm growing tired of the random quirks and shortcomings of the tmobile stock firmware very quickly. For example, how the screen doesnt automatically turn on when you move the phone away from your face during a call, even though it does automatically turn off.
Xquisite rom by wicked. Look the the development section. He updates when he finds fixes and improvement. Plus a lot of good tweaks
Sent from my SGH-T999 using xda app-developers app
Does Xquizit include debloating? From reading the description, it looked like the goal was to remain as close to 100% stock as possible. I didnt see any mention of removal of the bloat that came with the phone.
shrimants said:
I have the exact opposite question, oddly enough. I see that CM10 nightlies are in a somewhat unstable state, as they are nightlies. I cant complain about their instabilities because of this, and that is fine. Some people say they are stable, Others tell me that since they are nightlies I shouldnt be using them as daily driver, and yet others (those posting in the thread) are having bugs and issues of the exact sort that I dont want to be encountering (like not being able to get wifi working, or google account sync issues).
So how did you figure out which nightly to put on your phone, especially when the preferred install method is full wipe/clean install?
I am also interested in the jellybean stock rom question. I dont really care for updates all the time but I'm growing tired of the random quirks and shortcomings of the tmobile stock firmware very quickly. For example, how the screen doesnt automatically turn on when you move the phone away from your face during a call, even though it does automatically turn off.
Click to expand...
Click to collapse
The latest nightly
Sent from my SGH-T999 using xda premium
I'm using liquidsmooth its fast, looks very good and amazing battery life
Sent from my SGH-T999 using xda app-developers app
Flashed latest CM10 nightly, must have been a corrupt download or something because now it flashes the "samsung" logo for a split second and then I get a black screen. I can get back into recovery, but I cant mount external SD card or internal storage. All it says is "usb device not recognized". All drivers are installed correctly, so I dont know wtf is going on. This requires further research, preferably after dinner.
I've been using the nightly CM10 for the past 3 weeks and I've had little to no issues. (And yes, I update daily.) The only reason I've considered going back to stock is for *possibly* better battery life. WiFi, camera, Google accounts sync, and everything have worked for me from the start.
Sent from my SGH-T999 using xda premium

Strange issues after flashing a ROM

so i recently got my Note 2, and i love it. i decided to go ahead and start tinkering with it, but i'm having some strange issues. i've searched the forums, and havent found any concrete answers. after i flashed a new rom, all my sensors are out of whack, and i only have intermittant bluetooth connectivity. i also seem to have issues with cell signal strength. if i go down to one bar of LTE, it gets slow as hell.
i've tried several different ROMS. JellyBam, JellyBeer, and i'm currently on Paranoid Android, running SPB 3D shell. none of my sensors are back online, and i miss my auto rotate. should i try a new kernal or new radio? i also seem to have a ton of freezes and force closes when running the Deus Ex theme.
any body have any ideas? i'm almost tempted to go back to bone stock...
thanks for your help guys.
oh, and if it matters, ive been using the team win recovery instead of CWM.
Try the newer Jellybeer or Jellybam, It should fix your sensors and BT
i was using the latest JellyBeer, and they still didnt work, i'll try JellyBam again tonight and see if it helps. i heard someone say something about the Perseus kernel, but that its a touchwiz only kernel. any other ideas?
Why not go completely stock ,that will fix your sensors,then continue on flashing?

wifi doesnt stay on when rebooting on TW roms

so, I havent ran a TW rom in ages, and I installed Clean rom and Ammosphereium roms.
everything works fine on both of them, but when I reboot, my wifi has to be manually turned on every time, on both of these roms..
this never happens on an AOSP roms, and I dont remember if it happenned before when I ran TW roms all the time...
anyone else see this happen, or just something goofy with my hardware?
thanks!
wase4711 said:
so, I havent ran a TW rom in ages, and I installed Clean rom and Ammosphereium roms.
everything works fine on both of them, but when I reboot, my wifi has to be manually turned on every time, on both of these roms..
this never happens on an AOSP roms, and I dont remember if it happenned before when I ran TW roms all the time...
anyone else see this happen, or just something goofy with my hardware?
thanks!
Click to expand...
Click to collapse
Weird I don't have this issue...
Have you tried on more than one router?
Are you clean flashing?
yep, always clean flashing, and, I have only tried it on my home router, which works just fine for every other thing that I do...
weird, because every AOSP rom does NOT have this issue for me, just the Touch Wiz stuff..
wase4711 said:
yep, always clean flashing, and, I have only tried it on my home router, which works just fine for every other thing that I do...
weird, because every AOSP rom does NOT have this issue for me, just the Touch Wiz stuff..
Click to expand...
Click to collapse
Could be an issue with the wifi drivers and your router.
The ones from aosp would be different from the tw ones.
Try another router if you get the chance, or you could try entering static ip settings to see if that solves the issue
thanks for the suggestions, bro! :good:
I'm sure I will be back on AOSP shortly anyways; TW is just too laggy for me, after being spoiled by the great AOSP roms the Dev's have been cooling up..
wase4711 said:
thanks for the suggestions, bro! :good:
I'm sure I will be back on AOSP shortly anyways; TW is just too laggy for me, after being spoiled by the great AOSP roms the Dev's have been cooling up..
Click to expand...
Click to collapse
No problem man!
I don't find tw laggy at all though, plus I use so many features that I wouldn't be able to live without.
Spen, multiwindow, etc..
I was an AOSP junkie on all my other phones.
This one in actually liking tw. Plus the battery life on tw roms is insane
where I really miss TW roms is when I use my BT headsets to make calls; on TW, you get s-voice, which is great for initiating calls with one push of your headset; I have yet to find an app that does this with AOSP..they always activate the "dialer" which doesnt do squat...

[Q] Random reboots and lock ups (memory leak?)

Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app

Categories

Resources