[ROM][10]Android Open Source Illusion Project[Coral][Flame][Official]

Search This thread

Madjax2020

Senior Member
Dec 7, 2019
408
58
No, actually. Misty custom roms are built from source code Google offers under an open source license, and in the old days with only the proprietary blobs that are in the vendor partition being pulled. When it's not built like that, it's built using factory images. It's impossible to pull 100% of an Android os due to limitations imposed for security

Thank you for the lesson. I did not know this, fully.
 

WhiteReign

Senior Member
Apr 15, 2011
1,002
465
What is the best way to root after install? I did the old way "fastboot flash boot magisk_patched.img" but this makes for boot loop. IS there something I am doing wrong please help. Sorry Noob qyestion
 

dragynbane222

Senior Member
Jul 2, 2012
226
98
Google Pixel 4 XL
Google Pixel 5
What is the best way to root after install? I did the old way "fastboot flash boot magisk_patched.img" but this makes for boot loop. IS there something I am doing wrong please help. Sorry Noob qyestion
Also, make sure you flash patched boot image for this rom /after/ going through the setup wizard, magisk has the word tendency to cause a bootloop on this device if it's not been run through the setup wizard, even on stock
 

TGUSAGI

Member
May 22, 2017
8
1
Sim Manager Keeps Stopping

Hello.

I installed the AOSIP rom for Coral. It works great except I get a pop up, error message that says "SIM Manager keeps stopping." See log below. Can you please help?

Thank you.

Tom


10-13 19:06:26.093 D/msm8974_platform(814): platform_split_snd_device: snd_device(2) num devices(0) new_snd_devices(0)
10-13 19:06:26.093 I/msm8974_platform(814): platform_get_custom_mtmx_params: no matching param with id 0 ip_ch 2 op_ch 1 uc_id 1 snd_dev 2
10-13 19:06:27.651 W/WindowManager(1354): removeWindowToken: Attempted to remove non-existing token: android.os.Binder@a02bdde
10-13 19:06:28.011 D/Zygote (804): Forked child process 6007
10-13 19:06:28.014 I/ActivityManager(1354): Start proc 6007:com.google.android.euicc/u0a196 for service {com.google.android.euicc/com.android.euicc.service.EuiccServiceImpl}
10-13 19:06:28.016 E/e.android.euic(6007): Not starting debugger since process cannot load the jdwp agent.
10-13 19:06:28.029 D/ApplicationLoaders(6007): Returning zygote-cached class loader: /system/framework/android.hidl.base-V1.0-java.jar
10-13 19:06:28.029 D/ApplicationLoaders(6007): Returning zygote-cached class loader: /system/framework/android.hidl.manager-V1.0-java.jar
10-13 19:06:28.029 D/ApplicationLoaders(6007): Returning zygote-cached class loader: /system/framework/android.hidl.base-V1.0-java.jar
10-13 19:06:28.035 I/SDM (622): HWCDisplay::SetActiveConfig: Active configuration changed to: 1
10-13 19:06:28.047 D/AndroidRuntime(6007): Shutting down VM
10-13 19:06:28.048 E/AndroidRuntime(6007): FATAL EXCEPTION: main
10-13 19:06:28.048 E/AndroidRuntime(6007): Process: com.google.android.euicc, PID: 6007
10-13 19:06:28.048 E/AndroidRuntime(6007): java.lang.RuntimeException: Unable to create application com.google.android.euicc.pixel.EuiccGoogleApplication: java.lang.SecurityException: Failed to find provider com.google.android.gsf.gservices for user 0; expected to find a valid ContentProvider for this authority
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6465)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.app.ActivityThread.access$1300(ActivityThread.java:219)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1859)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Handler.dispatchMessage(Handler.java:107)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Looper.loop(Looper.java:214)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.app.ActivityThread.main(ActivityThread.java:7356)
10-13 19:06:28.048 E/AndroidRuntime(6007): at java.lang.reflect.Method.invoke(Native Method)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
10-13 19:06:28.048 E/AndroidRuntime(6007): Caused by: java.lang.SecurityException: Failed to find provider com.google.android.gsf.gservices for user 0; expected to find a valid ContentProvider for this authority
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Parcel.createException(Parcel.java:2071)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Parcel.readException(Parcel.java:2039)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Parcel.readException(Parcel.java:1987)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.content.IContentService$Stub$Proxy.registerContentObserver(IContentService.java:1234)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.content.ContentResolver.registerContentObserver(ContentResolver.java:2266)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.content.ContentResolver.registerContentObserver(ContentResolver.java:2254)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.gsf.Gservices.ensureCacheInitializedLocked(Gservices.java:93)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.gsf.Gservices.getVersionToken(Gservices.java:408)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.gsf.Gservices.getBoolean(Gservices.java:295)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.flib.phenotype.ExperimentFlag$1.retrieve(ExperimentFlag.java:169)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.flib.phenotype.ExperimentFlag$1.retrieve(ExperimentFlag.java:161)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.flib.phenotype.ExperimentFlag.get(ExperimentFlag.java:119)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.euicc.EuiccGoogleBaseApplication.onCreate(EuiccGoogleBaseApplication.java:92)
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.google.android.euicc.pixel.EuiccGoogleApplication.onCreate(EuiccGoogleApplication.java:36)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1190)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6460)
10-13 19:06:28.048 E/AndroidRuntime(6007): ... 8 more
10-13 19:06:28.048 E/AndroidRuntime(6007): Caused by: android.os.RemoteException: Remote stack trace:
10-13 19:06:28.048 E/AndroidRuntime(6007): at com.android.server.content.ContentService.registerContentObserver(ContentService.java:344)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.content.IContentService$Stub.onTransact(IContentService.java:482)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Binder.execTransactInternal(Binder.java:1021)
10-13 19:06:28.048 E/AndroidRuntime(6007): at android.os.Binder.execTransact(Binder.java:994)
10-13 19:06:28.048 E/AndroidRuntime(6007):
10-13 19:06:28.049 I/DropBoxManagerService(1354): add tag=system_app_crash isTagEnabled=true flags=0x2
 

TGUSAGI

Member
May 22, 2017
8
1
messenger delays

There is also a delay of about ten minutes on receipt of text messages. I don't have gapps installed with the rom.
 

Madjax2020

Senior Member
Dec 7, 2019
408
58
Oh damn I thought it was just a random reboot, but 3 in 3 days. I just realized now my camera doesn't work, the torrents I was downloading are gone, and now for es file explorer I get this error SD card is formatted as internal storage please reboot and blah blah. Can't even save a screen shot as it says I'm out of space. I have 30 gig free.
 

[email protected]

New member
Oct 29, 2020
3
0
Sprint Data Issues (Specifically LTE)

Greetings everyone. I'm a very long time lurker on xda, probably approaching the decade mark at this point.

For the past two to three days, I have been trying to find a ROM for my Pixel 4 XL that allows LTE to work. I have followed the directions to a t on several roms, no matter what I do, I can get 3G to work, but I can't get LTE to work. If I switch back to a stock factory image, LTE works just fine.

I initially decided to switch ROMs because I don't like Android 11, but now that I have seen what other roms look like, I really want to keep AOSIP. It seems like a really beautiful rom.

I am utilizing a physical Sim card, and my network is Sprint. I have noticed that if I go into the mobile network settings and click on Carrier settings, nothing happens. I don't know if that is related or not, but it seems like it might be. I don't know enough to troubleshoot this problem myself, but I assure you that I have followed the directions, and have read through the forums to no avail. after a significant amount of reading, I think it might have something to do with access point names, but honestly I'm pretty lost. The second I switch back to a stock rom, my LTE works, but no matter which custom rom I might choose, I lose LTE.

Thank you in advance for any help! let me know if there is any specific information that would help you troubleshoot as well.
 
Last edited:

moslondon

Senior Member
Sep 30, 2012
198
16
Dallas
Hello everyone, can anybody tell me if Android Auto is working with this rom? Also, what about Cast to any device other than Chromecast?
 

wrongway213

Recognized Dev & Contributor / Retired Forum Mod
Jul 27, 2014
5,107
8,894
34
Canton, OH
Google Pixel 7
Those are google products. I can't cast to my TV, Home theater or android box. I found that you can't cast to non google devices. I would like to know if a custom rom would chance that before messing with the software of the phone.

A custom ROM isn't going to deliver functionality like this unless the third party device on questionr has released source code, as Nintendo Switch & Steam Valve have to allow Android devices to control them. If you can find code that allows this, submit it and I'm sure devs of most projects would be glad to add support - I don't know that many of these kinds of products have such code open sourced though.
 

[email protected]

New member
Oct 29, 2020
3
0
Thinking it was somehow GAPPs related

Greetings everyone. I'm a very long time lurker on xda, probably approaching the decade mark at this point.

For the past two to three days, I have been trying to find a ROM for my Pixel 4 XL that allows LTE to work. I have followed the directions to a t on several roms, no matter what I do, I can get 3G to work, but I can't get LTE to work. If I switch back to a stock factory image, LTE works just fine.

I initially decided to switch ROMs because I don't like Android 11, but now that I have seen what other roms look like, I really want to keep AOSIP. It seems like a really beautiful rom.

I am utilizing a physical Sim card, and my network is Sprint. I have noticed that if I go into the mobile network settings and click on Carrier settings, nothing happens. I don't know if that is related or not, but it seems like it might be. I don't know enough to troubleshoot this problem myself, but I assure you that I have followed the directions, and have read through the forums to no avail. after a significant amount of reading, I think it might have something to do with access point names, but honestly I'm pretty lost. The second I switch back to a stock rom, my LTE works, but no matter which custom rom I might choose, I lose LTE.

Thank you in advance for any help! let me know if there is any specific information that would help you troubleshoot as well.

I still haven't been able to get it working, but I got LineageOS working by switching from Nano to Pico.
 

[email protected]

New member
Oct 29, 2020
3
0
I can't answer that question

Is this a common thing? Not being able to get lte to work? I haven't flashed the rom yet

I wasn't able to find anyone else with the issue on this rom or any of the other AOSP roms I tried. Years ago I had a situation where the Google setup was failing to work, and I remembered that it broke data on my phone at the time. As a result, I surmised that perhaps it was actually the gapps package that I chose. Therefore I switched from nano to Pico to see if that solved the problem. It's solved the problem completely, and now my carrier settings work and I have LTE. Keep in mind that that's only on lineage though. I didn't get the opportunity to test it with this ROM because they already include gapps.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 36
    logo.png
    Code:
    [B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
    Android Open Source illusion Project

    About us:
    AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.​

    Team Illusion:

    Bug reporting:

    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    • Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.



    Credit/Thanks:

    Mike Williams (founder and creator of AOSiP)
    Google for Android and AOSP
    LineageOS
    ABC ROM
    AquariOS
    BootleggersROM
    Dirty Unicorns
    PixelExperience
    OmniROM
    CarbonROM
    nathanchance
    ---------
    Other projects whose work helped us to create this
    And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible



    XDA:DevDB Information
    [ROM][10]Android Open Source Illusion Project[Coral][Flame][Official], ROM for the Google Pixel 4 XL

    Contributors
    xlxfoxxlx
    Source Code: http://www.github.com/aosip

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    Based On: aosp

    Version Information
    Status: Stable

    Created 2020-02-13
    Last Updated 2020-09-05
    18
    INSTALLATION PROCEDURE:
    Have an unlocked bootloader, and knowledge of adb/fastboot
    flash the boot.img in fastboot(fastboot flash boot boot.img)
    boot to aosp recovery
    Factory reset phone in aosp recovery
    choose install update from adb
    adb sideload AOSiP*.zip
    Reboot into the system, and enjoy the illusion!

    KNOWN ISSUES:
    - No issues of my testing
    17
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • Include your firmware versions in reports.
    • Mention any and all Magisk modules you might be using along with the Magisk version
    • If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
    10
    Newest update is up (7/23) and includes many changes to device, we are now building vendor instead of including stock so thorough testing is needed. Cts is fixed to pass with magisk hide. Some time this week I will be doing a mid week release for coral that will require flashing a boot image and flashing the build manually as we are changing the keys used for signing. After that build the next weekly will flash fine through updater.
    9
    Ok so i will be running the update here shortly, if you get a notification from updater please do not download as it wont save. Instead download the latest from https://aosip.dev/coral when it is up. The boot image that you will need to flash first is here flash that in bootloader and then boot to recovery and flash the new zip. After this build you will be ok to update to the next weekly with the inbuilt Updater. if you plan to root use that boot and patch it from magisk manager.