The Following 4 Users Say Thank You to jobe For This Useful Post: | ||
|
2016-05-23
, 07:08
|
Posts: 288 |
Thanked: 1,103 times |
Joined on Jul 2014
|
#232
|
I didn't realize that you are also working on it
What is your target device? Would it mean that once sfdroid is ported to CM12.1 it will run on all CM12.1 device ports without recompilation or is recompilation needed for every device with the appropriate android build env?
Do you have already some ported code available? e.g. on GitHub?
I have not yet started the actual porting. At least it seems that I have now a CM12.1 build env for Oneplus X.
The Following 5 Users Say Thank You to nh1402 For This Useful Post: | ||
|
2016-05-23
, 10:40
|
Posts: 26 |
Thanked: 55 times |
Joined on Aug 2012
|
#233
|
Nexus 5, It will require recompilation for each device with the sfdroid code cherry-picked.
|
2016-05-23
, 11:08
|
Posts: 288 |
Thanked: 1,103 times |
Joined on Jul 2014
|
#234
|
That sounds reasonable
Once we got the base ported to CM12.1 it should be easier to port then to specific devices. Working on sfdroid is my next project but I have only very limited time. So I actually don't know when I will have something done. At least you will find it on github under my account name "jobe-m".
The Following 3 Users Say Thank You to nh1402 For This Useful Post: | ||
|
2016-05-23
, 11:15
|
Posts: 26 |
Thanked: 55 times |
Joined on Aug 2012
|
#235
|
If you have any ideas of how to make it device independent (but zip's working on specific Android versions) then let us know. You can extract the zip in the first post to see what files are modified and where they go, to give you a better understanding of what changes and what is and isn't device independent.
I *think* what's holding us back from being device independent is touch input, camera, and accelerometer and possibly init.rc. But I could be wrong.
The Following 3 Users Say Thank You to jobe For This Useful Post: | ||
|
2016-05-23
, 15:42
|
Posts: 210 |
Thanked: 841 times |
Joined on Feb 2013
|
#236
|
If you have any ideas of how to make it device independent (but zip's working on specific Android versions) then let us know. You can extract the zip in the first post to see what files are modified and where they go, to give you a better understanding of what changes and what is and isn't device independent.
I *think* what's holding us back from being device independent is touch input, camera, and accelerometer and possibly init.rc. But I could be wrong.
The Following 5 Users Say Thank You to liar For This Useful Post: | ||
|
2016-05-28
, 14:11
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#237
|
The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
2016-05-28
, 14:36
|
Posts: 210 |
Thanked: 841 times |
Joined on Feb 2013
|
#238
|
|
2016-05-28
, 14:40
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#239
|
|
2016-05-30
, 18:24
|
Posts: 210 |
Thanked: 841 times |
Joined on Feb 2013
|
#240
|
I have a Harmattan device, I could test whether it works if you point me to the documentation how. But I'll rather have time for it in July, not in June.
/edit: I've got the piratepad link from nh1402, but these instructions are for SFOS. How should I adapt them for Harmattan?
Tags |
apkenv |
Thread Tools | |
|
What is your target device? Would it mean that once sfdroid is ported to CM12.1 it will run on all CM12.1 device ports without recompilation or is recompilation needed for every device with the appropriate android build env?
Do you have already some ported code available? e.g. on GitHub?
I have not yet started the actual porting. At least it seems that I have now a CM12.1 build env for Oneplus X.