Hi,
I am currently working on a least authority file system for AppArmor based Linux systems (MinorFs). The file-system is an encrypting loopback user space filesystem (FUSE), and it would be interesting if next to OpenSuse and Ubuntu, I could look at targeting a custom Android ROM also.
I am totaly new to the whole custom ROM world, so my apploogies if some of these quesions are FAQs.
I'm not fully sure yet if the concept will work for Android, I'm hoping it will.
I have a few questions that I hope I could get answers to in this forum:
1) Is there any custom ROM that supports fuse and allows for custom built fuse file systems to be added to it?
2) Are there any custom ROMs that next to fuse, also come with AppArmor enabled or the possibility to enable AppArmor?
3) If the question to 1 and/or 2 is no, where should I start if I wanted to customize a custom ROM to support both AppArmor and Fuse?
4) If the answer to 1+2 is yes, what would be the best way to customize and test the ROM using my file-system? Can I use virtualisation software for testing? Or will I have to keep flashing an old phone to do the testing?
5) Ones I'm done with testing, if things work out well, this file-system might, together with AppArmor be a good basis for a security focused custom ROM, is anyone working on custom ROMs that is to have a particular focus on security?
T.I.A.
Rob
Related
I'm very new to Android as an OS with the Linux kernel at its heart, but fairily proficient with GNU/Linux and a plethora of its distributions for what has been more than a decade by now. So, what I (amongst other things) find a bit bewildering is that very many of custom firmware images seem to require a very specific kernel version or build for handsets to actually work. For my Xperia Mini (Smultron), there are ROM images based on CyanogenMod that won't work with the "vanilla" CM7 kernel, for instance.
With a proper GNU/Linux system, you don't have that kind close coupling of userspace and kernel versions at all. Barring some minor incompatibilities between certain (old) releases of udev and modern releases of the Linux kernel (and vice versa), there's very little (if anything) that stops you from supplanting your three years old distro's kernel with something that Linus released a few days ago.
However, whenever I've come across a guide how to install/set up this and that ROM for some kind of phone, and someone (more or less prominently) states that that image will require a specific kernel build, I've _never_ been so lucky to have been offered a technicial explanation as to why exactly this is the case. Can anyone reading this thread tell me, or point me to where I can find out more about the underlying reasons for these subtle incompatibilities?
I refuse to believe noone can answer that question...
Some features are not available in stock kernel, that are needed for custom ROM.
I am personally not fully familiar with kernels.
I realize that one can run and install linux on an android device (which is running it's own kernel on top of android's kernel), so wouldn't it be just as possible to run a factory kernel on top of a modded kernel to regain access to device specific features that only the factory kernel can currently utilize (4g, 3d cameras, etc.)? As far as I understand, linux has access to those features and can interface with them (whether it can do anything with them is another topic, but...), so wouldn't this be a viable solution to make custom ICS, JellyBean, Cyanogenmod roms work 100% with each device? Sorry for the lack of specific technical mumbo-jumbo lingo, just a newbie brainstorming here.
Hello everybody. I love this community and I have been lurking for a long time.
I have noticed on a foreign language forum that some people were offering a custom rom for my android 9 TV box.
The chinese box is based on a s905x3 CPU and has a mediatek wifi chip for which it is hard (if not impossible to find the wifi drivers).
The site claims that the image was made by modifying the stock rom that came with the box. Is this possible or do all custom roms need to be build from the source?
The custom rom I want to make is going to replace the launcher with kodi.
I am prepared to build the whole rom from source but I do have a couple of questions.
Since the mediatek wifi drivers cannot be found how would I go about including the binary for the wifi?
I have noticed that the box that I have uses a .ko (kernel object) module to drive the wifi chip.
Can I include these kernel objects in build? It is a shame that the kernel is built as a 32bit system. Would that mean that I can only compile a 32bit kernel if I were to reuse those kernel modules and binaries?
Another idea is to perhaps use the kernel from coreelec in my build since it seems to include a lot of drivers.
Is it possible to use a kernel from something like coreelec but use the source from AOSP for the rest of my build?
Is there anything else that I should be aware of?
Thank you all!!!!
Can anyone give me any hints to any of the questions?
Essentially I want to swap out the stock launcher for Kodi. What is the easiest way to do so?
Hello friends
As you can see, we download Linux and install it on laptops and tablets with completely different hardware. And we see that after installation, we do not need to download and install any drivers.
Is there an Android firmware - Android ROM that can be installed on all smartphones and use all its features?
Can non-official developers produce such an Android? Especially now that the internal memory of phones is 128 GB or more?
There are GSI ROMs. They can run on any Project Treble supported device. However, some things don't work. For example, there is no Sony camera DRM implementation in official AOSP, so the Sony phone camera won't work on GSI. If you want to use a GSI, I recommend trying Phh-Treble.
Also, when I set up my Microsoft Surface on Linux, I had to mess around with kernel modules to get the touchscreen to work. So, Linux does require some configuration depending on your hardware.
$cronos_ said:
There are GSI ROMs. They can run on any Project Treble supported device. However, some things don't work. For example, there is no Sony camera DRM implementation in official AOSP, so the Sony phone camera won't work on GSI. If you want to use a GSI, I recommend trying Phh-Treble.
Also, when I set up my Microsoft Surface on Linux, I had to mess around with kernel modules to get the touchscreen to work. So, Linux does require some configuration depending on your hardware.
Click to expand...
Click to collapse
Thanks for answering my question.
Please tell me is there any pre-rooted version of GSI?
I think it must available pre-rooted because maybe we need install drivers and reconfigure system files.
Hello, so this is a developer oriented thread, so please refrain from answering if you aren't well informed on the subject matter as to avoid cluttering it up.
I've been wanting to ask what the reason of using FBEv1 still in most ROMs is instead of FBEv2 (Starting Android 11). FBEv1 is less secure and is no longer recommended by Google starting 11. Most ROMs are AOSP based anyways, so preserving compatibility with the stock MIUI ROMs in my opinion isn't a valid excuse. Lineage has shown that FBEv2 works just fine on the device. This also creates segmentation between user groups as now part of people are on FBEv1 ROMs and the other part is on v2 making any simple transition impossible without a wipe and making recovery compatibility hell.
Shouldn't we be adopting the newer more secure standard on any non MIUI based ROM for obvious reasons? Especially since going further, newer and newer android versions will eventually leave FBEv1 deprecated.
I'm not meaning to attack or defame anyone here with this, moreso raise the question and hopefully get some developers to switch to FBEv2 in their next release.
+1 I have the same question too. Why not adopt FBEv2?