Related
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
DarkBlaidd said:
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
Click to expand...
Click to collapse
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
I will likely switch back as I have a new hands free stereo for my car that I would like to legally take advantage of
let us know if you run into issues you will need to do a few searches.
sbiricuda said:
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
Click to expand...
Click to collapse
I'm a poor boy, so I am probably going to try and save a few bucks by using this method, which requires root.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
Click to expand...
Click to collapse
What was the GPS issue? Can you link to the fix please?
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
Click to expand...
Click to collapse
Cool, thanks for giving your opinion. How good is your battery life?
yohan4ws said:
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
Click to expand...
Click to collapse
Sounds like a good idea, I will do that.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
Click to expand...
Click to collapse
Noted, I will stay away from fastgsm. I think I am going to do this or GalaxSim Unlock.
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
Click to expand...
Click to collapse
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out. There is also a chance that Samsung will update us to Jellybean, they just released an update for the Galaxy S2, so it's possible.
let us know if you run into issues you will need to do a few searches.
Click to expand...
Click to collapse
Thanks! I believe I have done enough research to do what I want, so hopefully I won't make any dumb mistakes.
DarkBlaidd said:
Update from 2.3.6 to 4.0.4
Click to expand...
Click to collapse
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
Click to expand...
Click to collapse
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
DarkBlaidd said:
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out.
Click to expand...
Click to collapse
I'm in same boat here I guess. Just ordered a Glide, looking forward to having a physical keyboard again since my TP2 days. I was checking out the ROM options, found the link for "Stock UCLJ3 Rom" and it looks like that is the way go, other than maybe just staying stock... I need Bluetooth, Camera, GPS, and Tethering to work, so I guess I won't be messing around with anything fancy.
So don't do any OTA upgrade at all when I first get it out of the box? Just back it up, then root, and install UCLJ3 via CWM? Is this the best choice?
roothorick said:
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Click to expand...
Click to collapse
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
idenlover said:
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
Click to expand...
Click to collapse
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
roothorick said:
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
Click to expand...
Click to collapse
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
idenlover said:
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
Click to expand...
Click to collapse
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
roothorick said:
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
Click to expand...
Click to collapse
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
idenlover said:
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
Click to expand...
Click to collapse
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
roothorick said:
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
Click to expand...
Click to collapse
Awesome, thanks for the help!:good:
roothorick said:
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
Click to expand...
Click to collapse
Damn it, that really sucks. Thank you so much for letting me know that, you saved me some headaches.
Edit: I did some digging around to get a technical explanation of this issue and stumbled across some unexpectedly good news, I can use HSPA+ on T-MO, well halfway at least, I'm going to make a new post as a public service.
So I pulled down the OTA for my phone the other day, it installed perfectly fine. I'm fully stock.
First thing I noticed was that my NFC was no longer working. I can't turn it on in the settings, it sits there trying to turn on, but won't. I was working before the update as I have NFC tags in my cars setup to turn on Bluetooth and all that.
Has anyone had issues with NFC after the OTA? Note that I also performed a factory wipe to see if that might fix the issue with no luck!
Side question, how have others found battery life to be? So far to me, seems worse than before, but I'll give it a good week to see for sure.
Thanks!
This is why I think its such a phenomenal fail on AT&T's part for not providing the stock firmware! Normally I would suggest flashing the stock firmware via Odin. Im working on getting an Odin flashable built for you guys, so keep an eye out for it. Once its done and confirmed working, flash it and factory reset. Ill try to post something tonight.
took longer than expected(about a full minute) but both NFC and S beam turn on eventually, couldnt test it, i dont have another nfc capable device
Works for me. I could pass a picture between my wife's nexus4 to my s3 via nfc.
So no worries.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Anyone seen the firmware for the M9 that supports Marshmallow ? It's definitely out there as some users are running Marshmallow ROMs....
Any leaks ? Any news on official release ?
Is this what you are looking for?
http://www.htc.com/us/support/htc-one-m9/news/
No, that's not for Verizon plus it's a full ROM/RUU.
Sent from my HTC6535LVW using Tapatalk
Yeah, I have been wondering the same thing. I figured something would have got leaked by now. Or at least some info...
Sent from my HTC One M9
The Marshmallow ROM for Verizon's M9 is still in the testing stages. Based upon my current build, I'd guess late testing stages, but don't quote me.
hgoldner said:
The Marshmallow ROM for Verizon's M9 is still in the testing stages. Based upon my current build, I'd guess late testing stages, but don't quote me.
Click to expand...
Click to collapse
Oops! Sorry...
I believe Marshmallow firmware is only out for the dev / WWE devices.
VZW will most likely be the last variant to the update to MM, so don't hold your breath waiting on it.
FYI - I'm running the latest Candy6 (an AOSP-based Marshmallow ROM) on the most recent VZW firmware and it is running flawlessly. I actually thought I was enjoying sense until i went back to AOSP!
PrizmaticSmoke said:
FYI - I'm running the latest Candy6 (an AOSP-based Marshmallow ROM) on the most recent VZW firmware and it is running flawlessly. I actually thought I was enjoying sense until i went back to AOSP!
Click to expand...
Click to collapse
Is there a thread for that here at XDA, in the VZW section ? I've used CM-based ROMs for years but the only one I've seen for the M9 didn't have VZW support (yet).
The Venom team, and a few others, do have a test build for Verizon from HTC. However sharing this build would mean violating an agreement between said testers and HTC/Verizon. This, in turn, would mean no more early test builds would be released to them. This is not what any of us want.
You, and I, have Verizon M9's. We understand our devices are not the same as International/Developer... and thus we wait, patiently. Our turn will come.
hallstevenson said:
Is there a thread for that here at XDA, in the VZW section ? I've used CM-based ROMs for years but the only one I've seen for the M9 didn't have VZW support (yet).
Click to expand...
Click to collapse
Yep there's an XDA thread, but it's over in the general M9 section, here ya go: http://forum.xda-developers.com/one-m9/development/rom-t3265048
The thread title still states it's CM based, but they recently rebased on AOSP for Marshmallow. Most recent build is labeled as an alpha, but it's working great for me.
So to confirm, Verizon is actually testing a marshmallow build?
Aganar said:
So to confirm, Verizon is actually testing a marshmallow build?
Click to expand...
Click to collapse
Of course. Have been for a while. No release date though.
PrizmaticSmoke said:
The thread title still states it's CM based, but they recently rebased on AOSP for Marshmallow. Most recent build is labeled as an alpha, but it's working great for me.
Click to expand...
Click to collapse
I'm working my way through that thread. When it was first started, it appeared that there were a few critical things not working properly, like non-system apps being unable to read the external SD card. When they switched to AOSP, it seemed to improve things, but it's still not clear from that thread.
So..... since you're using it and also on Verizon, what doesn't work ? I've seen people release ROMs with non-working cameras, can't make phone calls, and other crazy s**t. I'm all for helping if I can, but I still need a functioning phone !!
I've got the ROM zip and GAPPS downloaded on my phone ready to go....
hallstevenson said:
I'm working my way through that thread. When it was first started, it appeared that there were a few critical things not working properly, like non-system apps being unable to read the external SD card. When they switched to AOSP, it seemed to improve things, but it's still not clear from that thread.
So..... since you're using it and also on Verizon, what doesn't work ? I've seen people release ROMs with non-working cameras, can't make phone calls, and other crazy s**t. I'm all for helping if I can, but I still need a functioning phone !!
I've got the ROM zip and GAPPS downloaded on my phone ready to go....
Click to expand...
Click to collapse
Honestly everything is working great for me on the build from 01-08, nothing is broken that i can tell. Data, wi-fi, gps, bluetooth, camera, flashlight, SD card, calls, texts, all are good to go. I haven't tested IR blaster as I don't use it for anything. And you will not have advanced calling/VoLTE available as far as I'm aware. But all good otherwise. :good:
I did see another VZW user reporting some issues on the same build like not getting a GPS lock, and their network incorrectly showing as Sprint and losing service whenever they drop to 3g or 1x coverage. But I have not had any GPS issues myself, and can't speak to the coverage issue as I live and work in an area with pretty solid LTE coverage and have had no problems.
I saw the one report of a GPS issue but multiple people saying they have no problem, so I brush off that "issue". I do have advanced calling enabled but no one I call does, so it doesn't matter. If I'm not mistaken, both ends need it enabled (?). Either way, it won't stop me.
Sent from my HTC6535LVW using Tapatalk
The 01/08 build is the one I have downloaded too.
Sent from my HTC6535LVW using Tapatalk
hallstevenson said:
I saw the one report of a GPS issue but multiple people saying they have no problem, so I brush off that "issue". I do have advanced calling enabled but no one I call does, so it doesn't matter. If I'm not mistaken, both ends need it enabled (?). Either way, it won't stop me.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I never had a gps lock when I went from sense to aosp. That was my problem. Switching from LTE to 3g and 1x because of fringe coverage , and having it read sprint pcs was just odd. Other than that, it's a great rom
No problem with GPS here. I just tried it for the first time with Google Maps and it showed my location spot-on. I also tried GPS Status and got a fix on 15/20 satellites (inside).
hallstevenson said:
No problem with GPS here. I just tried it for the first time with Google Maps and it showed my location spot-on. I also tried GPS Status and got a fix on 15/20 satellites (inside).
Click to expand...
Click to collapse
locks super quick too. Once i went and flashed a sense rom, got my lock, then went back to aosp, all was good. Do me a favor, download 4g switcher from the play store (its got a red power button logo). Since your in good 4g coverage. in this app, goto the dropdown menu that lists the radio bands (CDMA/EVDO/GSM/WCDMA/LTE Auto is set by default) select CDMA auto (PRL) (this will force you into 3g mode). Then see if you see either 3107 or sprint PCS as your coverage. Then try to browse to a webpage or something on the 3g, i couldnt get data to work in that mode whatsoever. Then at least ill know if im sane. Thank you
Don't need an app for that - just dial "*#*#4636#*#*"
It shows "Sprint PCS" when I switch to 3G mode. I'm not going to chance any data roaming charges though... Sorry
Did you toggle Settings, Cellular Networks, Data roaming to 'on' ? It's off by default. That could be why you couldn't browse on 3G.
Would like to ask if anybody experienced the issue "fingerprint hardware not available"?
There's a thread in z5 forum:
http://forum.xda-developers.com/xperia-z5/help/fingerprint-hardware-available-t3354800/page11
but seems liker a common problem for whole z5 series...
There are several possible solutions there but nothing works for me. And there is no clear symptom, when is occurs...
Perhaps can anybody share experience?
I have this problem too, im on latest romaur and with the aur kernel and i loose the fingerprint Thing after about 30mins after a reboot. I also get an video error from Youtube so i vant watch videos
Goto google player service and disable body sensor from permission, if the problem persists then downgrade google play service to stock.
kiritoxda said:
Goto google player service and disable body sensor from permission, if the problem persists then downgrade google play service to stock.
Click to expand...
Click to collapse
Didn't help and Google Play services gets updated automatically again...
I have recently been having the same issue while running v4.1 of ROMAUR, I never upgraded to v4.2.1 and it got considerably worse in the last two weeks. Initially it would happen once or twice a month but then, like you, I started experiencing it every 30 minutes and nothing would solve that issue.
For over a week now I have not had that issue, that is because I have gone back to a stock ROM of 253 and used a stock kernel that simply has recovery and drm fixes. I am rooted and running xposed, problem is with Auras work, whatever he is doing to his ROM is breaking the functionality of the sensor.
Sent from my E6853 using Tapatalk
Mobfigurz said:
I have recently been having the same issue while running v4.1 of ROMAUR, I never upgraded to v4.2.1 and it got considerably worse in the last two weeks. Initially it would happen once or twice a month but then, like you, I started experiencing it every 30 minutes and nothing would solve that issue.
For over a week now I have not had that issue, that is because I have gone back to a stock ROM of 253 and used a stock kernel that simply has recovery and drm fixes. I am rooted and running xposed, problem is with Auras work, whatever he is doing to his ROM is breaking the functionality of the sensor.
Sent from my E6853 using Tapatalk
Click to expand...
Click to collapse
I doubt that, because I had been using Romaur 4.2.1 since a while and the sensor worked fine for a really long time until about 2 weeks ago.
Can you share your Google Play Services version?
CrisperNeO said:
I doubt that, because I had been using Romaur 4.2.1 since a while and the sensor worked fine for a really long time until about 2 weeks ago.
Can you share your Google Play Services version?
Click to expand...
Click to collapse
I do not doubt it, I have seen first hand that it was an issue when I was running ROMAUR and now I am not having a single issue. I updated all my apps, including Google apps via apkmirror, so the same Play Services was running on both ROMAUR and my stock 253, yet not a single issue on stock, so explain that one.
Sent from my E6853 using Tapatalk
---------- Post added at 12:26 PM ---------- Previous post was at 12:23 PM ----------
Oh yeah, when I rebooted my phone on stock, it actually boots back up first time, does not act up and loop either like it did on ROMAUR and I have all the same apps running, including Xposed and Viper.
Sent from my E6853 using Tapatalk
Just to report back:
In another thread in Z5 forum (http://forum.xda-developers.com/showpost.php?p=68299976&postcount=165) there was a solution proposed, and it works for me so far:
Try renaming these files on /system/etc/firmware/
tzwidevine.b00 -> tzwidevine.b00.bak
tzwidevine.b01 -> tzwidevine.b01.bak
tzwidevine.b02 -> tzwidevine.b02.bak
tzwidevine.b03 -> tzwidevine.b03.bak
tzwidevine.mdt -> tzwidevine.mdt.bak
Then reboot.
Click to expand...
Click to collapse
This seems really to be fix. Havent got the fingerprint problem ever since (should have already had several times, based on the experience in the last weeks). It also solves the youtube video issue.
In addition I found a thread on this on Z2 forum: http://forum.xda-developers.com/xper...t3290793/page2
Seems to be a bug regarding unlocked bootloader or similar. Don't know what the files really do. But based on knowledge that people solved this with newer .253 ROM and kernel (rootkernel), perhaps SONY has already done something there. Perhaps anybody can check his .253 ROM?
Anyway, thanks to @depotjam.
Hello, are users experiencing reboot issues after nougat update??
Please clarify it, cause I am planning to buy this phone
arjuntsgowda said:
are users experiencing reboot issues after nougat update? Please clarify it, cause I am planning to buy this phone
Click to expand...
Click to collapse
Me not. Don't know about other users
Any more reviews from other people,it would help me properly decide to buy this phone or not
Can't speak for stock ROMs but I've got no issues with the phone at all, no heating like people keep moaning about too... Happily running RR
arjuntsgowda said:
Any more reviews from other people,it would help me properly decide to buy this phone or not
Click to expand...
Click to collapse
I'm using the latest Zui 2.5.104 ST since last two months, everything is stock and I haven't faced any random reboot issue. May be issue was there with first/earlier version, but no issue with the latest update. VoLTE also works perfectly and never drops (Just that "HD" sign grts vanished sometimes, but VoLTE still works). You can go ahead and buy this phone. Btw, issues like random reboots, heating can be due to individual usage, so make sure you don't overheat the phone, or use bad apps.
arjuntsgowda said:
Hello, are users experiencing reboot issues after nougat update??
Please clarify it, cause I am planning to buy this phone
Click to expand...
Click to collapse
No such issue after update
To be on the safe side just factory reset the phone few times after update....it helps to get rid of such issues.
On 2.5.104 ST, every time I unlocked my phone, screen flickered and all radios disconnected. Sometimes it would immediately freeze, go to black screen, then LED lit up, requiring me to hold power button down to reboot the phone. Sometimes this happened, but not immediately. Sometimes radios would recover and phone would continue to function. Sometimes cellular radios recovered, but wifi did not, and even toggling airplane mode didn't fix it so I had to reboot. Nougat was quite a mess on my phone and that's even after factory reset many times. Several on zukfans.eu site had similar issues.
I don't think it was a hardware issue, because downgrade to 2.0.133 ST (Marshmallow) works perfectly.
GnatGoSplat said:
2.5.104 ST, 2.0.133 ST
Click to expand...
Click to collapse
works as usual on my phone.
sergsinger said:
works as usual on my phone.
Click to expand...
Click to collapse
Do you have dual SIMs installed? Connecting to 5GHz wifi or 2.4GHz?
Trying to figure out what is different about my situation.
GnatGoSplat said:
SIMs installed? Connecting to 5GHz wifi or 2.4GHz?
Click to expand...
Click to collapse
One. 2.4.