I recently tried to upgrade to CM 12.1 for my T Mobile S4 being used on the Wind Network in Canada. But when ever the screen turns off it will lose connection to the cellular network, when i turn it back on i get a bunch of notifications, sometimes it will buzz 2 or 3 times for the same notification. I tried searching but can't find anything pertaining to this. i also tried other builds, Slim LP, Resurrection and the GPE but still all show the same issue
Has anyone seen this before let alone know how to fix it?
icewolf293 said:
I recently tried to upgrade to CM 12.1 for my T Mobile S4 being used on the Wind Network in Canada. But when ever the screen turns off it will lose connection to the cellular network, when i turn it back on i get a bunch of notifications, sometimes it will buzz 2 or 3 times for the same notification. I tried searching but can't find anything pertaining to this. i also tried other builds, Slim LP, Resurrection and the GPE but still all show the same issue
Has anyone seen this before let alone know how to fix it?
Click to expand...
Click to collapse
lollipop is known to be buggy with network on our device. Sometimes I even get sim card removed message and after a couple dozen reboots will my sim be recognized again. I suggest to stick with the rom that works flawlessly for you and skip lollipop, for now atleast.
And that's why I only root my phone, and run it stock. Roms always do this, no matter what anyone says. And I said this in my other thread, but ppl try to day otherwise. I told you guys lollipop roms are buggy for our phones. 4.4.4 for the win. Just uninstall bloatware and ur good to go.
Sent from my SGH-M919 using XDA Free mobile app
epicboy said:
lollipop is known to be buggy with network on our device. Sometimes I even get sim card removed message and after a couple dozen reboots will my sim be recognized again. I suggest to stick with the rom that works flawlessly for you and skip lollipop, for now atleast.
Click to expand...
Click to collapse
So it's not just me with the SIM Card problem either. I got that so many times on lollipop and I tried to flash a 4.4.4 ROM again and it would still give me the SIM Card not detected. I was going to get it repaired again and I flashed stock MetroPCS tar and it got rid of the problem. I don't knowant if I would root again and just flash a 4.4.4 ROM and use xposed. I don't want that SIM Card problem to happen again. It's annoying.
j21098 said:
So it's not just me with the SIM Card problem either. I got that so many times on lollipop and I tried to flash a 4.4.4 ROM again and it would still give me the SIM Card not detected. I was going to get it repaired again and I flashed stock MetroPCS tar and it got rid of the problem. I don't knowant if I would root again and just flash a 4.4.4 ROM and use xposed. I don't want that SIM Card problem to happen again. It's annoying.
Click to expand...
Click to collapse
In my experience. After flashing a kitkat rom and rebooting a couple times the problem is fixed.
epicboy said:
In my experience. After flashing a kitkat rom and rebooting a couple times the problem is fixed.
Click to expand...
Click to collapse
I stayed with it for about a week before flashing stock firmware. Rebooted many times while I had it and it still happened. I've been on stock firmware for over 3 weeks and no problem at all.
j21098 said:
I stayed with it for about a week before flashing stock firmware. Rebooted many times while I had it and it still happened. I've been on stock firmware for over 3 weeks and no problem at all.
Click to expand...
Click to collapse
In my experience it worked. I was on a touchwiz kitkat rom. Were you on AOSP kitkat when it still didn't wirk?
epicboy said:
In my experience it worked. I was on a touchwiz kitkat rom. Were you on AOSP kitkat when it still didn't wirk?
Click to expand...
Click to collapse
No, I tried MD 1.3 and the stock T-Mobile ROM. Also forgot to mention I had a really bad problem with the Play Store. I couldn't install anything at all. I'd always get error 905 and this other number I forgot. No matter what I tried I couldn't get a fix, clearing cache, data, dalvik, uninstalling updates, reboots after each one and nothing fixed. Stock Firmware seemed to fix all the problems I had
Related
I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules
Hi guys,
I have had the s2,s3,galaxy nexus,original note and i am used to flashing and modifying,but i have a serious issue with the note 2.
The problem is whenever i flash AOSP rom(cm,aokp,pa) my wifi would not connect.It shows the name of the network and when i click conenct nothing happens.Flashing back TW rom fixes it,wifi works like a charm. I've done full wipes but it doesn't seem to resolve the issue.I tried different kernels,but that doesn't help either.
So I am stuck at TW roms and i hate that.Anyone has any ideas?
You can try options 2 and 3 from this thread.
Thanks for your reply,but i tried this and it didn't solve my problem.
Anyone?
spookhc said:
Anyone?
Click to expand...
Click to collapse
I Have the same problem...
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Primokorn said:
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Click to expand...
Click to collapse
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
With my Note2 this is not the solution. I've tried everything. What you said, move file "pit" ..... but nothing. I can not connect wifi. The connection does not appear region Spain, and have opted to choose europe, but neither. I do not know to do. CM 10.1 also does not work WIFI. In Stock ROM or Custom ROM works fine fine, but in ROM CM 10.1, 10.2, AOKP don't work.
spookhc said:
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
Click to expand...
Click to collapse
Hi there!
My WiFi seems to disconnect and then reconnect every 5 to 10 minutes or so, after I have installed different KitKat ROMS. It happens with different ROMS.
My girlfriend also has a Note 2, and I also updated her phone with a KitKat ROM (Android Revolution HD), but her's doesn't disconnect at all.
You guys know what's happening here? I did flash latest MJ5 bootloader, but it says failed. Then I also flashed the WiFi Fix. In Download mode, Phone says, KNOX VOID: 1.
Thanks in advance.
Anyone?
It happens a lot now..sometimes. It seems a 4.4.2 rom issue in combination with my router.
Laptop doesn't disconnect, but phone of my girlfriend does as well. On her phone I also installed a 4.4.2 rom. Different one though.
dmxl said:
Anyone?
It happens a lot now..sometimes. It seems a 4.4.2 rom issue in combination with my router.
Laptop doesn't disconnect, but phone of my girlfriend does as well. On her phone I also installed a 4.4.2 rom. Different one though.
Click to expand...
Click to collapse
dmxl said:
Hi there!
My WiFi seems to disconnect and then reconnect every 5 to 10 minutes or so, after I have installed different KitKat ROMS. It happens with different ROMS.
My girlfriend also has a Note 2, and I also updated her phone with a KitKat ROM (Android Revolution HD), but her's doesn't disconnect at all.
You guys know what's happening here? I did flash latest MJ5 bootloader, but it says failed. Then I also flashed the WiFi Fix. In Download mode, Phone says, KNOX VOID: 1.
Thanks in advance.
Click to expand...
Click to collapse
Another user from Phoenix ROM is reporting the same. WiFi keeps dropping on his phone. Which ROM did you flash on your gf's phone ? And which ROM are you using ? The guy I'm talking about first flashed a stock KK ROM and then Phoenix ROM so he's on the newest boot loader already
Sent from my GT-N7100 using Tapatalk
singhpratik87 said:
Another user from Phoenix ROM is reporting the same. WiFi keeps dropping on his phone. Which ROM did you flash on your gf's phone ? And which ROM are you using ? The guy I'm talking about first flashed a stock KK ROM and then Phoenix ROM so he's on the newest boot loader already
Click to expand...
Click to collapse
Hi, thanks for replying! My girlfriend (still) uses the Android Revolution 30, I use the SupremeKat. I plan to install SupremeKat on hers as well, after mine is configured and all.
Before that we both had Android Revolution version 19, which is still Android 4.1.2 I think. No WiFi problems at that time....
Any idea who it was that reported the same issues?
dmxl said:
Hi, thanks for replying! My girlfriend (still) uses the Android Revolution 30, I use the SupremeKat. I plan to install SupremeKat on hers as well, after mine is configured and all.
Before that we both had Android Revolution version 19, which is still Android 4.1.2 I think. No WiFi problems at that time....
Any idea who it was that reported the same issues?
Click to expand...
Click to collapse
It was @Puffin617 he flashed the official stock ROM first and then flashed the custom 4.4 rom called Phoenix ROM and he reported that the WiFi keeps dropping. I've asked one of the users on xda who has a bit more knowledge about such things that what could be causing this cause many users are complaining about battery drain and frequent WiFi drop not sure why is it only affecting a few phones when people have flashed the same stock ROM and your case a custom ROM. If I find anything useful to share I'll get back at you. Perhaps switch custom ROM? Give Dr ketan's version 7 a shot and see if that removes the WiFi issue. Good luck
Sent from my GT-N7100 using Tapatalk
I have same problem. Stock rom - not root. It drops and reconnect every 2 or 3 minutes.
So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated
Was the problem present on the stock ROM?
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.
Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much
Hey there,
I was wondering if anyone could maybe figure out this issue which has been troubling me for about a month or so.
I have ran marshmellow before absolutely fine however decided to flash lollipop back on my phone as I felt the battery life was better.
Anyway, whenever I come back to any version of the Marshmallow roms, i'm greeted with not being able to set a lockscreen (lockscreen has crashed), I cannot uninstall apps without a force reboot and I cannot access the security settings on the phone without it crashing.
I've tried wiping pretty much everything and it seems to be on all roms. I've tried multiple from fresh.
Any ideas?
Much Appreciated
Issue fixed, flashed a new KDZ and seems to be working
milpan said:
Issue fixed, flashed a new KDZ and seems to be working
Click to expand...
Click to collapse
DO you know if flashing back works on verizon? I loved this phone until MM...
Also any insight on the steps, did you just use LGUP and get the KDZ off Sotragecow?
zwalk said:
DO you know if flashing back works on verizon? I loved this phone until MM...
Also any insight on the steps, did you just use LGUP and get the KDZ off Sotragecow?
Click to expand...
Click to collapse
@zwalk - sorry for the late response. I did exactly that. Seemed to fix everything. I recommend trying 20f or 20g if it works with your phone as it seems to fix battery issues.