Related
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Wexberg said:
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Click to expand...
Click to collapse
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
DeadlySin9 said:
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
Click to expand...
Click to collapse
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Wexberg said:
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Click to expand...
Click to collapse
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
DeadlySin9 said:
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
Click to expand...
Click to collapse
Wexberg said:
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
Click to expand...
Click to collapse
I don't know why that would work. At this point I'm not sure what else you could do. I know I used to have WiFi issues after some flashes with my Inspire but i never really had a fix even then.
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Been there, done that.
It's not a hardware problem. It is, I believe, problems with the restrictive 4.3 update not playing nicely with some system settings. In short your system drivers or configuration settings are getting messed up to to bugs in how Knox and the bootloader are interacting with the modem.
I had your exact symptoms after installing certain custom ROMs, also noted that the problem could be temporarily "fixed" if the boot process was interrupted or by specific sequences of modem changes. The situation is not helped by Bell being more restrictive than other Canadian carriers e.g. Rogers, something that also caused me problems when I was enabling AWS on a Bell firmware.
The effective solution was to install a custom recovery to facilitate a complete wipe of files, then flash a Rogers stock image. Cured. And continuing to work properly if subsequently returned to a Bell stock image. Although, frankly you'd have a more stable and flexible platform if you you kept the Rogers image in the end. If the build properties edit doesn't solve your issue, then here is a path for you to pursue.
.
1/2 Lit Toggles - build.prop editing issue
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
jrwebdev17 said:
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
Click to expand...
Click to collapse
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
DeadlySin9 said:
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
Click to expand...
Click to collapse
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Editing build.prop is a plausible workaround if the OP has root access. If he doesn't wish to root his phone, then he can clean up his system configuration by reinstalling as I described earlier in the thread without requiring root. Two approaches to the same result.
And yes, you can add the entry if it doesn't already exist in your configuration.
.
jrwebdev17 said:
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Click to expand...
Click to collapse
UPDATE: I didn't have any luck using the build.prop fix, nor with the wpa_supplicant.conf fix that some of you may have seen mentioned. I ended up Recovering to stock MF3, (I was already on MF3). This gave up my root access, and I didn't take any additional steps to hide busy_box or anything like that, after my MF3 recovery it looked like I was safely unrooted and I contacted AT&T support via web-chat, and they asked some questions and sent me to a nearby AT&T device center. I took it there, they didn't ask a single question about how it happened, whether I had rooted it, etc(although I was paranoid that there would be traces left behind and they would turn me away). Long story short, they replaced the phone no questions asked!
In my opinion it would seem that while this problem could in some cases be caused by rooting and tinkering, it's enough of a known issue to AT&T that they would replace it under warranty. Hopefully Bell or other carriers would do the same. My advice is to try your carrier, particularly if you are with AT&T.
Just to help people who are searching for a solution. I had flashed a T-Mobile rom and my wifi stopped being togglable on my AT&T S4. That is, I couldn't turn on wifi. The button would get stuck on. After trying to flash what I thought was the right MK2 modem and still having the same issue, I thought I was out of luck. However, I found this one here: http://forum.xda-developers.com/devdb/project/dl/?id=3275 and hit paydirt. Flashing it using Safestrap and then wiping cache and delvik worked. The file is called jflteatt-MK2-modules.zip.
Only for WIFI, for me what worked was I had to open a litte bit the one side of the phone and close it again (removing a little the plastic, like if you were going to open the device) Wifi started working again, no need to flash any roms, it seemed to be something related with pressure, humidity or something inside the phone.
Regarding bluetooh I had no luck still not working, only keeps saying activating and never gets activated.
does anyone find a solution for this yet?
I have had the same issue for months. Started after warranty was up. I have AT&T on nc1. I tried everything mentioned here but nothing worked. Even left it with the phone repair guys for a week with no luck. It first started after I flashed Hyperdrive ROM. A reboot helped for a while. It actually came back for a week on Kevp's ROM, but then had an error that reboot the phone and lost it again. Phone is now on Craigslist and I am back to my S2. On a high note it's nice to not have a unlocked bootloader again.
you need to flash the exact same model/firmware's modem file atleast thrice before giving up.... i have a simalar issue the thing is my model number is 1377z and google doesnt have a working flashable modem file for it so basically i am screwed too wifi calling and video recording doesnt work....
update :: saw that you got it replaced !!
smoooth .....
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
Just tried this on my sgh-i337m that was having the same wifi issues after rooting and flashing a kernel. Rebooted and wifi is up and running. So far so good. Thanks a lot!
I recently updated to KitKat OTA a few days ago, I flashed the hotspot mod (although it didn't work) And I have TWRP installed. Aside from that I haven't touched any system files. The home button does nothing, it flashes and causes the phone to vibrate upon press but doesn't actually DO anything. I am not getting any notifications at all, my phone will vibrate but the notifications will not appear. Also, I have it set to lock with a PIN. But it doesn't lock, I'll lock it, wait, unlock it and it won't ask for the pin it'll just be right where it was when I locked it. Please could someone help me? It was working fine earlier, except the Play Store kept giving "No connection" so I restarted my phone and then all of these issues arose. Please could someone help me?
Edit: considering trying a factory reset through the settings, would this be safe considering I am rooted with TWRP installed?
Edit2: I'm trying to flash a stock Jellybean image using LG Flash tool. But the tutorial is telling me I need to go into device manager and set the COM port to 41. The problem is device manager isn't showing any com ports at all. I have the drivers installed and they worked fine before all this happened. The computer also doesn't recognize the phone's internal storage. Could I try flashing it without setting the COM port? Or could someone help me set it?
Sent from my LG-LS980 using Tapatalk
After installing the the hotspot mod it didn't work and issues started arising so my question is did you remove the mod after you knew it didn't work? Also about you flashing stock, there is no way to do it without switching the com port to 41, if you don't change it the flash fails at around 49% or so, have you tried switching usb ports?
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
After installing the the hotspot mod it didn't work and issues started arising so my question is did you remove the mod after you knew it didn't work? Also about you flashing stock, there is no way to do it without switching the com port to 41, if you don't change it the flash fails at around 49% or so, have you tried switching usb ports?
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
I have not tried removing the mod, as I'm honestly unsure how. I deleted the backup I had made because no issues had arisen and it took around 2 gigs of space if that was needed to remove it. I'm going to try more when I get home soon and hope I can get the COM port to appear under device manager. I could see the hotspot mod causing issues with connection, since it affects USB connection. Is there any way I can remove it without a backup? Really shouldn't have deleted my backup..
EDIT: Got it working, guess it had to be in download mode to set the port and I just missed that part Working on the flashing now.
Sent from my LG-LS980 using Tapatalk
pokemaster787 said:
I have not tried removing the mod, as I'm honestly unsure how. I deleted the backup I had made because no issues had arisen and it took around 2 gigs of space if that was needed to remove it. I'm going to try more when I get home soon and hope I can get the COM port to appear under device manager. I could see the hotspot mod causing issues with connection, since it affects USB connection. Is there any way I can remove it without a backup? Really shouldn't have deleted my backup..
EDIT: Got it working, guess it had to be in download mode to set the port and I just missed that part Working on the flashing now.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
well for future reference a backup should be stored in the pc for the future because it's one of the ways to go to stock before you started modifying files, and yea download mode very important
XxZombiePikachu said:
well for future reference a backup should be stored in the pc for the future because it's one of the ways to go to stock before you started modifying files, and yea download mode very important
Click to expand...
Click to collapse
Got it fixed, thanks for all your help and patience! :good:
Help
Hey guys, i'm having this exact same problem, i'm not rooted and would like to know how you got it fixed exactly.
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Update!
I got the wifi to work, temporarily. Deleting or renaming the data/misc/wifi directory and rebooting allows me to connect to a wifi network. The problem is that it only lets me connect to that network. If I try to switch ssids or leave the area it will revert to wifi not turning on until I delete or rename the data/misc/wifi directory and reboot again. Not sure what else to try here.
Any help would be appreciated.
Now with logcats
Checked out adb logcat, errors:
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)Client SS library: connect: Connection refused
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)SS_ConnectToDmnSndCmnData error
Anyone with a fix? Got the same problem today. It's fixed after a restore but if I change the network, wifi turns greyed out.
rstoops said:
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Click to expand...
Click to collapse
Found the fix.
Use Root Explorer.
Delete the files below that are inside /data/misc/wifi/
wpa_supplicant (folder)
wpa_supplicant.bak.conf
wpa_supplicant.conf
Go to build.prop press menu and select Text Editor than find this line:
ro.securestorage.support=true
change it to:
ro.securestorage.support=false
Save. Reboot, wifi should be fine.
Since nougat was released for our XZ I noticed that even stock ROMs Miracast feature broken from the jump, hell even nougat update on Nexus 5x and 6p broke Miracast as well. This is a guide to fix that.
SPECIAL THANKS TO @maksim_kw FOR SHOWING ME THE WAY AWHILE BACK.
REQUIREMENTS:
Root
ADB set up on a Computer
Root File explorer/text editor
INSTALLATION:
Go to system/etc and find file wfdconfig.xml
Then find this line and change
- enable HDCP by default -->
<ContentProtection>
<Valid>1</Valid>
To
- enable HDCP by default -->
<ContentProtection>
<Valid>0</Valid>
Then save
Then go to system/ and find build prop
Find this block
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
##property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
Then add this line
persist.sys.wfd.appmonitoring=1
So it looks like this
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
persist.sys.wfd.appmonitoring=1
##property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
Then save
Then connect to adb and run theses codes
Adb shell
Su
setprop persist.debug.wfd.appmonitoring 1
Reboot
And it's working again ! ?
Leave a thanks if this worked for you
I did this yesterday on my Xperia XZ running 39.2.A.0.417
and the phone was bricked. It was stuck in a bootloop. It never got past the SONY logo.
Then I tried to undo the mod by replacing the 2 files with the originals
/system/build.prop
/system/etc/wfdconfig.xml
And it is still stuck in the bootloop.
Should I just run the command:
setprop persist.debug.wfd.appmonitoring 0
to undo this mod ?
I hope it will boot again then.
I don't know what I did wrong. I didn't use adb and the computer. I did all the steps on the phone itself. Maybe that's what caused the bootloop?!
lebigmac said:
I did this yesterday on my Xperia XZ running 39.2.A.0.417
and the phone was bricked. It was stuck in a bootloop. It never got past the SONY logo.
Then I tried to undo the mod by replacing the 2 files with the originals
/system/build.prop
/system/etc/wfdconfig.xml
And it is still stuck in the bootloop.
Should I just run the command:
setprop persist.debug.wfd.appmonitoring 0
to undo this mod ?
I hope it will boot again then.
I don't know what I did wrong. I didn't use adb and the computer. I did all the steps on the phone itself. Maybe that's what caused the bootloop?!
Click to expand...
Click to collapse
I dont think thay would brivk your device, and you should have a backup
All I had to do to fix my screen mirroring disconnection issue in Nougat was to simply flash the device keys DK.ftf using the old Flashtool 0.9.22.3
Now that my FIDO keys are provisioned, the screen mirroring works again.
@Smacksmack206
Working fine with my sony xz dual
Confirmed still working in latest FW 7.1.1.
tried your procedure on my nexus 6 nougat 7.1.1
unfortunately casting still doesn't work
tried with sony and Samsung smart tvs
it gets as far as preparing screen mirroring
and then after a while it disconnects
marisaleh said:
tried your procedure on my nexus 6 nougat 7.1.1
unfortunately casting still doesn't work
tried with sony and Samsung smart tvs
it gets as far as preparing screen mirroring
and then after a while it disconnects
Click to expand...
Click to collapse
Well you can try to download the version on my GitHub maybe that might work. I never tried this on my 5x since I got my xz 3 months ago
sorry I don't understand, what version
and how do I access your GetHub
once again I am on nexus 6 running Nougat version 7.1.1
tried your instructions for screen cast and didn't work
marisaleh said:
sorry I don't understand, what version
and how do I access your GetHub
once again I am on nexus 6 running Nougat version 7.1.1
tried your instructions for screen cast and didn't work
Click to expand...
Click to collapse
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/master/wfdconfig.xml
You can try it not sure if it will work on n6 but it works on xz
thank you for that
I've just tried it on my nexus 6 and unfortunately it didn't work
marisaleh said:
thank you for that
I've just tried it on my nexus 6 and unfortunately it didn't work
Click to expand...
Click to collapse
It was worth a shot, makes me wonder what they did and how to fix it in your end, on the xz it was kinda easy to fix
WOW man @Smacksmack206 thank you so much!
Confirmed working on XZ running Existenz 7. Now I can mirror my screen with Miracast
Cheers!
Does anyone success on XZ Premium?
I think they are same but I failed......
I got my miracast 4 days ago
And its 100% working
Using stock room
Nougat 7.1.1
Should this method still works on Oreo?
---------- Post added at 10:42 AM ---------- Previous post was at 10:18 AM ----------
Answer IS YES!!!!
I've spoken a bit too fast... the casting works for a few seconds, then the phone disconnect form the TV. Any hint on how to be able to cast phone screen to TV with Oreo?
Thanks.
edit: OK... it seems that casting works, but is limited to music, settings, and xperia launcher... if I try to go to anything else, it automatically disconnects. some king of locking of any other content. is there any solution? Is this related to DRM?
sensei_sai said:
I've spoken a bit too fast... the casting works for a few seconds, then the phone disconnect form the TV. Any hint on how to be able to cast phone screen to TV with Oreo?
Thanks.
edit: OK... it seems that casting works, but is limited to music, settings, and xperia launcher... if I try to go to anything else, it automatically disconnects. some king of locking of any other content. is there any solution? Is this related to DRM?
Click to expand...
Click to collapse
You did it wrong some where in the procedure redo it again, double check the config file you made edits to, double check the adb commands, simply do it over lol you shouldn't get restrictions if you do it correctly. I no longer have an XZ but I can somewhat assist u
Smacksmack206 said:
You did it wrong some where in the procedure redo it again, double check the config file you made edits to, double check the adb commands, simply do it over lol you shouldn't get restrictions if you do it correctly. I no longer have an XZ but I can somewhat assist u
Click to expand...
Click to collapse
Unfortunately it doesn't work on Oreo. It worked on Nougat but I'm guessing something's missing in Oreo that we need to edit.
iArvee said:
Unfortunately it doesn't work on Oreo. It worked on Nougat but I'm guessing something's missing in Oreo that we need to edit.
Click to expand...
Click to collapse
I'm aware of this, hopefully someone can find a new way to fix it in Oreo. I would try but I no longer have my XZ and Samsung has smart view feature that works on nougat and Oreo to Miracast so I don't have that problem on my note 8. But just now thinking about it, maybe someone can port smart view app over to the XZ somehow lol
Hi there, I got an issue on the OOS 4.5.12 after 3 days of using it. I got the problem , that the button looks stuck. I can click it and it will change its own color, but it doesnt turn on my wifi. Now I know I can clean flash the update again, but In want to know if someone had/has this problem too, and if someone maybe knows a work-around.
Edit: So I tested the device furthermore and found out, that I can't turn my Wi-Fi hotspot on... Wiping dalvic/ART cache didn't work neither...
Strange.... I didn't have this problem at all.
_MartyMan_ said:
Strange.... I didn't have this problem at all.
Click to expand...
Click to collapse
Same until today ? I will try to dirty flash the update, just to see if this will solve the problem. If it doesn't work, then I will be switching back to 4.5.10 OOS
Sent from my OnePlus 5 using XDA Labs
When I got this error I found out it was because I flashed new firmware and used an older kernel which didn't support the new firmware. You should read your logcat and see if there is any clue there.
Hello. Calling for help!
I have the exact same issue except i am able to launch and use WIFI. When i try to enable portable hotspot it gets stuck on "Turning on". The hotspot button in the slider shows enabling but the hotspot never gets enabled. I was on OOS 4.5.15 and upgraded to 5.1.5 after which i restored only the DATA partition from TWRP. I am currently rooted. I tried with editing the build.prop file and restarted but the issue is persistent. Any help would be appreciated.
Thanks
qureshiburhan said:
Hello. Calling for help!
I have the exact same issue except i am able to launch and use WIFI. When i try to enable portable hotspot it gets stuck on "Turning on". The hotspot button in the slider shows enabling but the hotspot never gets enabled. I was on OOS 4.5.15 and upgraded to 5.1.5 after which i restored only the DATA partition from TWRP. I am currently rooted. I tried with editing the build.prop file and restarted but the issue is persistent. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I would recommend a clean flash to test without restore old data.
strongst said:
I would recommend a clean flash to test without restore old data.
Click to expand...
Click to collapse
Thank you for replying. I dug a bit deeper last night. Deleting the entire wifi folder from root and restarting fixed the issue.
I had a lot of problem with wifi after flashed a not stock rom. Nobody could me help until I find the solution. Tell me Jelly do you have mac address or it show 02:00:00:00:00:00?