Database Develop

[Q] [JB AOSP][How to compile to Captivate?}

My question is where can I find a guide for compile for AOSP JB ROM for Captivate?
I do have some knowledge in packaging ROM to a zip file.
I saw that there is an AOSP ROM called [JB 4.1.1] Monfro Aosp, but I couldn't find any open source repository for that.
I'm not looking for CM or AOKP, but merely AOSP.

The guide on the cm wiki will be close to the same, you just need to use the aosp repo instead of the cm one. Where is the aosp repo? I have no idea. Google is your friend, bout all i can say.

[discussion] Evervolv AOSP ROM

I am in no way a dev or contribute to this rom, other than flashing it. i noticed there wasn't a thread for evervolv rom for the grouper, but there are nightlies for it. If i'm violating any rules on xda i'll take this thread down.
"For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and Evervolv Project is made up of numerous members and contributors."
Right now the current source we are working on is Jellybean (Android 4.2.x)
You can find us on irc.freenode.net in #evervolv (or by using the web chat).
You can follow project updates on twitter via @preludedrew.
The Evervolv project source can be found on github.
Downloads:
ROM: Release, Nighlties
GAPPS

AW: [discussion] Evervolv AOSP ROM
Maybe I'm blind but I don't see neither a release nor a nightly for Grouper.

It's the one that says evervolv-mirus, it says grouper at the end of the file.
Evervolv-Mirus-3.2.0-Nightly-2013.03.08-grouper.ziphttp://dl.evervolv.com/static/n/2013.03.08/Evervolv-Mirus-3.2.0-Nightly-2013.03.08-grouper.zip
Sent from my Nexus 7 using Tapatalk 2

paranoid android85 said:
I am in no way a dev or contribute to this rom, other than flashing it. i noticed there wasn't a thread for evervolv rom for the grouper, but there are nightlies for it. If i'm violating any rules on xda i'll take this thread down.
"For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and Evervolv Project is made up of numerous members and contributors."
Right now the current source we are working on is Jellybean (Android 4.2.x)
You can find us on irc.freenode.net in #evervolv (or by using the web chat).
You can follow project updates on twitter via @preludedrew.
The Evervolv project source can be found on github.
Downloads:
ROM: Release, Nighlties
GAPPS
Click to expand...
Click to collapse
Is they're any screens shots or anymore info on this rom?
Sent from my Nexus 7 using Tapatalk HD

[Q] doubts about versions

Hello people.
What are the differences between the latest cyanogenmod nightlies and the latest cyanogenmod pershoot?
Thanks

Nightlies will have generic cm11 updates. I suspect pershoot cherry picks the ones he wants for our device tree.
Nightlies are not considered stable releases.

Xavier1966 said:
Hello people.
What are the differences between the latest cyanogenmod nightlies and the latest cyanogenmod pershoot?
Thanks
Click to expand...
Click to collapse
when i post a build (on droidbasement) its for testing device specific work prior to it being included in to mainline (nightlies, milestones, etc.).

Unified kernel for msm8974 devices

Unified kernel for msm8974 devices
hi all
we are cooking 1 kernel for all msm8974 devices for all custom roms
Source
https://github.com/sonyxperiadev/kernel
in this moment Z1 (honami) and Z2 (sirius) are tested
feel free to fork, joyn and push back
XDA:DevDB Information
Unified , Kernel for the Sony Xperia Z2
Contributors
jerpelea, Kali-, tilal6991, cdesai
Kernel Special Features:
Version Information
Status: Testing
Created 2014-10-07
Last Updated 2014-10-13

By "custom" you mean based on stock roms or AOSP-derived?

adwinp said:
By "custom" you mean based on stock roms or AOSP-derived?
Click to expand...
Click to collapse
both
depending on what an developer wants to build

What will the impact of this project be on areas that have been problems for aosp projects such as hardware drivers ?

furrypotato said:
What will the impact of this project be on areas that have been problems for aosp projects such as hardware drivers ?
Click to expand...
Click to collapse
1 kernel to rule them all means that 1 hal fixed in 1 device works on all devices
1 patch merged in kernel to fix something fixes same problem on all devices

jerpelea said:
1 kernel to rule them all means that 1 hal fixed in 1 device works on all devices
1 patch merged in kernel to fix something fixes same problem on all devices
Click to expand...
Click to collapse
I hope I'm not presumptuous or wrong: will it come with CWM and/or TWRP recovery versions?
Many thanks.

bonderbond said:
I hope I'm not presumptuous or wrong: will it come with CWM and/or TWRP recovery versions?
Many thanks.
Click to expand...
Click to collapse
this is just source code so depends on developers on what android fork is used

jerpelea said:
both
depending on what an developer wants to build
Click to expand...
Click to collapse
Unless I'm mistaken, the sony source doesn't work with pure AOSP. All AOSP or derivatives roms use the CM android_kernel_sony_msm8974pro or forks of it.
My question is thus the following: is this kernel source compatible with AOSP or like "kernel-copyleft", only with stock rom derivatives?
My custom kernel works on the latter, but I need to use the "msm8974pro" trees for pure AOSP.
Unless I'm missing something?

adwinp said:
Unless I'm mistaken, the sony source doesn't work with pure AOSP. All AOSP or derivatives roms use the CM android_kernel_sony_msm8974pro or forks of it.
My question is thus the following: is this kernel source compatible with AOSP or like "kernel-copyleft", only with stock rom derivatives?
My custom kernel works on the latter, but I need to use the "msm8974pro" trees for pure AOSP.
Unless I'm missing something?
Click to expand...
Click to collapse
it works perfectly on aosp and derivates

new guides published
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/

kernel is rebased
z3 platform (shinano) added to kernel
https://github.com/sonyxperiadev/kernel/commits/aosp/LNX.LA.3.5.1-01110-8x74.0
status
z1 - bringup in progress
z2 - boots
z3 - boots
feel free to push fixes

broadcom wifi is now merged in kernel

crash has been fixed
broadcom wifi crash fixed

Can't boot
@jerpelea I've compiled AOSP Lollipop and it boots fine. I've compiled the kernel from 3.5.2.2 branch of the unified kernel source and successfully made zImage. I've combined the zImage with the resulting dtb and the ramdisk from the AOSP build. I can't get the device to boot for some reason. It's stuck at the Sony boot logo. Did I miss a step ? I've searched online but couldn't get enough help about this.
Tried the same with Kitkat too but same result. Doesn't go past the sony boot logo.
UPDATE
Got it to work The command line argument in the guide provided has android boot device as qcom whereas the one compiled during AOSP has it as "shinano" Took me 1 build to understand this Back to work again

hi All
Busy weeks ....months ...
Progress so far
- unified 3.4 kernel is stable for daily use and community tweaking
As some of you have already seen we have started work on comunity 3.10 unified kernel
This kernel is not finished and not stable but is an invitation for developers to joyn, test and improve a kernel built "by community for community"
Br
J

build guide has been updated for easy reading
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/

hi all
kernel 3.10 is progressing nice
it can soon be used on SONY AOSP Project
master branch on devices uses 3.10 kernel
l-mr0 branch uses 3.4 kernel
br
J

hi all
3.10 is progressing nice
at this point can be used for L MR1 and shows good battery savings
more enhancements and bugfixes will come soon
br
J

Hi @jerpelea, which of the branches should be used for the 3.10 kernel?

I ll be appreciated that the unified kernel can support d6563.

Any roms with the official source code???

Is there any rom with the official kernel sources??

Ivan's AOSP 4.4.4 and 5.0

NisseCool said:
Ivan's AOSP 4.4.4 and 5.0
Click to expand...
Click to collapse
Are you sure they are with official kernel? possible to post link?

pra300 said:
Are you sure they are with official kernel? possible to post link?
Click to expand...
Click to collapse
Yes i am sure. It's a developer working on xiaomi who made it. Here is the android 5.1 from him http://forum.xda-developers.com/xiaomi-mi-3/general/android-5-1-ivan-t3056153 and here is 4.4.4 http://en.miui.com/thread-44424-1-1.html

Ivan has a privat source. Not official.

These are the ones with official sources.
Try Bitti09's CM12:
http://forum.xda-developers.com/xiaomi-mi-3/development/rom-cyanogenmod-12-t3036066
(Link in thread posts)
Or audahadi's Temasek builds:
http://forum.xda-developers.com/xiaomi-mi-3/development/temasek-unofficial-cm12-t3012588
I should warn you, the official kernels are VERY unstable as of now, and the Devs are working on them as we speak...Expect a LOT of bugs.
(Wifi not working, bootloops, reboots, battery drain, pretty much everything is a WIP at this stage...)

NisseCool said:
Yes i am sure. It's a developer working on xiaomi who made it. Here is the android 5.1 from him http://forum.xda-developers.com/xiaomi-mi-3/general/android-5-1-ivan-t3056153 and here is 4.4.4 http://en.miui.com/thread-44424-1-1.html
Click to expand...
Click to collapse
Thanks for the links, 5.1 is not having official kernel and the 4.4.4 build is of Sept. 2014.... I did not find latest build.

The Dork Knight Rises said:
I should warn you, the official kernels are VERY unstable as of now
Click to expand...
Click to collapse
Do you think it could be some old kernel sources? May be MIUI uses some other kernel sources?
Or it is possible that MIUI devs did the same work as our dev do right now - fixing bugs in kernel sources?
I'm just trying to understang how it works
If MIUI have no bugs so either it basd on different kernel sources or MIUI devs already fixed all kernel sources bugs but not within branch released and within MIUI code instead.
PS: Sorry, I'm C# dev, not firmware dev, so have no clue how those things works :silly: