Active Topics

 


Reply
Thread Tools
Posts: 36 | Thanked: 121 times | Joined on Sep 2015 @ California
#261
This may be useful for anyone accessing work email (office365) using sfdroid. My company requires we install Microsoft Intune to check for android compliance, which it does fail. However, making the below changes will allow it to pass and you can enroll and get all the benefits.

SFOS; 2.0.1.11
CM:12.1
SFDROID: (FIRST PAGE)

Step 1
Under /system/build.prop
Look for ro.build.tag=test-keys
Change to ro.build.tags=release-keys

Step2
Rename /system/xbin/su to anything (I named it sux)

You can now enroll your sfdroid android environment.
 

The Following 7 Users Say Thank You to linuxunux For This Useful Post:
Posts: 387 | Thanked: 707 times | Joined on May 2015 @ Italy
#262
I've installed sfdroid on Nexus 5 with CM12 and Sailfish 2.0.4.13, but when i open it it remains charging with the blue logo and nothing happens, what should i do?
With that port of Sailfish jolla camera doesn't work, i'll try camera+
 

The Following User Says Thank You to claustn For This Useful Post:
Posts: 387 | Thanked: 707 times | Joined on May 2015 @ Italy
#263
the camera doesn't work with this version, what version + cm do i have to install to makes camera working and sfdroid too?
 

The Following User Says Thank You to claustn For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#264
Have you tried reinstalling the camera app via terminal?

Code:
pkcon install jolla-camera
Regarding sfdroid have you added nemo to the net_bt_stack group?
 

The Following User Says Thank You to mautz For This Useful Post:
Posts: 387 | Thanked: 707 times | Joined on May 2015 @ Italy
#265
Thank you, i've tried now and it remains the same, camera crashes before starting. For sfdroid yes, i've done it but same behavior.
Maybe should i try an older version of Sailfish?
This is 2.0.4.13
 

The Following User Says Thank You to claustn For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#266
You could try the version linked at the first post of this page. If everything works, you could OTA update to 2.0.4.14 or 2.0.5.6...
 

The Following 3 Users Say Thank You to mautz For This Useful Post:
Posts: 387 | Thanked: 707 times | Joined on May 2015 @ Italy
#267
Now everything works! Sfdroid too, thank you all to keep alive this project
 

The Following 5 Users Say Thank You to claustn For This Useful Post:
Posts: 300 | Thanked: 962 times | Joined on Jun 2010 @ USA
#268
Originally Posted by mautz View Post
You could try the version linked at the first post of this page. If everything works, you could OTA update to 2.0.4.14 or 2.0.5.6...
@mautz, have you updated to 2.0.5.6 on your Nexus 5?
__________________
Sony Xperia XA2 Ultra SFOS 3 + Sony Xperia X SFOS 3, Nokia N810
 

The Following User Says Thank You to deprecated For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#269
Yes, i installed it on my test partition, despite the known dbus bug, installation wen't fine. But i haven't tested everything, since its only my installation for testing kernels and some other stuff...
 

The Following 4 Users Say Thank You to mautz For This Useful Post:
BluesLee's Avatar
Posts: 411 | Thanked: 1,105 times | Joined on Jan 2010 @ Europe
#270
I am using 2.0.5.6 since several days, coming from 2.0.4.x I thought that the dbus bug should not have any impact on the above OTA upgrade but it took several attempts and a complete night to upgrade, i had to interrupt it, reboot, install the package where it was hanging manually and do a version --dup again.

Do you guys run sfdfoid on cm12.1 + sfos >=2.0.4? I only get the blue cm logo? How can i fix this, i.e. rerun the very first scripts to configure cm (language settings etc)?
 

The Following 4 Users Say Thank You to BluesLee For This Useful Post:
Reply

Tags
hammerhead, nexus5, sailfishos, sfdroid


 
Forum Jump


All times are GMT. The time now is 17:48.