Search results

For those asking, o builds have been discontinued. Whatever happens next will happen in p which is WIP.

There is a changelog app for you to see that, else Gerrit. The new changes won't be there on your phone currently anyway, they'll come to you with the next weekly.

Those who want can join the Telegram group (now linked in the second pest) for discussion, troubleshooting and help with debugging issues. And of course jira is also open for reporting issues as well.

Reserved

Credits: mdeejay khan_frd2002 Bugs: You tell me How to flash: - Download Rom && Gapps - Boot into recovery && full wipe - Flash rom && Gapps - Boot - Update with weeklies from then on Requirements to report a bug: - Make sure that you aren't using a custom kernel or any system mod -...

About Omni The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there.*Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented...

As I don't have the athene anymore this thread is being closed, Jleeblanch will be taking over later.

No, straight up removing/ignoring is pretty certainly going to produce a broken build, the correct steps here is to identify what's missing and add them. Don't simply tell people to do that if you can't provide useful assistance.

You're missing some repos, grab the modules that are sending errors, the one after the missing following the error and search for them in another ROM's repo/online org that you know compiles fine without those errors and sync the repos required. The pretty obvious guess here is you missing some...

updated, check https://review.carbonrom.org/#/q/status:merged between 20th april-2nd may for changelog

Updated, link in the op. For changelog check https://review.aosiprom.com/#/q/status:merged between 19th April to now.

Nothing device side, for rom side check https://review.carbonrom.org/#/q/status:merged between 12th and 20th April.

updated,link in the op.

Reserved

Credits: Team athene Nikit golden-guy Bugs: Flashlight toggle Video recording Sepolicy permissive You tell me How to flash: - Download Rom && Gapps - Boot into recovery && full wipe - Flash rom && Gapss - Boot Requirements to report a bug: - Make sure that you aren't using a custom kernel...

**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! **** Android Open Source illusion Project About us: AOSIP is a quality custom rom based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability...

What gapps you used?

cr-6.1 is up,link in the op. For anyone who might ask,no talk of official until remaining major bugs are fixed.

Lineage sdk is to be synced in /lineage-sdk not in the vendor directory, resync and then clean build.

You actually will have to pull the console-ramoops (Google this) not the traditional last_kmsg (this slipped out of my mind). Also mido sources aren't going to work out of the box with oxygen so it's better to grab actual oxygen sources and try to update them for Oreo instead, can use mido and...

You probably should link this in the op I guess, as it gets asked a lot.

Sync lineagesdk (search on this if you don't know what that is). It'll require a eng build (a bit of searching will tell you about that).

Well this looks pretty useful, before posting here it's better to search in-depth (Google/github/gerrits/XDA).

It's defined as lineageos in the original repo, you probably edited wrong or something? Anyway post the full log alongside your modified sources.

The path should be /lineage-sdk. Don't confuse up - with _ as it's only the latter (at least in Lineage) that's used for guiding path.

You have lineagesdk synced?

Check this as a reference.

That's not a solution. Either remove configpanel or edit them to point to lineage instead of cm, it's asking for the sdk that was rebranded in Oreo from cmsdk to lineagesdk.

Still, doing such changes device side is a cleaner approach and will prevent even the "maybe" problems from occurring.

Either sync lineagesdk (check los GitHub) or remove whatever is asking for it.

Keeping the original commit authorship is enough, that's why it's open source.

This is a place to get guidance not to get spoonfed, you'll need some technical knowledge and know how with Linux before starting with the building of kernels. The guides here on those topics mostly assume you know you're way around the basics and have a bit of experience, if you don't then...

Use hastebin or some other paste service for posting logs (everybody), As for the error pretty sure it has been discussed in this thread several times before (also elsewhere on the internet) so search first. Have you tried uninstalling and reinstalling Jack?

Yes the aosp app packages aren't Gradle based Android studio supported projects (they use make as you can see) so you gotta manually edit them and compile in the ROM project directory generally. You're missing a module, grab whatever is between / and intermediates in the error and search for...

Not directly, this has been discussed on this thread before so scroll back/search.

Are the hardware components similar? If you're sure enough then try. Possibly a derp on the ROM side, check previous commits for the file where the errors are coming from. Yes...? The context of these?

You'll have to commit necessary changes to get the kernel to boot nougat, or any newer version of Android. No direct guide for that, check sources of devices with similar hardware to the one you have and try.

Don't edit something in .repo/manifests manually, if you wanna remove a project or add it's modified fork of yours then use the remove-project tag in local manifest. Seeing as other things you've been told are not working try init repo in another directory then manually copy/paste the...

As you've already been told, and for a more in depth/quick process you can try this About the device sources, if there's none in GitHub then you'll have to try looking for a device that has similar hardware as yours (the soc and architecture, camera, display etc.) And try to make necessary...

Adding to what was already said, you can also search for the commits in your local clone using grep git log --grep=*whatever you're searching for*

Says the module is defined in 2 places, delete the one from hardware/ril/libril.

You can't really just upstream from one mainline version (3.4/3.10/4.4) to another mainline version (3.18/4.12), they're separate branches. Can only upstream the same branch as your kernel-in-question.

Nope, not like that.

Sync qcom Hals for your chipset from Lineage, searching more on this forum with that error will tell you in details. Also, post your logs in a paste service like hastebin rather than posting a screenshot.

Sync lineagesdk and see.

Rebooting only restarts the system and factory reset wipes the data partition which will do nothing to a system mod. Your best bet is to flash back the stock ROM then root and try to reproduce the problem and report to the v4a thread with logs and other info. If you think they're compromised...

What? Check his GitHub and do a general search there...

That repo haven't been updated to support building Oreo, so you got 2 choices now: 1. Wait for someone to do it. 2. Study other repos, learn+try and diy. There's no set guide for such as it'll differ device to device, so check the sources of the other devices that have been brought up to Oreo...

Not seeing any new error there, rather the same old unsupported overlay. Go to device/motorola/msm8916-common/overlay/packages/apps/Bluetooth/res/values/config.xml and simply remove the line, disabling/removing overlays not present in roms from devices trees have been discussed here myriad of...

As what neonkat said, check these local manifests for a reference if you still don't get it In short device(where device trees are placed)/*the name of the manufacturer of your device*/*the codename of your device* So the redmi note 4 from xiaomi that has the codename mido will go to...