• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

Secure Spaces Android ROM (now on +50M devices)

JeffRt

Senior Member
Nov 12, 2015
70
61
0
Ottawa
www.securespaces.com
XDA:DevDB Information
Secure Spaces, ROM for the Google Nexus 5

Contributors
JeffRt
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 3.4
Stable Release Date: 2015-11-12
Current Beta Version: 3.4
Beta Release Date: 2015-11-12

Created 2015-11-17
Last Updated 2016-10-31
 

Attachments

Last edited:

driekus33

Senior Member
Jun 6, 2012
87
5
0
We are working on porting to Marshmallow currently to support Nexus 5x and 6P, we will release this ROM when it is ready. Thanks for asking.
Thanks for such a speedy reply. I look forward to seeing more of it.

A quick question, is the virtualization used a Xen virtualization?
 

schwarzlichtkind

Senior Member
May 13, 2010
290
64
0
Bildungsrepublik
You really got my interest here, this looks really awesome. I just like to know, if there are some extra settings for customization included, or if this is pure stock.
Another thing is, that I like to use xposed with xprivacy - I doubt that xposed is working here, or?
 

JeffRt

Senior Member
Nov 12, 2015
70
61
0
Ottawa
www.securespaces.com
Thanks for such a speedy reply. I look forward to seeing more of it.

A quick question, is the virtualization used a Xen virtualization?
HI driekus33 , we are not using Xen. We create separated spaces "virtual phones" using a combination of kernel mods (ecryptfs, pid namespaces etc) , framework mods and applications to achieve this. I will provide more technical details in this thread for those that are interested. Thanks for the question.
 

JeffRt

Senior Member
Nov 12, 2015
70
61
0
Ottawa
www.securespaces.com
You really got my interest here, this looks really awesome. I just like to know, if there are some extra settings for customization included, or if this is pure stock.
Another thing is, that I like to use xposed with xprivacy - I doubt that xposed is working here, or?
Hi schwarzlichtkind, I am not sure what you mean by extra settings - but we provide a way for you to divide your device into multiple spaces or "virtual phones" and also the ability to create a hidden space "virtual phone". You can push what ever apps you want into these spaces and customize based off of stock AOSP. Our ROM does not support xposed.
 
  • Like
Reactions: schwarzlichtkind

JeffRt

Senior Member
Nov 12, 2015
70
61
0
Ottawa
www.securespaces.com
On my one sim 16 gig Nexus. Waste of time. My lenovo zuk 1, two sim, 64gig,yup handy
Hi zerosum0, Can you expand on your "Waste of time"? I think keeping a hidden space and a personal space with only a few important apps will help reduce the impact of memory. For example in your hidden space you may just have a set of Tor apps and in a personal space you might use this to try new games or apps you want to ensure do not get access to your personal data (contacts etc..). I am glad you like it on your Lenovo zuk 1. Thanks for the feedback.
 
Last edited:

JeffRt

Senior Member
Nov 12, 2015
70
61
0
Ottawa
www.securespaces.com
You really got my interest here, this looks really awesome. I just like to know, if there are some extra settings for customization included, or if this is pure stock.
Another thing is, that I like to use xposed with xprivacy - I doubt that xposed is working here, or?
I would also argue you no longer need Xprivacy. When you create a space this space is isolated from the owner space , mulit user data separation (and also encrypted using ecryptfs) , plus we have enabled pid namespaces in the kernel. Anything running in the additional space cannot access anything in the owner space (this includes contacts, sensitive data etc). You can also control the network access for this space as well using a number of exposed attributes. We have made this very easy for you to have strong and secure separation.
 
  • Like
Reactions: schwarzlichtkind