[ROM][UNOFFICIAL][9.0.0_r56] [F500,LS991,H81x,US991,VS986] AOSiP 9.0 Final

Search This thread

aoleary

Senior Member
Nov 16, 2012
1,003
955
http%3A%2F%2Fi.imgur.com%2FDr6rSI1.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:

Josh Fox (xlxfoxxlx)
Akhil Narang
Brett Montague
Sri Harsha
Harsh Shandilya

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.

Source code:

Latest Downloads:

Mega
Visit us on telegram:
release channel: @aosipreleases
update/info channel: @aosip
community chat: AOSiP Community Chat
G4 Users: G4 Users group

FAQ and Install instructions:

Install instructions:

1. If you're coming from another ROM or need to perform a clean flash.
1. Download the ROM, Firmware and GApps from the links above
2. Wipe System, Data, Dalvik, Cache (if it first installation)
3. Flash the latest Firmware for the respective device
4. Flash the ROM and GApps
5. Reboot and Enjoy

Flash OpenGApps
Flash ONLY the latest Magisk
Any mods you want to flash (I won't be supporting Custom Kernels or Xposed)
Enjoy

2. If you're updating the ROM:
a. Via the inbuilt Updater
When you get a notification of new build available, tap it
Tap Download
Wait for Download
Tap the three dots>preferences>enable "Install updates faster"
Tap install
Wait for install
Tap reboot
Enjoy!!
b. via TWRP
Flash Substratum rescue zip if you have a theme applied
Flash ROM
Flash TWRP Installer
Reboot to recovery
Flash OpenGApps
Flash Magisk
Reboot
Enjoy
NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).

Current Issues/Information:

* Let me know

Credit/Thanks:

Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
AICP
ABC ROM
AquariOS
BootleggersROM
PixelExperience
OmniROM
---------
Any others we may have forgotten to credit
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] AOSiP 9.0 [UnOfficial], ROM for the LG G4

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

Special thanks to steadfasterX who fixed RIL and a whole load of other stuff, and Pie would not be possible without him..
Thanks to kessaras, who flew the flag for the G4 for so long and did most of the initial heavy lifting

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10
Based On: AOSP

Version Information
Status: Stable
Stable Release Date: 2019-11-21

Created 2019-11-21
Last Updated 22019-11-21
 
Last edited:

aoleary

Senior Member
Nov 16, 2012
1,003
955

aoleary

Senior Member
Nov 16, 2012
1,003
955
Frequently Asked Questions (FAQ)
Note, I have shamelessly kanged this from the LOS16 thread by @steadfasterX

Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP!
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:

logcat GUIDE

If you encountered a kernel panic follow FAQ #6 in this post instead.

Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).

Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.

Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.

so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..


Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues

Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.

A regular clean install can be done like this:
  • WIPE -> Advanced -> select: System + Cache
  • Flash the ROM
  • reflash root addon/magisk if you want root
  • reflash opengapps if you want to use Google crap

A full clean install needs 2 steps more then the regular:
  • follow the steps for regular clean
  • go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
  • REBOOT -> Recovery
  • Flash the ROM
  • reflash root addon/magisk if you want root
  • reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.



Q #03: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.



Q #04: I get a kernel panic or green/purple/blue screen how to grab logs for this?
You need a ROM with pstore fully enabled and working (pstore = debug kernel panics/oops happened in a ROM)!

All builds starting from 2019-08-15 on support pstore due to: commit#1, commit#2, commit#3

This is a 2-site change if you want to make use of it in TWRP you must install the latest TWRP "PREVIEW" release as well (TWRP is only able to show pstore logs when the ROM is able to write them so I needed to fix pstore in the ROM first (see above commits #1 + #2 )).
Besides those 2 patches these kernel configs were set: PSTORE

You can check if a ROM does support writing pstore logs by:

as soon as possible on a fresh boot:
Code:
adb shell
dmesg | grep "ramoops|pstore"

Code:
[    0.000000] cma: Found [email protected], memory base 0x000000001fe00000, size 2 MiB, limit 0xffffffffffffffff
[    0.000000] cma: CMA: reserved 2 MiB at 0x000000001fe00000 for ramoops_mem
[    0.200846] cma: Assigned CMA region at 0 to ramoops.78 device
[B][    3.957553] console [pstore-1] enabled[/B]
[B][    3.957939] ramoops: attached [email protected], ecc: 16/0[/B]
[    3.958079] drv probe : 200 ramoops 3744
[    6.262463] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts

or (if you are not fast enough) this ensures mostly the same check:

Code:
adb shell
ls -la /dev/pmsg0

Code:
crw-rw-rw- 1 camera camera 254,   0 2015-01-05 04:54 /dev/pmsg0
If you get no output your ROM does not support pstore logs.

From now on when you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1) reboot (without taking out the battery!) to either TWRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:

Enable the terminal app in developer options or download any
Open the terminal app.

su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore

Attach pstore.tgz to your post.

It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.

Developers note:
convert PMSG log
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 > readable-pmsg.txt
 
Last edited:

gioyann

Senior Member
Jun 24, 2011
225
20
48
Pisa
Hello all,
New h811/h815 builds uploaded today with Double Tap to Wake reimplemented.

I have rebased on SFXs trees, so now the device should be even more stable..

Enjoy!!


Very happy to see that DT2W is back! This is 1 of the 3 features I can't stand without!
The other 2 are:

- Power button-long presso to turn on torch
- Metadata working for bluetooth car device

Are these features workin? If yes I will test this ROM immediately!
 

aoleary

Senior Member
Nov 16, 2012
1,003
955
Very happy to see that DT2W is back! This is 1 of the 3 features I can't stand without!
The other 2 are:

- Power button-long presso to turn on torch
- Metadata working for bluetooth car device

Are these features workin? If yes I will test this ROM immediately!
Long press should be there. Its a pretty standard feature for custom ROMs.. I'm on Havoc-OS at the moment..

What do you mean by metadata for Bluetooth phone call?
 

pixapo

Senior Member
Jan 16, 2009
88
5
I got black screen while calling so hang up is imposible. Someone else?
Edit: it was a proximity sensor failure. Nothing to do with the rom, my excuses.
 
Last edited:

ogun281

Member
Dec 3, 2014
7
0
i have just tried to install this rom but it gives an error that says 'This package is for device g4, p1, 811; this device is h815'.
I have H815TR. How can i fix this issue ?
 

sdembiske

Senior Member
Jan 4, 2015
1,349
1,823
i have just tried to install this rom but it gives an error that says 'This package is for device g4, p1, 811; this device is h815'.
I have H815TR. How can i fix this issue ?

The H815TR is not able to be officially bootloader unlocked, I suspect. In order to install this custom rom, you need to unlock your bootloader first, before you can do anything.

If you have not already unlocked your bootloader unofficially with the process referred to in this thread, [UNLOCK] [UNOFFICIAL] [G4] Unlock ** ANY ** LG G4 device with UsU refer to it now and read everything very carefully and make sure you understand it fully.

When you have unoffocially unlocked your bootloader, you can install TWRP for the Pie preview version and proceed to flash the H815 rom (not the H811) that is referred to in the Downloads section at the beginning of this thread.
 

ogun281

Member
Dec 3, 2014
7
0
The H815TR is not able to be officially bootloader unlocked, I suspect. In order to install this custom rom, you need to unlock your bootloader first, before you can do anything.

If you have not already unlocked your bootloader unofficially with the process referred to in this thread, [UNLOCK] [UNOFFICIAL] [G4] Unlock ** ANY ** LG G4 device with UsU refer to it now and read everything very carefully and make sure you understand it fully.

When you have unoffocially unlocked your bootloader, you can install TWRP for the Pie preview version and proceed to flash the H815 rom (not the H811) that is referred to in the Downloads section at the beginning of this thread.

I have already unofficialy unlocked my bootloader with all nececity stuff. I can install the other custom roms such as lineage rom AOSCP etc. But this rom gives the error i said.
 

aoleary

Senior Member
Nov 16, 2012
1,003
955
Hi guys,
Uploading new builds of AOSiP with the DT2W fixes, much improved HDR processing speeds in Google Cam and some other small stuff.
 
Last edited:
  • Like
Reactions: morjul

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    http%3A%2F%2Fi.imgur.com%2FDr6rSI1.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:

    Josh Fox (xlxfoxxlx)
    Akhil Narang
    Brett Montague
    Sri Harsha
    Harsh Shandilya

    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.

    Source code:

    Latest Downloads:

    Mega
    Visit us on telegram:
    release channel: @aosipreleases
    update/info channel: @aosip
    community chat: AOSiP Community Chat
    G4 Users: G4 Users group

    FAQ and Install instructions:

    Install instructions:

    1. If you're coming from another ROM or need to perform a clean flash.
    1. Download the ROM, Firmware and GApps from the links above
    2. Wipe System, Data, Dalvik, Cache (if it first installation)
    3. Flash the latest Firmware for the respective device
    4. Flash the ROM and GApps
    5. Reboot and Enjoy

    Flash OpenGApps
    Flash ONLY the latest Magisk
    Any mods you want to flash (I won't be supporting Custom Kernels or Xposed)
    Enjoy

    2. If you're updating the ROM:
    a. Via the inbuilt Updater
    When you get a notification of new build available, tap it
    Tap Download
    Wait for Download
    Tap the three dots>preferences>enable "Install updates faster"
    Tap install
    Wait for install
    Tap reboot
    Enjoy!!
    b. via TWRP
    Flash Substratum rescue zip if you have a theme applied
    Flash ROM
    Flash TWRP Installer
    Reboot to recovery
    Flash OpenGApps
    Flash Magisk
    Reboot
    Enjoy
    NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).

    Current Issues/Information:

    * Let me know

    Credit/Thanks:

    Mike Williams (founder and creator of AOSiP)
    Google for Android and AOSP
    LineageOS
    AICP
    ABC ROM
    AquariOS
    BootleggersROM
    PixelExperience
    OmniROM
    ---------
    Any others we may have forgotten to credit
    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] AOSiP 9.0 [UnOfficial], ROM for the LG G4

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

    Special thanks to steadfasterX who fixed RIL and a whole load of other stuff, and Pie would not be possible without him..
    Thanks to kessaras, who flew the flag for the G4 for so long and did most of the initial heavy lifting

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10
    Based On: AOSP

    Version Information
    Status: Stable
    Stable Release Date: 2019-11-21

    Created 2019-11-21
    Last Updated 22019-11-21
    8
    Can't fix double tap. But I keep trying.
    Me I just corrected the errors in the code and android 9 and 10 will be more battery friendly.
    GPS is big fix though. Now location will appear normally using any camera app and maybe any location app will get more accurate coords
    7
    AOSiP March Security Patch is up

    H811 and H815 builds of AOSiP with the March Security Patch are UPPPPPP..

    New stuff since February:
    Sensor Block per Package
    Alarm Blocker
    Wakelock Blocker
    Expanded Desktop
    Switch Styler
    Expanded Notifications switch
    Screen-off frequency limited to 787MHz
    IO Scheduler is FIOPS again
    Added Lionfish CPU Governor (Tripndroid is still my preferred default)


    Clean Flash OBLIGATORY..

    Clean Flash = Wipe all of:
    Dalvik
    ART
    Cache
    Data
    System
    7
    when will the next stable build be?
    My apologies for the delay.
    I've been working on a LOT of kernel stuff and I've been trying to track down some issues that I introduced (which I now think I have resolved).
    I'm also rebasing back to the AOSiP base to find the root cause of the hard shutdowns, which I think I have now also found.

    I really hope to have a stable build out this week (without hard shutdowns) ...
    7
    Hi guys,
    I hit a bit of a snag in my search to get rid of the hard shutdowns.
    I fixed one that was due to some variable settings I had to modify in Expanded Desktop to remove some conflicts, only to find another with another feature..

    I havent had time last week to properly investigate, but hopefully this week I will..