[ROM][AOSP][CM][SafeStrap]Cyanogenmod 11 for SafeStrap with locked bootloaders

AlaskaLinuxUser

Senior Member
Oct 23, 2015
1,942
4,073
0
Fairbanks
thealaskalinuxuser.wordpress.com
I just tried the one from Joe's ROM and am getting no force-close errors, haven't checked logcat tho. Sadly calling still fails.
Great work! I need to get Joe's permission to use his. I will PM him. Have you tried any from jmsqs? We have permission to use his stuff. Perhaps the other fixes have enabled the apk to work? Can you attach yours here so we can test it too? Also to verify against the one I tried.
Great work! Once we get permission, I'll add it in and update the OP.
As for phone calls, we need to fix the APN settings so you can link up with your carrier. You could try editing the APN XML file directly, it is very straight forward. You can edit it with any text editor.
 

Evant28

Member
Jan 22, 2013
34
37
0
Great work! I need to get Joe's permission to use his. I will PM him. Have you tried any from jmsqs? We have permission to use his stuff. Perhaps the other fixes have enabled the apk to work? Can you attach yours here so we can test it too? Also to verify against the one I tried.
Great work! Once we get permission, I'll add it in and update the OP.
As for phone calls, we need to fix the APN settings so you can link up with your carrier. You could try editing the APN XML file directly, it is very straight forward. You can edit it with any text editor.
Sorry, looking back I might have mislead you a bit. I am getting the force close error on the dialer when I try to place the call, but I am not getting any crazy errors obviously related to the teleservice.apk. I'll upload the apk anyways.

http://www.filedropper.com/teleservice

EDIT: Changing APNs doesn't seem to change anything.
 
Last edited:
  • Like
Reactions: AlaskaLinuxUser

Sterben Pistole

Senior Member
Sep 28, 2014
421
203
0
21
Jefferson
I'm compiling a build with the apn fix. Will report back with result in around 1 hour.

EDIT: Oh, editing apns has no effect? In that cade I'll be looking through jmsq's ROM for some files related to apns/cellular service and research them.
 
Last edited:
  • Like
Reactions: AlaskaLinuxUser

Evant28

Member
Jan 22, 2013
34
37
0
I'm compiling a build with the apn fix. Will report back with result in around 1 hour.

EDIT: Oh, editing apns has no effect? In that cade I'll be looking through jmsq's ROM for some files related to apns/cellular service and research them.
I may not have done the APN config right but I think I did. Also...I copied everything related to Google from the priv-app folder in Joe's ROM; so no crazy force-close festivals. I was able to add my account and browse apps on the play store. No such luck on installing apps though (Error retrieving information from the server). The Google app will launch, allow me to opt-into Google Now, but then force close; same result if I clear data and opt-out of Google Now.

EDIT: Voice search fails to launch as well.
 

Sterben Pistole

Senior Member
Sep 28, 2014
421
203
0
21
Jefferson
I may not have done the APN config right but I think I did. Also...I copied everything related to Google from the priv-app folder in Joe's ROM; so no crazy force-close festivals. I was able to add my account and browse apps on the play store. No such luck on installing apps though (Error retrieving information from the server). The Google app will launch, allow me to opt-into Google Now, but then force close; same result if I clear data and opt-out of Google Now.

EDIT: Voice search fails to launch as well.
Hmmm... That means the gapps problem is something with the rom, and we need to find out what that would be. I have no idea what it could be. Do any of you?
 
Last edited:
  • Like
Reactions: AlaskaLinuxUser

Evant28

Member
Jan 22, 2013
34
37
0
Hmmm... That means the gapps problem is something with the rom, and we need to find out what that would be. I have know idea what it could be. Do any of you?
If I try to launch the Google Search app I get ... [CRASH] com.google.android.googlequicksearchbox threw java.lang.UnsatisfiedLinkError

According to this link, "The UnsatisfiedLinkError is thrown when an application attempts to load a native library like .so in Linux".
 

AlaskaLinuxUser

Senior Member
Oct 23, 2015
1,942
4,073
0
Fairbanks
thealaskalinuxuser.wordpress.com
I may not have done the APN config right but I think I did. Also...I copied everything related to Google from the priv-app folder in Joe's ROM; so no crazy force-close festivals. I was able to add my account and browse apps on the play store. No such luck on installing apps though (Error retrieving information from the server). The Google app will launch, allow me to opt-into Google Now, but then force close; same result if I clear data and opt-out of Google Now.

EDIT: Voice search fails to launch as well.
One thing to be careful of, is not turning this CM ROM into a GPE ROM. CM apks have different features built in, which we only want to replace if we have to.
Swapping all the priv-apps is a good idea for testing, but we want to keep as much CM goodness as possible. :)
 
  • Like
Reactions: darazor

Sterben Pistole

Senior Member
Sep 28, 2014
421
203
0
21
Jefferson
It ran in terminal, but I don't see a difference in the phone. I slapped in some modules I had from another cm build and my personal rom, but no luck. We need to focus on cell service right now. If we don't focus on it, then, even if we fix everything else, but have no signal, then the rom would be pointless. Does anyone have any suggestions on what the problem could be?
 
Last edited:
  • Like
Reactions: AlaskaLinuxUser

AlaskaLinuxUser

Senior Member
Oct 23, 2015
1,942
4,073
0
Fairbanks
thealaskalinuxuser.wordpress.com
It ran in terminal, but I don't see a difference iin the phone. I slapped in some modules I had from another cm build and my personal rom, but no luck. We need to focus on cell service right now. If we don't focus on it, then, even if we fix everything else, but have no signal, then the rom would be pointless. Does anyone have any suggestions on what the problem could be?
This is the key to a ROM, it's not much of a phone if you can't make a phone call. ;)
 
  • Like
Reactions: Sterben Pistole

Evant28

Member
Jan 22, 2013
34
37
0
One thing to be careful of, is not turning this CM ROM into a GPE ROM. CM apks have different features built in, which we only want to replace if we have to.
Swapping all the priv-apps is a good idea for testing, but we want to keep as much CM goodness as possible. :)
Very good point.

---------- Post added at 07:41 AM ---------- Previous post was at 07:41 AM ----------

It ran in terminal, but I don't see a difference iin the phone. I slapped in some modules I had from another cm build and my personal rom, but no luck. We need to focus on cell service right now. If we don't focus on it, then, even if we fix everything else, but have no signal, then the rom would be pointless. Does anyone have any suggestions on what the problem could be?
Also very good point.
 

Sterben Pistole

Senior Member
Sep 28, 2014
421
203
0
21
Jefferson
We need to find more people to help test and find solutions to the problems we're having in the rom. Like, we fixed a great amount within the 3 days of the rom being on XDA we fixed/worked around essential problems like Wi-Fi, internal storage, SoD, and the CM camera issues. If we had more than just 4 people working with us we could probably make huge leaps in progress within the next week or so and have a much more usable rom. This thread has over 800 views and and there are only 4 people actively participating. Like, come on now. I understand that most people don't know much about the internals of a rom, but at least contribute a little. Sorry for going on this little rant. It was bothering me a bit earlier today so I decided to let it out.

---------- Post added at 01:55 AM ---------- Previous post was at 01:36 AM ----------

I think I might have found a fix for the external sd, but I'm not too sure yet. I remembered an issue with one of the sd cards a while back on one of my old devices and they mentioned the file 'vold.fstab' which I just found out is located in /system/etc/ I'll report back after I finish compiling and flashing the rom.
 
Last edited:
  • Like
Reactions: AlaskaLinuxUser

Evant28

Member
Jan 22, 2013
34
37
0
We need to find more people to help test and find solutions to the problems we're having in the rom. Like, we fixed a great amount within the 3 days of the rom being on XDA we fixed/worked around essential problems like Wi-Fi, internal storage, SoD, and the CM camera issues. If we had more than just 4 people working with us we could probably make huge leaps in progress within the next week or so and have a much more usable rom. This thread has over 800 views and and there are only 4 people actively participating. Like, come on now. I understand that most people don't know much about the internals of a rom, but at least contribute a little. Sorry for going on this little rant. It was bothering me a bit earlier today so I decided to let it out.

---------- Post added at 01:55 AM ---------- Previous post was at 01:36 AM ----------

I think I might have found a fix for the external sd, but I'm not too sure yet. I remembered an issue with one of the sd cards a while back on one of my old devices and the mentioned the file 'vold.fstab' which I just found out is located in /system/etc/ I'll report back after I finish compiling and flashing the rom.
Sounds good, I'm gonna just keep poking around. I should probably test the other kernels too.
 
  • Like
Reactions: AlaskaLinuxUser

Evant28

Member
Jan 22, 2013
34
37
0
Wooooooo! I've made some progress! Now, I can see an extSdCard folder in /mnt/ but it say's I need root access. Gonna try the temporary root method and report my findings.
Awesome!

---------- Post added at 07:40 PM ---------- Previous post was at 07:28 PM ----------

About the kernel thing...it looks like I'd have to take the OTA and then do the whole upgrade process. Unless it's really necessary I'd like to avoid having to do a complete wipe.

Sorry :(
 

AlaskaLinuxUser

Senior Member
Oct 23, 2015
1,942
4,073
0
Fairbanks
thealaskalinuxuser.wordpress.com
We need to find more people to help test and find solutions to the problems we're having in the rom. Like, we fixed a great amount within the 3 days of the rom being on XDA we fixed/worked around essential problems like Wi-Fi, internal storage, SoD, and the CM camera issues. If we had more than just 4 people working with us we could probably make huge leaps in progress within the next week or so and have a much more usable rom. This thread has over 800 views and and there are only 4 people actively participating. Like, come on now. I understand that most people don't know much about the internals of a rom, but at least contribute a little. Sorry for going on this little rant. It was bothering me a bit earlier today so I decided to let it out.

---------- Post added at 01:55 AM ---------- Previous post was at 01:36 AM ----------

I think I might have found a fix for the external sd, but I'm not too sure yet. I remembered an issue with one of the sd cards a while back on one of my old devices and they mentioned the file 'vold.fstab' which I just found out is located in /system/etc/ I'll report back after I finish compiling and flashing the rom.
Easy champ! :)
By the grace of God, a bit of elbow grease, and determination has enabled us to fix lots of problems. It would be great to have more help, but we are getting a lot done. We should have this finished in no time! ;)
 

AlaskaLinuxUser

Senior Member
Oct 23, 2015
1,942
4,073
0
Fairbanks
thealaskalinuxuser.wordpress.com
Sorry, looking back I might have mislead you a bit. I am getting the force close error on the dialer when I try to place the call, but I am not getting any crazy errors obviously related to the teleservice.apk. I'll upload the apk anyways.

http://www.filedropper.com/teleservice

EDIT: Changing APNs doesn't seem to change anything.
I just got a PM from Joe-Tech giving us permission to use it. I added it to my ROM, but it causes FC errors. Which ROM date did it work with for you? Did you edit/change anything else? What kernel were you using? Thanks, let's keep up the good work!