• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[Unofficial] AICP 14 - Galaxy Note 4 (Snapdragon) [TRLTE][TBLTE][TRLTEDuos]

Search This thread

73sydney

Senior Member
Jul 21, 2018
1,681
1,372
Sydney
Google Pixel 2 XL
Scratch that, this rom is the best I've 4un. Great battery life, stability, and performance. I wish there was an option to move the volume panel to the left, but no complaints. Only issues so far is charging status always says 0-2mA, which is way off, and I can't install a custom font with iFont anymore. I love this rom

EDIT: is there any way to make the GPS work?

Flashed the latest, confirmed gps is not working on this build @tripLr
 

MonadoLink

Senior Member
Jun 19, 2016
163
6
Im running the latest unofficial build by triplr and I having no problems with GPS. Everything is working fine on my end. N910F

If you're speaking of the 20191106 version, GPS definitely does not work. Been running it and have no lock, usually getting my location off by a few blocks at best. Not my hardware as RR could get a lock, and even after editing GPS.conf, still no luck. Curious if you have a fix, or if it's another version confirmed working with gps
 

PantherCat

Member
Apr 5, 2007
24
6
If you're speaking of the 20191106 version, GPS definitely does not work. Been running it and have no lock, usually getting my location off by a few blocks at best. Not my hardware as RR could get a lock, and even after editing GPS.conf, still no luck. Curious if you have a fix, or if it's another version confirmed working with gps

GPS DOES work (20191106). It's apparently not working for some, but I get a lock (N910F) quickly (actually much more quickly than usual) and without issue.

Problem I have is that Bluetooth is spotty. My headset connects and stays connected. However, my Alexa Auto won't stay connected for longer than a couple of seconds. Never had this issue on previous builds. If there was a Bluetooth issue in the past, ALL devices would be problematic. Never before was it device specific like this (and never had a problem connecting Alexa Auto before).
 

73sydney

Senior Member
Jul 21, 2018
1,681
1,372
Sydney
Google Pixel 2 XL
Im going to reiterate that its very unsual in my AICP flashing experience (which is extensive) for GPS not to work for me, and i tried every manual edit trick i know....so i consider it buggy....she no work

I can however flash mainline LOS (though not the current lineage-16.0-20191112-UNOFFICIAL-trlte build which is bootlooping) and have functional GPS, and as generally most other Pie ROM's are based off LOS code, +/- some handpicked options by x dev, it should be working on AICP....
 
Last edited:

MonadoLink

Senior Member
Jun 19, 2016
163
6
Im going to reiterate that its very unsual in my AICP flashing experience (which is extensive) for GPS not to work for me, and i tried every manual edit trick i know....so i consider it buggy....she no work

I can however flash mainline LOS (though not the current lineage-16.0-20191112-UNOFFICIAL-trlte build which is bootlooping) and have functional GPS, and as generally most other Pie ROM's are based off LOS code, +/- some handpicked options by x dev, it should be working on AICP....

That's funny. I've run LOS builds for months, clean I stalling new builds many times, and the GPS never worked for me
Rereading that, it looks like I was having attitude, but that was not what I meant. Anyway, I think it was a hardware issue
 
Last edited:
Cheers, theres a surprise, i thought she were dead

Once was my fave

Downloading, you know you had me an "new build" and i feel like a such a whore for jumping right on it
I have been busy with work. Sorry for not keeping updated.

I will ask if someone can update the OP for me as well.

I like this Rom as well.

Viper is still not compiling.
We have a new dev adding spen and working on GPS issues.

I dunno if the spen stuff got ported over here.
Welcome to dev @ghostwheel
 
Waze is not available thru the play store, at least for me any way. When I googled waze and followed the link to install it it stated it was not compatible with my version. I got the same for BofA and life360, which are part of my usual set up. It's been happening ever since I left 6.0.1 based roms *palms up shrug* I have been grabbing the apks and installing them myself. Small price to pay for having a current relevant rom on my 5 year old phone ?. If I understand correctly this has something to do with the version being "aicp something something something" and not "910TWKRPblahblahblah." I'll live. Thanks again devs!
 
Last edited:
  • Like
Reactions: Da_Mak
GPS fine for me, i always edit the NTP to my local (au.pool.ntp.org) though

Definitely less sim death and recovers far better from sim death it does have than XenonHD which id been using previously as my daily.

Went all over Sydney today and didnt skip a beat

We're finding out some sim issues while developing 10 source code.

Keep tuned.
There is a special build.prop fix to show complete unfiltered log messages.
This should get to why sim death occurs.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16


    logo_black.png


    AICP
    Android Ice Cold Project

    AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!

    Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
    With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.

    If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!


    Code:
    #include <std_disclaimer.h>
    
    /*
     * Your warranty is now void.
     *
     * We are not responsible for bricked devices, dead SD cards,
     * thermonuclear war or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications and if
     * you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
     *
     */

    features.png

    Feature list (rough overview)


    credits.png


    In the beginning we would like to thank:

    GZOSP team
    LineageOS & CM (R.I.P.) team
    @maxwen and the rest of the OmniRom team
    DU team
    SlimRoms team
    Resurrection Remix team
    Community
    ...

    Specifically for the TRLTE Build-
    @Inkypen

    team.png


    @LorD ClockaN
    @zipsnet
    @eyosen
    @semdoc
    @SpiritCroc
    @wartomato
    @eboye
    plus the rest of the crazy bunch that we call "team"
    ...


    donations.png


    We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
    Thank you!!



    downloads.png


    TWRP for Samsung Galaxy Note 4 (Qualcomm)

    Latest Release AICP Version 14.0

    Download links:
    - SM-N910F/G/P/R4/T/T3/V/W8: trlte
    - SM-N9100ZC/ZH/6W/9W: trlteduos
    - SM-N915F/G/P/R4/T/W8: tblte

    Google Apps:
    Open GApps
    Select ARM and 9.0. Variant is of your own choosing. Suggested: Pico or Nano.

    Magisk Stable
    Magisk Manager v7.1.1
    Magisk v18.1


    changelog.png


    Full Changelog link: https://dwnld.aicp-rom.com/
    (Just click the changelog button next to the download link in the list of builds available for your device)

    issues.png


    You tell... :p

    FAQ:
    Before using the ROM:
    Q. Can I have an ETA for the next build?
    A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.

    Q. Does this ROM support custom kernels officially?
    A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!

    Q. Why doesn't this ROM support Xposed?
    A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.

    Q. Alright, but I still want to flash Xposed, so which version do I need to install?
    A. You will need to use the version arm64/arm/whatever for SDK 28.

    Flashing the ROM:
    Q. What do I need to know before flashing?
    A. Check the install instructions in the first post...

    Q. Can the builds be dirty flashed over each other?
    A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.

    Q. How do I 'dirty flash' builds?
    A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.

    Q. How do I flash kernel builds?
    A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
    A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.

    Using the ROM:

    Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
    A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.

    Q. I'm having issues with WhatsApp, how do I fix it?
    A. Read this

    Q. Do I need to provide a logcat if I'm reporting a bug?
    A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)

    Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
    A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
    A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.


    instructions.png


    The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
    If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.

    It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
    If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.

    How to flash for the first time:
    (Again: Don't do it if you don't know it!)

    1. Download the ROM and GApps and transfer them to your device.
    2. Boot to recovery (TWRP recommended).
    3. Wipe the System, Cache, and Data (you might need to format the data partition!).
    4. Flash the ROM Zipfile.
    5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
    6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
    7. Reboot back into TWRP recovery.
    8. Flash the root solution of your choice (optional).
    9. Reboot your device.
    The procedure might vary from device to device and is a bit different on system updates!


    The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
    The root solution can be flashed together with every OTA update (= ROM Update).


    PREREQUISITE FOR OTA ("Over-The-Air" Updates):
    To be able to flash using the built-in OTA app, TWRP recovery is needed.
    Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
    On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.

    If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)

    sources.png


    Kernel source:
    apq8084 Kernel

    Telegram:
    Note 4 SnapDragon ROM Testers

    TWRP:
    TWRP XDA Thread

    ROM & Additional links:
    AICP's Homepage
    AICP Gerrit Code Review
    AICP sources on Github
    AICP Download page for official builds and media content
    AICP Discord Community


    XDA:DevDB Information
    [Unofficial] AICP 14, ROM for the Samsung Galaxy Note 4

    Contributors
    Shizzle2889, Inkypen, TripLr, _mone, mobspyguy, cvxda, ripee
    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    Based On: LineageOS

    Version Information
    Status: Testing

    Created 2019-04-07
    Last Updated 2019-06-29
    6
    Good news everyone.
    We got a team now that can check bugs.
    Everyone is focused on getting Q up, and we finally got ril.

    Bugs probably won't be fixed much on P.

    Stay tuned.

    I'm gonna have a requirement !!!! Of logs if you post bugs.
    No response at all if you post a bug without a log.

    Unless your a tester .

    Best wishes @tripLr
    5
    roomservice.xml

    To my knowledge, these room service files should be stable. Please let us know if any are not. Easiest way to do so is via the Telegram group linked at (near) bottom of OP for testing ROMs, but more than welcome here as well. Thank you.

    TRLTE:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
      <project name="AICP/packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="p9.0" />
      <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
      <project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-16.0" />
      <project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_apq8084-common" path="device/samsung/apq8084-common" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_trlte" path="device/samsung/trlte" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
    </manifest>

    TBLTE:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
      <project name="AICP/packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="p9.0" />
      <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
      <project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-16.0" />
      <project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_apq8084-common" path="device/samsung/apq8084-common" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_tblte" path="device/samsung/tblte" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
    </manifest>

    TRLTEDuos:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
      <project name="AICP/packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="p9.0" />
      <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
      <project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-16.0" />
      <project name="LineageOS/android_kernel_samsung_apq8084" path="kernel/samsung/apq8084" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_apq8084-common" path="device/samsung/apq8084-common" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
      <project name="triplr-dev/android_device_samsung_trlteduos" path="device/samsung/trlteduos" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="aicp-p9.0" />
      <project name="triplr-dev/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
    </manifest>
    5
    Ok, a short report and some questions.

    Some questions:
    Is there a human-readable changelog? The link in the OP does not seem to lead to anything resembling the 910F.
    I don't get how OTA updates are supposed to work. Can't see any in-built app for that. Is it the TWRP app? I have used TWRP Recovery for flashing.
    There is a Work Profile system app but it doesn't seem to have a UI. Nothing in the system settings. Are profiles and switching implemented?

    Unfortunately, due to being in "Unofficial" status, there is no changelog for this device on the AICP servers. Additionally, there are no OTA updates for this or any other ROM while being in "Unofficial" status. For the changelog, you can look over both AICP and the triplr-dev githubs. That will show you all the changes that have been made. However, these may or may not be easily understandable on what is going on. Also, the AICP github holds the repositories for all the "Official" devices so not everything that is there is going into the ROM when I upload it. Just be aware of that.
    5
    GPS fine for me, i always edit the NTP to my local (au.pool.ntp.org) though

    Definitely less sim death and recovers far better from sim death it does have than XenonHD which id been using previously as my daily.

    Went all over Sydney today and didnt skip a beat

    We're finding out some sim issues while developing 10 source code.

    Keep tuned.
    There is a special build.prop fix to show complete unfiltered log messages.
    This should get to why sim death occurs.