Ask / Submit
12

No WiFi (WLAN) after flashing Sailfish X to Xperia XA2 (all variants) - any idea? [released]

Tracked by Jolla (In release)

asked 2019-03-02 23:04:19 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2019-03-05 11:17:27 +0300

Marti Masa K gravatar image

It seems, I am stuck with a strange issue on my newly flashed Sony Xperia XA2 plus (dual-SIM).

As usual, I followed the instructions on how to flash carefully. However, it turns out that strangely the mobile network (4G, 3G, 2G) works well on both SIM cards - no problem at all - but I cannot turn on WiFi. After flashing the set-up procedure asks usually to connect to a WiFi network before setting up an account. I re-flashed the phone now for the 3rd time - no change for WiFi to work. Already at the initial setup, I cannot turn on WiFi.

After the setup of Sailfish is done, I go in the settings trying to enable WiFi, but no chance there either: "Network is not available. Please restart device". Sure, I can do this and also a factory reset, nothing changes.

I noticed that some folks had issues with the mobile network (not working at all) and the solution was to revert back to Android using EMMA-tool. I'm afraid to have to do the same thing and I don't have any Windows pc.

Just for information, before I decided to flash I tested almost all basic features in Android (8.0) such as WiFi and it was working just fine. I have my doubts that un-looking the bootloader and/or getting first SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_nile.img onto the XA2-plus prior the flashing to Sailfish may have bricked the WiFi...

I tried to seek if anyone else here had this issue but apparently not. Well, if there is someone who had been running into the same issue and solved it or if anybody as a hint, I would appreciate!?!

Addendum: Hello sailors! feedback about experience are always welcome!
But please give setup (windows/mac/linux vXX, binaries vXX), eventually short description.
Help for sure. Many thanks in advance :-)

image description

image description

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by jovirkku
close date 2019-03-25 12:42:50.291602

Comments

1

Did you tried to restart your phone after configuration and app update ?

cemoi71 ( 2019-03-03 03:04:28 +0300 )edit

have the same issue with double sim xa2 plus. restart and new unlock code does change something

cemoi71 ( 2019-03-03 03:45:14 +0300 )edit

Thank you cemoi71 for your prompt reply! I did several restarts including the change of the device look code. Unfortunatly, this trick does not help :-( I'm afraitd I need to get back to Android and try once again to flash it fully with EMMA-tool.

Marti Masa K ( 2019-03-03 09:41:28 +0300 )edit
2

hi i've the same problem here, my wifi was ok before flashing... I did not tried to reflash the device though...

nerip ( 2019-03-03 11:53:54 +0300 )edit
1

Hey! I have the exakt same problem but i havnt tried to reflash. I have reset the XA2 dual a couple of times. I tested the wifi and other stuff before flashing. Sailfish runs normal in other sens and the mobile data works as normal after i manually change the settings for the mobile network.

volvo88 ( 2019-03-03 12:19:10 +0300 )edit

3 Answers

Sort by » oldest newest most voted
15

answered 2019-03-03 16:56:37 +0300

nerip gravatar image

updated 2019-03-04 11:23:09 +0300

Hi me again, i've flashed again and it's working,

but i didn't pay attention firstly that i've dl the latest version of Sony "SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_nile"

and on the tutorial they wrote about "SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile"

"16" instead of "17", on the Sony website the latest version has been changed on the 1rst of March...

maybe it's something else but pay attention to this driver build...

For me it has fixed the WIFI problem.

(I had the "16" dled some days ago waiting for my XA2 to arrive)

edit flag offensive delete publish link more

Comments

2

i confirm.

following the guide in step 5.1 it says download from sony and links to LATEST which is v17, but instead it should link to v16, use this file for step 5.1: https://developer.sony.com/file/download/software-binaries-for-aosp-oreo-android-8-1-kernel-4-4-nile-v16/

fl ( 2019-03-03 18:02:09 +0300 )edit

not bad but why? the v17 should be an improvement. they made some improvement for sure, but not test somethings...

cemoi71 ( 2019-03-03 19:26:18 +0300 )edit

Maybe stupid question (or not) do someone knows how wrong could it be to take the binaries of aosp pie (android 9) with kernel 4.9?

cemoi71 ( 2019-03-03 20:14:10 +0300 )edit
1

After the infamous usb 3 linux install problem (but another version documented somewhere), and thanks to my girlfriend's old mac, I think I'm done with problems when my WLAN does not work… I was about to throw my phone through the (closed) window. But your post saved my phone (and window)…

THANK YOU !!!

As a note :

lzbk ( 2019-03-03 20:32:47 +0300 )edit
1

I'm also confirming that v16 fixes the issue, ufff... Also the brightness of the display can be controlled now. Many thanks for this question and the solution! I have noticed the difference during the initial flashing, but I had no idea if that matters or not.

Michal Turek ( 2019-03-03 21:32:27 +0300 )edit
8

answered 2019-03-05 17:03:09 +0300

sledges gravatar image

updated 2019-03-06 23:33:52 +0300

@Marti Masa K and @nerip, thank you for spotting this. Instructions on Jolla website have been updated to point to v16.

Sailfish OS on XA2 must be run with v16 in version 3.0.1, and can be run with v17B in 3.0.2 where XA2 will get its BSP HW adaptation update. 17B brings only stability updates that have not affected currently known issues. Optional instructions about how to flash 17B will be provided.

edit flag offensive delete publish link more

Comments

thank you for clarifications :-)

cemoi71 ( 2019-03-06 23:46:33 +0300 )edit

@sledges an other question just for curiosity.
is it for a particular purpose that binaries from oreo are used, and not from Pie?
Teh binaries from Pie couldn't make the job?
is it from strategy the choice, from software architecture & design, or from authorisation from sony?

cemoi71 ( 2019-03-07 11:39:42 +0300 )edit
2

Thanks for the info. I'm still interested in cemoi71's question above (of which I might have missed the answer, sorry) : Do SFOS updates (from 3.0.1 to 3.0.2 for instance) embark the sony binaries and flash the phone with the new versions ? Or do we have to reflash the phone and reinstall SFOS manually ? (maybe that's what your comment about 17B explains — automatic 17 flashing provided in 3.0.2 update, optional 17B flashing instructions — but I'm not sure).

lzbk ( 2019-03-07 13:30:09 +0300 )edit

yeah! the more it's asked, sooner comes an answer...
That's not the only place where i ask for this... ;-)

cemoi71 ( 2019-03-07 15:36:59 +0300 )edit

otherwise i found this part from sledges answer a little bit unclear
"... and can be run with v17B in 3.0.2 where XA2 will get its BSP HW adaptation update..."
Seems to answer it, but not clearly, could be a yes or no, depends on the mood.
@sledges, concretely what is the correct answer of this point?
Future Sfos update contains the new binaries part, and will upgrade it? or not?
Thank you very much in advance for the answer

cemoi71 ( 2019-03-07 15:48:50 +0300 )edit
1

answered 2019-03-06 21:39:26 +0300

Direc gravatar image

updated 2019-03-06 21:53:19 +0300

The supported version of the software binaries is v16. There is now v17b also, but it is not fully completely compatible with Sailfish 3.0.1. Here are results of my CSD test on my Xperia XA2 Ultra dual-SIM (everything listed is a pass):

  • Light sensor: Fail
  • Proximity sensor: Fail
  • Compass: Fail (known fail)
  • Hall sensor: Fail (I don't have compatible cover)
  • Fingerprint sensor: Fail (known fail)
  • Headset buttons: Fail (I don't have compatible headset)
  • Main camera and flash: Fail (black viewfinder, same with camera app)
  • FM Radio: Fail (known fail, I think...)
  • USB ORG: Fail (I have no such device)

Here are passes that need further comments:

  • Audio below microphone: Pass (actually the above mic)
  • Audio above microphone: Pass (actually the below mic)
  • WLAN: Pass (the main culprit of the question)

So; it almost works great. I suspect the broken devices (prox, light, camera) can be fixed with perhaps something as simple as config change, or perhaps Jolla has to disable some weird quirk that was needed to make it work in the first place.

Andoird apps also work as before.

I think I'll run this overnight at least and see what else pops up.

Edit: I missed what @sledges said above; SFOS 3.0.1 is only compatible with v16, and SFOS 3.0.2 is compatible with v16 and v17 (I assume this means v17b, since the "original" v17 can't be downloaded anymore)

edit flag offensive delete publish link more

Comments

Thank you for the test and feedback :-)

cemoi71 ( 2019-03-06 23:45:46 +0300 )edit

I really feel blind as sledges' answer was already there. This is what I get when I try to use my brains while on sick leave...

Direc ( 2019-03-07 09:32:38 +0300 )edit

Question tools

Follow
9 followers

Stats

Asked: 2019-03-02 23:04:19 +0300

Seen: 1,143 times

Last updated: Mar 26