• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Unofficial AOSP Builds

Nupich said:
Other builds aren't going well, getting msm8926 defconfig undefined from the kernel. I've tried the KK and CM-11 branches. Not sure what I broke but even Carbon won't work now.

Somcom, any idea what my manifest should look like?

P.S. The wifi problem is that module not loading one you had before.
Click to expand...
Sorry nupich,
Haven't pushed that file yet.
Go to your boardcondigcommon.mk in you msm8226-common device tree and change the defconfig define to msm8226_mmi_defconfig

Then your going to have to add the line for the peregrine in your defconfig.
I can do it for you later if you want.
But on these 2g speeds, I might quit on it.

I'll be on irc later hopefully.
 
somcom3x said:
Sorry nupich,
Haven't pushed that file yet.
Go to your boardcondigcommon.mk in you msm8226-common device tree and change the defconfig define to msm8226_mmi_defconfig

Then your going to have to add the line for the peregrine in your defconfig.
I can do it for you later if you want.
But on these 2g speeds, I might quit on it.

I'll be on irc later hopefully.
Click to expand...

Ahhh, fair enough. That makes sense. Yeah, do it later if you can, I'm going to be off for most of today anyway but I'll try some building when I get back.

Could you give me an idea of the manifest I'll need as well? Just want to make sure that's not the issue.
 
After testing a lot, I've discovered the most updated combination that works is this one: nupich build from 08/05 + audio fix patch... Everything works including apolo (after audio patch)...
 
Isn't the #2 build from Shabby's 7/31 working fine? Why even bother with the others. I got everything I need. Music, gps, gyro, wifi, LTE.
 
What's this audio patch? I haven't heard anything about it?

As for 'why bother', because it helps us port other ROMs and keep up to date. Also, we can't reproduce 7/31.
 
Ohhhh, that's how multi quote works...

eteles said:
After testing a lot, I've discovered the most updated combination that works is this one: nupich build from 08/05 + audio fix patch... Everything works including apolo (after audio patch)...
Click to expand...

What's this audio patch? I had one bad build once but it that was it for me .-.

hollow021 said:
Isn't the #2 build from Shabby's 7/31 working fine? Why even bother with the others. I got everything I need. Music, gps, gyro, wifi, LTE.
Click to expand...

Because it keeps us up to date, lets us build other ROMs with new features and we can't reproduce that build again.

Termy said:
n1, looking forward to it :D
building carbon, too?
Click to expand...

Trying! Having some issues with the other ROMs though, I'll work with somcom to fix them when we both have time and internet :)

At the moment Slim's getting

Code: 
rameworks/native/libs/ui/GraphicBufferAllocator.cpp: In member function 'android::status_t android::GraphicBufferAllocator::alloc(uint32_t, uint32_t, android::PixelFormat, int, const native_handle_t**, int32_t*, uint32_t)':
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:115:26: error: 'alloc_device_t' has no member named 'allocSize'
Which I'm fairly certain is a result of aosp changes breaking things. Hopefully tomorrow it'll be gone.

Carbon's still building at the moment, which is promising. No clue if wifi will work or not though but I repo synced so fingers crossed Carbon fixed our issue upstream!

And if anyone has any clue how to get builds running on Vanir, that'd be great. At the moment I'm getting
Code: 
Don't have a product spec for: 'vanir_peregine'
with manifest
Code: 
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
  <remote fetch="git://github.com/" name="peregrine" />
  <project name="OUDhs/android_device_motorola_peregrine" path="device/motorola/peregrine" remote="peregrine" revision="kk" />
  <project name="OUDhs/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="peregrine" revision="kk" />
  <project name="OUDhs/proprietary_vendor_motorola" path="vendor/motorola" remote="peregrine" revision="kk" />
  <project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="peregrine" revision="cm-11.0" />
  <project name="CyanogenMod/android_device_motorola_qcom-common" path="device/motorola/qcom-common" remote="peregrine" revision="cm-11.0" />
  <project name="somcom3x/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="peregrine" revision="kk2" />
  <project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="peregrine" revision="cm-11.0" />
  <project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="peregrine" revision="cm-11.0" />
  <project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="peregrine" revision="cm-11.0" />
</manifest>

Pretty much used the Carbon manifest. Maybe it's closer to Slim?

So y'all know, I'm just a builder at the moment, Shabby and somcom are doing all the hard work and they're responsible for things working, I just mash their work with a bunch of other people's work and hope something good comes out :p
 
Nupich said:
Ohhhh, that's how multi quote works...



What's this audio patch? I had one bad build once but it that was it for me .-.



Because it keeps us up to date, lets us build other ROMs with new features and we can't reproduce that build again.



Trying! Having some issues with the other ROMs though, I'll work with somcom to fix them when we both have time and internet :)

At the moment Slim's getting

Code: 
rameworks/native/libs/ui/GraphicBufferAllocator.cpp: In member function 'android::status_t android::GraphicBufferAllocator::alloc(uint32_t, uint32_t, android::PixelFormat, int, const native_handle_t**, int32_t*, uint32_t)':
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:115:26: error: 'alloc_device_t' has no member named 'allocSize'
Which I'm fairly certain is a result of aosp changes breaking things. Hopefully tomorrow it'll be gone.

Carbon's still building at the moment, which is promising. No clue if wifi will work or not though but I repo synced so fingers crossed Carbon fixed our issue upstream!

And if anyone has any clue how to get builds running on Vanir, that'd be great. At the moment I'm getting
Code: 
Don't have a product spec for: 'vanir_peregine'
with manifest
Code: 
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
  <remote fetch="git://github.com/" name="peregrine" />
  <project name="OUDhs/android_device_motorola_peregrine" path="device/motorola/peregrine" remote="peregrine" revision="kk" />
  <project name="OUDhs/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="peregrine" revision="kk" />
  <project name="OUDhs/proprietary_vendor_motorola" path="vendor/motorola" remote="peregrine" revision="kk" />
  <project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="peregrine" revision="cm-11.0" />
  <project name="CyanogenMod/android_device_motorola_qcom-common" path="device/motorola/qcom-common" remote="peregrine" revision="cm-11.0" />
  <project name="somcom3x/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="peregrine" revision="kk2" />
  <project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="peregrine" revision="cm-11.0" />
  <project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="peregrine" revision="cm-11.0" />
  <project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="peregrine" revision="cm-11.0" />
</manifest>

Pretty much used the Carbon manifest. Maybe it's closer to Slim?

So y'all know, I'm just a builder at the moment, Shabby and somcom are doing all the hard work and they're responsible for things working, I just mash their work with a bunch of other people's work and hope something good comes out :p
Click to expand...

Really enjoying that multi-quote I see :P
 
hollow021 said:
Isn't the #2 build from Shabby's 7/31 working fine? Why even bother with the others. I got everything I need. Music, gps, gyro, wifi, LTE.
Click to expand...
Apollo doesn't work properly... For example: you get music after pressing play, but after pressing pause it is takes long untill music stops... Or it just force closes...
 
Me too ..
I used Appollo ! It's just perfect but i'm using a Build #2 of 31/07,
i think you have the problem on these ..
I have xt1039 of moto g ?

-bd314
 
Thanks guys for all the hard work!

Did you know that the hardware also supports ANT+?
It's not supported in the stock rom, but there's a patch for OUDhs/android_device_motorola_peregrine on pastebin. It should apply cleanly to the current commit 1d625a9cff

I'm not allowed to post links in my first message, so please go to VDnE8Gv7 on pastebin.com :D
 
ant_for_moto_g said:
Thanks guys for all the hard work!

Did you know that the hardware also supports ANT+?
It's not supported in the stock rom, but there's a patch for OUDhs/android_device_motorola_peregrine on pastebin. It should apply cleanly to the current commit 1d625a9cff

I'm not allowed to post links in my first message, so please go to VDnE8Gv7 on pastebin.com :D
Click to expand...

I don't have commit access but if someone wants to give me it or patch it themselves, sure :D

Nupich said:
Ugh, Carbon failed with Java errors :/

Ant sounds fun but it's not much use to me yet since it breaks Xposed D:
Click to expand...

Figured out Carbon, seems to be building now :D

Shabbypenguin said:
Ant != Art
Click to expand...

That was silly of me. I forgot that existed .-.
 
Hey Nupich, seems your carbon has build :D
unfortunately, something seems to be very wrong with it - won't boot at all.
The short vibration on boot-up occurs, but then the Motorola-Logo stays there and nothing happens :/
I tried clean install (wiping dalvik, data, cache and system) from the old carbon-build and from stock, both the same...i noticed the "carbon_peregrine-ota-5a7242bac1.zip" file and tried it - same behaviour :/

will try a dirty flash now, but don't have much hope :(

edit: dirty flash from stock (simply flashing without wiping) doesn't help...at home i should still have to old build with broken wifi, when im back home i will try dirty from this build...
 
I'm not sure where the idea that dirty flashing a build is a good idea came from but I don't expect it'll help anything. Installing a ROM formats /system anyway so all that's left should be /data.

The current Carbon build might be broken because I mixed some stuff up in the middle of building it. Cleaning now and doing another one.

The OTA zips are for updates through CarbonDelta or whatever it's called. They're not ROMs in their own right.

P.S. Slim is having issues with Bluetooth now. CM is compiling fine and I did another build yesterday because I could.
 
i'm not a fan of dirty either ;)
just wanted to test if it helps because i thought you'll be asleep longer :D

but good to know that you figured the problem out...thanks again for your efforts :thumbup:
 
You must log in or register to reply here.
Back
Top Bottom