I'm build an AOSP 8.0 ROM for a stand alone unattended box for remote data collection. I'm trying to add sysinit so that I can start crond and sshd. I'm having trouble with selinux policy and am looking for a comprehensive step-by-step on how that can be accomplished. I had a similar service running on 6.0 but can't seem to make it work on 8.0. Any one know how to do this?
Related
@rovo89, the brilliant developer behind the Xposed Framework, issued an update on his plans for adding Lollipop support to the popular modification framework.
One of the under-the-hood changes brought by Android 5.0 Lollipop is the adoption of ART as the only runtime on Android, replacing the aging Dalvik. While ART brings faster app execution thanks to its use of ahead-of-time compilation, it also happens to break Rovo89’s Xposed Framework. For this reason, Xposed doesn’t work on devices running KitKat with ART, as well as on all devices running Lollipop.
In this post, Rovo89 issued an update on his work on Xposed for ART – in short, not much has changed since the last update from July, simply because the currently available Lollipop source code is still not final:
It’s pretty hard to shoot such a fast-moving target. I hope that once a final version is out and the source code for is published (with a proper branch), changes will slow down a bit – and hopefully, vendors will use it pretty much unmodified.
The bulk of the work is still ahead, and the bad news is Rovo89 is having trouble mustering the time and motivation to tackle the difficult new project:
I still don’t have time and motivation to work on Xposed as I used to, but I’m slowly starting again (no promises though).
Getting Xposed to work on Lollipop is more than figuring out ART, said the developer, as the implementation of SELinux on Android 5 is “much stricter”. In short, while there’s a good chance Xposed for Lollipop will work, that’s not a certainty, and, if it eventually happens, it won’t be anytime soon:
I can’t give any estimation when that will be the case, it depends much on my personal situation. Chance are pretty low that it will be within a month after Lollipop release, and will get higher once I start thinking about flashing a Lollipop ROM myself (which would probably be CM12, and I think these guys won’t give us a timeline either, for good reasons).
I’m still not 100% sure Xposed for Lollipop will work, but I hope that in some way it will, even if it might not be as compatible with most ROMs and as easy to install as it is for Android 4.x
Hello XDA,
I'm in the process of creating a custom rom, which is a brand new experience for me, but I don't quite know the limitations of Android yet. I am aware of Xposed modules providing a similar experience to a desktop, but I'm curious if it is possible to develop an Android rom where these features are provided natively (IE windows, persistent launcher, etc)
My goal is to create an android look and function more like Ubuntu, without having to use a chroot method, install modules, or install Ubuntu touch. Would it be possible to completely redesign Androids interface to achieve something like this?
AlmostVanillaAOSP is an AOSP-based ROM directly using Google's source code with a few functional modifications; these modifications are fully-sourced and easily-installed prior to building the ROM. Included modifications are designed to fix bugs, enhance security, and improve "in the field" function.
Many users prefer a "vanilla" version of AOSP, without added factory bloat and proprietary software; a basic version of AOSP is a great building block to create a custom-featured ROM, or it can be left as-is by users desiring to live outside Google's realm.
Users shouldn't see any visual or functional difference between this ROM and a vanilla AOSP build; all changes are "under the hood". Please note that there has been no attempt to remove functionality or user choice with this ROM.
link:soon!!
screenshot:soon!!
I want to add hardware support for a few things to my Nexus 7. (RTL8812au and ASIX88179 to start)
From what I gather, this involves adding the driver to the kernel. However, I'm not sure where to start on doing this for android.
I have the driver sources, and have gone through setting up a dev environment based on the google documentation at source.android.com/setup/build/requirements, etc. but don't know where to go next.
Is there an android version of something similar to Linux From Scratch?
I've been working with a partner recently, on an experimental Android app for unrooted cellphones, that would integrate with Xposed Framework modules, and be usable FROM the local device itself.
I knew up front that one of the biggest challenges would be emplementing some form of drag & drop functionality with what I have in mind.
My idea is a mashup between a weakness I've discovered in OTA transmissions, during software update sessions.
Without going into this topic too deeply, I'm VERY INTERESTED IN SEEING IF ANYONE ELSE out there has been looking into a work-arround for this framework.
OR, ANY OTHER NO-Root solutions (that aren't comical, and ACTUALLY work) to things like editing the build.prop, or any other form of permission escalation.