OESF Portables Forum
Model Specific Forums => Cosmo Communicator => Cosmo Communicator - Android => Topic started by: irukandji on July 15, 2020, 09:41:05 am
-
I am building a custom rom based on v23.
I have successfully deodexed and patched services.jar with haystack (https://github.com/Lanchon/haystack) but it looks like that replacing google gmscore with microg gmscore throws cosmo communicator into bootloop.
Is anyone having any expirience haystack patch (i have decompiled the patch and the changes seem fine to me), microg or knows how to logcat booting on cosmo/android9?
-
I'm sorry to say I have no experience of this with which I could help you, but I am interested in your results (and those of others). I would love to have a phone that removed google from the equation. (Sailfish has done that very well for me with the Gemini, but isn't yet ready for the Cosmo; and a working non-Google android would be interesting in its own right.)
Do please let us know how you get on. And I hope others on this forum are able to help you.
-
I am trying, I have cosmo from first batch and I have never put sim card, it is not acceptable as long as google is on phone. So either I will figure it out, linux/sailfish alternative will come out or I will sell cosmo and buy something else.
-
Just an info, I got feedback from haystack author and I think I got the culprit... will try to create new rom over the weekend.
-
And failed.
Looks like the problem is in deodexing, once it is done, the device goes into bootloop =/
-
I am glad that I was busy and postponed the deodex'ing my Cosmo... Is the bootloop occures on both stock and rooted firmware, or one of theme?
I am also very interested in deGoogify the OS as far as it let us to...
-
I am glad that I was busy and postponed the deodex'ing my Cosmo... Is the bootloop occures on both stock and rooted firmware, or one of theme?
I am also very interested in deGoogify the OS as far as it let us to...
It doesnt matter if it is rooted or not, immediately when it is deodexed, it goes into bootloop =/ I wasnt able to find any way how to fix this :(
It would be nice if planet pc would release non deodexed version :(
-
Hello,
Was there any luck getting the deodexed working?
-
Actually RIGHT now, I have figured out, why I get into bootloop... damn selinux :@ Like it is not enough manace on normal linux distributions, they included it into android.
Currently I am not aware how to disable it (on linux it is simple, on android it looks like it is done build time and enforced by default on post 4.x versions) , but I am digging trough...
services.jar is deodexed and properly patched, I have decompiled the patched code and it seems legit.
Looks like there are following options:
- one is boot.img and disabling selinux by rebuilding kernel, this is the most annoying part, I am reluctant to touch boot.img
- creating a new rule for services.jar (prefered option, I want it running due to potential that applications are checking for it)
- find some other way to disable it
If anyone knows anything about selinux on android, some help would be appreciated (just consider, that I am not running the rom - I have system.img mounted on linux and doing changes there)... I will eventually figure it out but any shortcut is welcome
-
I have just "fixed" android kernel sources, if this tutorial works (https://www.oesf.org/forum/index.php?topic=36338.0), I will have a solution in a day or two - kids, wife, job doesnt really help in that ;D