Is there any roms that are ASOP, based on stock AT&T for 5.0? All I can,find are CM12 based based roms. If that's the case, what's the reason? I have stayed away from CM roms in the past due to their lack of full functionality.(Bluetooth, camera, visual voice mail issues) Any recommendations for as close to an AOSP as possible?
I believe this has to do with the boot loader being locked and therefore all roms must be based of stock
jazzmoe76 said:
Is there any roms that are ASOP, based on stock AT&T for 5.0? All I can,find are CM12 based based roms. If that's the case, what's the reason? I have stayed away from CM roms in the past due to their lack of full functionality.(Bluetooth, camera, visual voice mail issues) Any recommendations for as close to an AOSP as possible?
Click to expand...
Click to collapse
Locked bootloader prevents any flashing of AOSP Roms and custom kernels period
I want to install aosp rom to my phone because of all of the stock passed issues. But I know that aosp roms have terrible camera framework, can I port the stock based one to aosp.
I see for some other Xperia phones they already did that.
Hello i'd like to know why we "only" have cm or aosp based Rom. Nobody wants to build stock based Rom without bloatware and few tweak or is it a software issue?
Hello everybody, sometimes, I flash my legendary Nexus 5, and test roms con Multirom forma ser their stability only, and think... Which ROMs are functional with pseudo kernel (Boot inject) from Multirom?
Based on my experiences says the following:
If you use the bootpatches for KitKat, you've problems with more of two Roms (Excluded the "Internal" *ROM base where you have been installed Multirom*); and should be reinstall it.
If you use bootpatches for Lollipop, all your Roms have battery drains and some errores for read files allocated in another Roms.
If you use bootpatches for Marshmallow, al works "perfecty", less when you try install another ROM based on MM.
Now:
Compatibility:
Multirom is Compatible with Stock Kernels only, FrancoKernel, Experience Kernel and others haven't a bootpatch for support that TWRP version.
All Roms based on KitKat, Stock, CAF and Cyanogenmod, included Sailfish OS, Ubuntu Touch and Firefox OS.
All Roms based on Lollipop that don't use FrancoKernel by default.
Almost all Marshmallow Roms (Some roms doesn't boot on Multirom), esencially Cyanogenmod based Roms.
Almost all Nougat Roms (LineageOS and "forkeds" Included), in Hammerhead CAF, non-CAF bases Roms, works too; CAF based Roms on Normal Nexus 5, and some based on Aosp, "Developer Options" doesn't works (Use Android Terminal for enable that options).
Oreo 8.0 Roms (Not Aosp Based) works only.
The Kernel and Bootloader update (I guess), don't leave that 8.1 Roms works on Multirom, the logic reason really IDK.
With supported Roms, sometimes "Developer Options" doesn't work; other times, SystemUI has Stopped is the reason (Included LineageOS 15.1 from @P4Block), but, in general, works without many problemas.
hello i have a serious question, so if i have 2 roms, and root and also flash xposed on my primary does that mean that my second rom will automatically have xposed aswell or is it up to me to decide whether i want to have it on secondary aswell, because i want to have my primary one with root and xposed but my secondary i want without root or xposed, so is that possible please?
driton.talinoci said:
hello i have a serious question, so if i have 2 roms, and root and also flash xposed on my primary does that mean that my second rom will automatically have xposed aswell or is it up to me to decide whether i want to have it on secondary aswell, because i want to have my primary one with root and xposed but my secondary i want without root or xposed, so is that possible please?
Click to expand...
Click to collapse
Is possible.
Root Bridge (SuperSU or Magisk) and Xposed only works on the Rom that you choose for install it.
In my case, I'm using Kitkat (With root, but without Xposed), and Nougat (With root and Xposed).
Hi,
I would like to ask if anyone tried to make AOSP camera blobs work on stock kernel based ROM on XZ1 Compact?
Is it possible? Are there any problematic points known in advance which I missed?
If I am not mistaken that would allow us to use GCam (Google Camera) on stock kernel based ROMs such as LineageOS 15.1/16.
I know currently those blobs are compiled against different kernel version (Sony stock - 4.4, Sony AOSP - 4.9) but for some time both used kernel 4.4.
Best regards
Has anyone used AOSP kenel version 4.4 based custom ROM with Google Camera (gcam)?
I wonder whether it would be possible to use AOSP camera blobs/drivers instead of stock ones in order to be able to use gcam with stock blobs/drivers based custom ROM (such as LineageOS 16.0).
Unfortunately, I don't have the XZ1 or XZ1 Compact to test it out by myself.
mp107 said:
Has anyone used AOSP kenel version 4.4 based custom ROM with Google Camera (gcam)?
I wonder whether it would be possible to use AOSP camera blobs/drivers instead of stock ones in order to be able to use gcam with stock blobs/drivers based custom ROM (such as LineageOS 16.0).
Unfortunately, I don't have the XZ1 or XZ1 Compact to test it out by myself.
Click to expand...
Click to collapse
@derf elot @modpunk @russel5