Do you mean can’t get “blue LED”? Sometimes it is the speed with which you push in USB-C when holding "volume down’ button in. Sometimes need to press and hold the power and the volume up button simultaneously until the device makes three vibrations if continually getting green LED.
1 Like
No no: the fact is that it turns blue, but from the terminal it gives me an error: Found 0 devices:
Incorrect number of connected devices. Make sure there is exactly one device connected in fastboot mode.
As not mentioned: with a USB 2.0 it works… 
I try to flash 3.3.0.16, where spoofing worked and update to 3.4.0.24, and let you know.
Hopefully you can now get back to:
For me the “killer” upon 3.4.0.24 is non-functioning GPS no matter how many satellites are in view usually 13 for some reason!
I’m also having issues getting Waze to work (no map tiles loading, and it says ‘Searching network…’ , although HERE WeGo works ok.
It can be done! By flashing 3.3.0.16, turning on spoofing regularly, and then updating to 3.4.0.24, the spoofing remains and everything works fine!!! 
3 Likes
I also have this problem, i think i’ll wait for it to be fixed rather than downgrading. Is it possible to mark this “i also have this problem” here on Sailfish OS Forum without creating a pointless reply?
Good luck, as until now I did not see that this is noted by Jolla as a problem at all.
Maybe it is an upgrade problem, maybe wrong execution of steps? But until now we also did not see any positive feedback where a user has spoofing enabled under a freshly flashed 3.4.0.24 system, right?
No, not really. Only way to acknowledge is the like (heart) button. (which has only been pushed once as of writing this here)
I also have this problem on a freshly flashed 3.4 device. An XA2 Ultra single sim specifically. Seems like it’s not an adaptation-specific issue?
Random thought: would someone be willing to try the old method of enabling spoofing to see if that still works? I have a bunch of travel this week so I can’t.
Do you have a link to a tutorial for this? I’m willing to give it a shot.
https://github.com/yeoldegrove/sailfish-signature-spoofing-lxc I believe these are the instructions.
1 Like
I have the same issue on my Xperia 10, freshly flashed to 3.4 and followed all the steps… enabled it in android settings as well as in sailfish settings and still, sig spoofing is showing disabled…
i have tried this now and can report back that it works perfectly!
2 Likes
Had the same issue with my new Xperia 10 Dual Sim with 3.4.
Going the route 3.3 route and then upgrading worked.
Hope this gets fixed soon!
I tried it too and it seems to work on an XA2 flashed directly to SFOSX 3.4.x, but I’m a total n00b at microG so I can’t tell what’s using signature spoofing or not. Before going through that tutorial, I was able to install most Android apps that I needed. Afterwards, one of those that didn’t run, and which had a mapping component (Mapbox/OpenStreetMaps), started running. No GPS, though.
Figured it out - the real problem why it will work on upgraded from 3.3 devices and not work on the clean install 3.4 is the only difference between them - the user folder name - defaultuser for clean 3.4 and nemo for 3.3 upgrades. So, the fix to get spoofing working is to stop AD and create a nemo symlink to defaultuser. 
Of course, if you already have a nemo folder, first move its contents to defaultuser, delete nemo and then symlink it.
9 Likes
That would be a bummer! 
But already mentioned/suspected in Octobre
And to fixed by @Jolla asap.
(maybe by adding the symlink into the flash image? )
1 Like
Yeah, I saw that, but didn’t expect the fix to be so easy.
So what is the status in 4.0?
I managed to grant microG spoofing permissions through its checker (it should really be documented that it no longer shows as a regular permission), but still spoofing shows as inactive for all the microG apps.