Database Users

Android 3.2 source code available

Just wondering...
Does this mean we can bake an SGS2 ROM with Android 3.2 now, or are the listed caveats insurmountable?
Android 3.2 source code available
As usual, and just like we had done before for Android 3.0 and 3.1,
the source code for the GPL and LGPL components of Android 3.2 is
available in the Android Open-Source Project, under the tag
android-3.2_r1
The process to build it is the same as what we had for 3.0 and 3.1:
# start from a master client
repo init -m 3.2-base.xml
repo sync
repo forall -c git checkout android-3.2_r1
# build with the regular process
# to come back to a plain master
repo init -m default.xml
repo sync
The caveats are unchanged since 3.1:
-the checkout command will return an error message because the tag
doesn't exist in all projects, ignore it.
-the compiled isn't any more likely to work on actual hardware as 3.1
did, since the same binary incompatibilities are still there.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Tsais said:
Just wondering...
Does this mean we can bake an SGS2 ROM with Android 3.2 now, or are the listed caveats insurmountable?
Android 3.2 source code available
As usual, and just like we had done before for Android 3.0 and 3.1,
the source code for the GPL and LGPL components of Android 3.2 is
available in the Android Open-Source Project, under the tag
android-3.2_r1
The process to build it is the same as what we had for 3.0 and 3.1:
# start from a master client
repo init -m 3.2-base.xml
repo sync
repo forall -c git checkout android-3.2_r1
# build with the regular process
# to come back to a plain master
repo init -m default.xml
repo sync
The caveats are unchanged since 3.1:
-the checkout command will return an error message because the tag
doesn't exist in all projects, ignore it.
-the compiled isn't any more likely to work on actual hardware as 3.1
did, since the same binary incompatibilities are still there.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Click to expand...
Click to collapse
honeycomb is just meant for tablets not cellphones..

ditto to the guy above me...
and this belongs in general, read the damn stickies!
We have known for about week now as well... thanks for the old news!
<Ninpo> rofl it's only the GPL and LGPL components
<Ninpo> so not the full thing by a long shot since most of Android is Apache licensed

Also, this is only the LGPL and GPL components, which is a hell of a long shot away from being actual Honeycomb sources, since most of Android is under the Apache license.

I remember reading that Google will release full source code for Honeycomb some time after Ice Cream Sandwich release.

Source code OMX ST-Ericsson

Hi, I found in the Galaxy S Advance Forum have posted a zip file containing source code OMX ST-Ericsson on Xperia U's Android Development Thread named "[ROM] [NIGHTLY] [TeamCanjica][UB] Unofficial CyanogenMod 10.1". No way around it but here is the download link for developers who are interested in this mediafire.com/download/hzg68480ecjozpy/vendor.zip

pabloo.b said:
Hi, I found in the Galaxy S Advance Forum have posted a zip file containing source code OMX ST-Ericsson on Xperia U's Android Development Thread named "[ROM] [NIGHTLY] [TeamCanjica][UB] Unofficial CyanogenMod 10.1". No way around it but here is the download link for developers who are interested in this mediafire.com/download/hzg68480ecjozpy/vendor.zip
Click to expand...
Click to collapse
That source look quite nice. There isn`t any binary elements and even have some documentation.

MateuszKrawczuk said:
That source look quite nice. There isn`t any binary elements and even have some documentation.
Click to expand...
Click to collapse
and you know if someone could prove or see if any of this serve?

pabloo.b said:
and you know if someone could prove or see if any of this serve?
Click to expand...
Click to collapse
there are 2 main folders, connectivity and multimedia
in connectivity we have something related to wlan
in multimedia we have a some files to generate the code and some documentatation
i dont think this is the NovaThor U8420
as far as i know the u8420 is a clone of the u8500 made specific for the s3 mini, some users where able to flash the xperia u kernel with overclock to 1.15>Ghz with afew side effects...
this is what is written in th readme of the "kernel"
note the date is from 2009
Bellagio OpenMAX Integration Layer 1.1.2 project
Release 0.9.2.1
This is an Open Source implementation of the OpenMAX Integration Layer
(IL) API ver. 1.1.2, specified by the Khronos group (see
http://www.khronos.org/openmax).
This package includes the libomxil-bellagio shared library together with the
following OpenMAX components (built as separate shared objects and
loaded at runtime):
CORE FUNCTIONALITIES
- An IL core
- A component loader for static libraries for Linux
- A simple resource manager
- A framework of components and ports base classes for Bellagio Hierarchy
- a draft support to content pipes
AUDIO
- OMX audio volume control
- OMX audio mixer component
VIDEO
- a video scheduler connected to a clock component for video synchronization
CLOCK
- OMX Clock component. It take audio(default) as input reference clock
and provide media clock to video sink and other component. It support
fast forward and rewind.
=============================
IMPORTANT NOTE
=============================
All the other components present in the old versions of Bellagio
are distributed from the 0.9.2 on as external packages maintained separately.
If you need more details you can check the download page in the Bellagio web site:
http://omxil.sourceforge.net/downloads.html
=============================
BUILD the bellagio library
=============================
autoreconf -i -f $(source_path)
$(source_path)/configure
make
make install
make check
Before attempting to run any test, the OMX components *must* be
registered with the command "omxregister-bellagio".
omxregister-bellagio components_path1:components_path2
That will create a registry file that will contain all the components
installed in the specified directories. By default the components
distributed with this package are installed in /usr/local/lib/bellagio
and the registry entries are stored in the file $HOME/.omxregister
The location of registry file can be changed setting the environment variable
OMX_BELLAGIO_REGISTRY to the location and name of the new register file.
Note: the default location for the installation is TARGET=/usr/local/lib
for the library, and the component will be installed in TARGET/bellagio
To change the installation directory execute the configure as in the example:
$(source_path)/configure --prefix=new_installation_path
=============================
TEST
=============================
The following simple test applications are provided:
test/components/audio_effects/omxvolcontroltest
test/components/audio_effects/omxaudiomixertest
test/components/resource_manager/omxrmtest
TEST USAGE
----------------------------------------------
Usage: omxvolcontroltest [-o outfile] [-g gain] filename
-o outfile: If this option is specified, the output stream is
written to outfile otherwise redirected to std
output
-g: Gain of PCM data [0...100]
-h: Displays this help
Usage: omxaudiomixertest [-o outfile] [-gi gain] -t -r 44100 -n 2 filename1 filename2 [filename3] [filename4]
-o outfile: If this option is specified, the output stream is
written to outfile otherwise redirected to std
output; Can't be used with -t.
-gi : Gain of stream i[0..3] data [0...100]
-t : The audio mixer is tunneled with the ALSA sink;
Can't be used with -o
-r 44100 : Sample Rate [Default 44100]
-n 2 : Number of channel [Default 2]
-h : Displays this help
The omxvolcontroltest and omxaudiomixertest receive as input an audio decompressed stream.
If an output file is produced yet another uncompressed audio stream is written.
The purpose of these tests is to verify the correct behavior of audio effects volume control ands audio mixer.
If any developer is interested in a full multimedia chain with codecs also please refer to the external components
and relates tests. A set of application using many components is also provided as a separate package.
For further details go to the download page of the Bellagio web pages:
http://omxil.sourceforge.net/downloads.html
=============================
BUILD RPM
=============================
- To build RPM:
make dist
cp libomxil-bellagio-0.9.2.tar.gz $HOME/rpmbuild/SOURCES/
rpmbuild -bb libomxil-bellagio.spec
=============================
BUILD DEB
=============================
To build the installable deb package with the Bellagio libraries run:
sudo checkinstall --pkgsource=/home/urlinigi/OpenMAX/sourceforge/omxil --install=no [email protected] --spec=/home/urlinigi/OpenMAX/sourceforge/omxil/libomxil-bellagio.spec --inspect
=============================
SOURCE CODE PACKAGE
=============================
There are two ways to generate the source code package. One is provided by the
makefile internal structure, running the following command:
make dist
In Ubuntu system is also available the debian mechanism to build a
source code package, running the following instructions, in the base
directory of the source code:
dpkg-buildpackage -S
=============================
DITRIBUTIONS
=============================
This version has been tested on:
- UBUNTU 9.10
- Fedora Core 11
Last modified: Dec 23, 2009
Click to expand...
Click to collapse

From what I've read, the only difference between NovaThor U8500 and U8420 is the Thor (modem-part).
U8420 doesn't have the HSPA+ modem. Other than that it's the same...I think

tys0n said:
From what I've read, the only difference between NovaThor U8500 and U8420 is the Thor (modem-part).
U8420 doesn't have the HSPA+ modem. Other than that it's the same...I think
Click to expand...
Click to collapse
Where did you read it?
Sent from my GT-I8190 using Tapatalk 4

tys0n said:
From what I've read, the only difference between NovaThor U8500 and U8420 is the Thor (modem-part).
U8420 doesn't have the HSPA+ modem. Other than that it's the same...I think
Click to expand...
Click to collapse
ppero196 said:
Where did you read it?
Sent from my GT-I8190 using Tapatalk 4
Click to expand...
Click to collapse
I can't remember where it was and I can't find it now. Somwhere I read that U8420 is a scaled down U8500 and that is was the modem that was scaled down. When looking at the specs it all made sense but I can't be 100% sure.

We have Bellagio sources from a few months Even Samsung published them
What is Bellagio?
OMX on our phone are from Symbian (yes, the same Symbian which you could have ealier on your Nokia). Bellagio is wrapper to use OMX from Symbian on Android. It's available on GPL license, so STE/Samsung has to publish its sources.

New Macław said:
We have Bellagio sources from a few months Even Samsung published them
What is Bellagio?
OMX on our phone are from Symbian (yes, the same Symbian which you could have ealier on your Nokia). Bellagio is wrapper to use OMX from Symbian on Android. It's available on GPL license, so STE/Samsung has to publish its sources.
Click to expand...
Click to collapse
wonderful!!

[q] product_build_prop_overrides

Hey guys,
I done build for p5100 & p5110 but my sound is broken because of build.prop bad product name.
for the build i have product name of p5110 but for the build.prop i need espresso10wifixx
so I use
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=espresso10rfxx TARGET_DEVICE=espresso10rf BUILD_FINGERPRINT=samsung/espresso10rfxx/espresso10rf:4.0.3/IML74K/P5100XWALE2:user/release-keys PRIVATE_BUILD_DESC="espresso10rfxx-user 4.0.3 IML74K P5100XWALE2 release-keys"
into my custom_p5110.mk
But this do not override my build.prop and let the product_name as custom_p5110.
How can i solve this?

sevenup30 said:
Hey guys,
I done build for p5100 & p5110 but my sound is broken because of build.prop bad product name.
for the build i have product name of p5110 but for the build.prop i need espresso10wifixx
so I use
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=espresso10rfxx TARGET_DEVICE=espresso10rf BUILD_FINGERPRINT=samsung/espresso10rfxx/espresso10rf:4.0.3/IML74K/P5100XWALE2:user/release-keys PRIVATE_BUILD_DESC="espresso10rfxx-user 4.0.3 IML74K P5100XWALE2 release-keys"
into my custom_p5110.mk
But this do not override my build.prop and let the product_name as custom_p5110.
How can i solve this?
Click to expand...
Click to collapse
Might need to pull in a patch to support PRODUCT_BUILD_PROP_OVERRIDES... Won't be able to look at this for a few days.

All right thank you, I'll do it by hand until this.

[ROM] [Unofficial] | AOSPA 4+ | Weekly Update

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Paranoid Android is a custom rom focused on open devices.
We aim to not simply add to Android but extend it, utilizing the same design philosophies Google uses with AOSP (Android Open Source Project).
AOSPA General Changelog​
Quote:
Code:
#include
/*
* Your warranty is now not void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Installation Instruction
New Install
Be on a KitKat ROM before flashing
You must have a custom recovery installed that allows SELinux.
Download the Xiaomi Mi3 build .
Download the gapps
Disable True Dual Boot
Fully wipe is highly recommended.
Install AOSPA on System 1
Wipe Dalvik and Cache
Reboot
Updating
Download rom and install
Reboot
AOSPA Cancro Download Link
Useful Link
AOSPA Official Page
AOSPA Legacy Google+ Community
MIUI Forum Community
Credits
varun.chitre15, qiwu, linuxxxx, Shahan_mik3,MI3 Cancro Devs, AOSPA Devs, Cyanogenmod Devs, Omni Dev, Community

Bugs :
What generally cm/aospa have
Random reboot (deep sleep & in call)..workaround for now
HDR not working
USB otg not working
Will be added in the journey..still fresh.
How To Build From Source
CAUTION : My work is a mess cause I'm not that good at dev. Sometime build may will break or device won't boot.
Mi3 cancro device tree
Mi3 cancro vendor tree
AOSPA Legacy Source : repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat
Local Manifest
Build script
#!/bin/bash
# Version 2.0.4, Adapted for AOSPA.
export USE_CCACHE=1
export CCACHE_DIR=/media/audahadi/b6234e42-ff56-4372-956d-184e596b9e3e/audahadi/.ccache
# We don't allow scrollback buffer
echo -e '\0033\0143'
clear
# Get current path
DIR="$(cd `dirname $0`; pwd)"
OUT="$(readlink $DIR/out)"
[ -z "${OUT}" ] && OUT="${DIR}/out"
# Prepare output customization commands
red=$(tput setaf 1) # red
grn=$(tput setaf 2) # green
blu=$(tput setaf 4) # blue
cya=$(tput setaf 6) # cyan
txtbld=$(tput bold) # Bold
bldred=${txtbld}$(tput setaf 1) # red
bldgrn=${txtbld}$(tput setaf 2) # green
bldblu=${txtbld}$(tput setaf 4) # blue
bldcya=${txtbld}$(tput setaf 6) # cyan
txtrst=$(tput sgr0) # Reset
# Local defaults, can be overriden by environment
: ${PREFS_FROM_SOURCE:="false"}
: ${THREADS:="$(cat /proc/cpuinfo | grep "^processor" | wc -l)"}
# If there is more than one jdk installed, use latest 6.x
if [ "`update-alternatives --list javac | wc -l`" -gt 1 ]; then
JDK6=$(dirname `update-alternatives --list javac | grep "\-6\-"` | tail -n1)
JRE6=$(dirname ${JDK6}/../jre/bin/java)
export PATH=${JDK6}:${JRE6}:$PATH
fi
JVER=$(javac -version 2>&1 | head -n1 | cut -f2 -d' ')
# Import command line parameters
DEVICE="$1"
EXTRAS="$2"
# Get build version
MAJOR=$(cat /media/audahadi/b6234e42-ff56-4372-956d-184e596b9e3e/audahadi/AOSPAL/vendor/pa/vendor.mk | grep 'ROM_VERSION_MAJOR := *' | sed 's/ROM_VERSION_MAJOR := //g')
MINOR=$(cat /media/audahadi/b6234e42-ff56-4372-956d-184e596b9e3e/audahadi/AOSPAL/vendor/pa/vendor.mk | grep 'ROM_VERSION_MINOR := *' | sed 's/ROM_VERSION_MINOR := //g')
MAINTENANCE=$(cat /media/audahadi/b6234e42-ff56-4372-956d-184e596b9e3e/audahadi/AOSPAL/vendor/pa/vendor.mk | grep 'ROM_VERSION_MAINTENANCE := *' | sed 's/ROM_VERSION_MAINTENANCE := //g')
TAG=$(cat /media/audahadi/b6234e42-ff56-4372-956d-184e596b9e3e/audahadi/AOSPAL/vendor/pa/vendor.mk | grep 'ROM_VERSION_TAG := *' | sed 's/ROM_VERSION_TAG := //g')
if [ -n "$TAG" ]; then
VERSION=$MAJOR.$MINOR$MAINTENANCE-$TAG
else
VERSION=$MAJOR.$MINOR$MAINTENANCE
fi
# If there is no extra parameter, reduce parameters index by 1
if [ "$EXTRAS" == "true" ] || [ "$EXTRAS" == "false" ]; then
SYNC="$2"
UPLOAD="$3"
else
SYNC="$3"
UPLOAD="$4"
fi
# Get start time
res1=$(date +%s.%N)
echo -e "${cya}Building ${bldcya}AOSPA $VERSION for $DEVICE ${txtrst}";
echo -e "${bldgrn}Start time: $(date) ${txtrst}"
# Decide what command to execute
case "$EXTRAS" in
threads)
echo -e "${bldblu}Please enter desired building/syncing threads number followed by [ENTER]${txtrst}"
read threads
THREADS=$threads
;;
clean|cclean)
echo -e "${bldblu}Cleaning intermediates and output files${txtrst}"
export CLEAN_BUILD="true"
[ -d "${DIR}/out" ] && rm -Rf ${DIR}/out/*
;;
esac
echo -e ""
export DEVICE=cancro
# Fetch latest sources
if [ "$SYNC" == "true" ]; then
echo -e ""
echo -e "${bldblu}Fetching latest sources${txtrst}"
repo sync -j"$THREADS"
echo -e ""
fi
if [ ! -r "${DIR}/out/versions_checked.mk" ] && [ -n "$(java -version 2>&1 | grep -i openjdk)" ]; then
echo -e "${bldcya}Your java version still not checked and is candidate to fail, masquerading.${txtrst}"
JAVA_VERSION="java_version=${JVER}"
fi
if [ -n "${INTERACTIVE}" ]; then
echo -e "${bldblu}Dropping to interactive shell${txtrst}"
echo -en "${bldblu}Remeber to lunch you device:"
if [ "${VENDOR}" == "pa" ]; then
echo -e "[${bldgrn}lunch pa_$DEVICE-userdebug${bldblu}]${txtrst}"
else
echo -e "[${bldgrn}lunch full_$DEVICE-userdebug${bldblu}]${txtrst}"
fi
bash --init-file build/envsetup.sh -i
else
# Setup environment
echo -e ""
echo -e "${bldblu}Setting up environment${txtrst}"
. build/envsetup.sh
echo -e ""
# lunch/brunch device
echo -e "${bldblu}Lunching device [$DEVICE] ${cya}(Includes dependencies sync)${txtrst}"
export PREFS_FROM_SOURCE
lunch "pa_$DEVICE-userdebug";
echo -e "${bldblu}Starting compilation${txtrst}"
mka bacon
fi
echo -e ""
# Get elapsed time
res2=$(date +%s.%N)
echo -e "${bldgrn}Total time elapsed: ${txtrst}${grn}$(echo "($res2 - $res1) / 60"|bc ) minutes ($(echo "$res2 - $res1"|bc ) seconds)${txtrst}"
Note 2 : Change this path "/media/audahadi/b6234e42-ff56-4372-956d-184e596b9e3e/audahadi" to your working directory
Note 3 : Add this to vendor/pa
Path : vendor/pa/vendorsetup.sh
add_lunch_combo pa_cancro-userdebug
Path : vendor/pa/products/AndroidProducts.mk
ifeq (pa_cancro,$(TARGET_PRODUCT))
PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_cancro.mk
endif
Path : vendor/pa/products/pa_cancro.mk
# Copyright (C) 2014 ParanoidAndroid Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Check for target product
ifeq (pa_cancro,$(TARGET_PRODUCT))
# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_xxhdpi
# Build paprefs from sources
PREFS_FROM_SOURCE ?= false
# Inherit telephony common stuff
$(call inherit-product, vendor/pa/configs/telephony.mk)
# Include AOSPA common configuration
include vendor/pa/main.mk
# Inherit device configuration
$(call inherit-product, device/xiaomi/cancro/full_cancro.mk)
# Override AOSP build properties
PRODUCT_DEVICE := cancro
PRODUCT_NAME := pa_cancro
PRODUCT_BRAND := xiaomi
PRODUCT_MODEL := MI 3W
PRODUCT_MANUFACTURER := Xiaomi
# Set build fingerprint / ID / Product Name ect.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=cancro TARGET_DEVICE=cancro
endif

Nice one..
Sent from my MI 3W

Waiting for it. Finally!! Thanks man.

Any problem with installing rom? Got pm someone mention it.
Sent from my Mi3 using Tapatalk

audahadi said:
Any problem with installing rom? Got pm someone mention it.
Sent from my Mi3 using Tapatalk
Click to expand...
Click to collapse
Chkout the miui thread for ur rom
http://en.miui.com/thread-42417-1-1.html

Shahan_mik3 said:
Chkout the miui thread for ur rom
http://en.miui.com/thread-42417-1-1.html
Click to expand...
Click to collapse
Not my rom..AOSPA..[emoji13]..Just mirror download link if you want too... Just for reminder..mostly I'm on xda..so won't check issue there much.
Sent from my Mi3 using Tapatalk

audahadi said:
Not my rom..AOSPA..[emoji13]..Just mirror download link if you want too... Just for reminder..mostly I'm on xda..so won't check issue there much.
Sent from my Mi3 using Tapatalk
Click to expand...
Click to collapse
Yes the thread is yet to be modified did it in a hurry.. Will give credits after u updated the thread.
Also I will remove the download link as more ppl will visit the thread to download ur ROM
We will do our best to resolve it or they will be redirected here

can't install
audahadi said:
Any problem with installing rom? Got pm someone mention it.
Sent from my Mi3 using Tapatalk
Click to expand...
Click to collapse
hey OP,
thanks for the efforts for getting PA to our Mi3
Unfortunately, when i download the zip file and move it to my phone, i'm getting an error "This device has either stopped responding or has been disconnected"
It happens only on your zip, when transferring to the sd card. Any other file can be transferred without issues.
I also noticed that in the file's properties, it is set to block (as it apparently came from another source), and there's an unblock button available for you to click on.
Did that and the same thing happened.
However, changing the file ext from zip to .txt allows me to transfer the file easily to my phone. I changed it back to .zip, rebooted to recovery and flashed the rom but failed - I didn't get the error but it somehow refers to the file as corrupted or non-supported.
Any help will be greatly appreciated! We're talking about PA here - AOSPA so I'm very excited about it!

Sorry for corrupt zip. This is new build.
https://docs.google.com/file/d/0B3JXRJM_jo8LQ1BzLXdCb3JBM1k/edit?usp=docslist_api
*fix auto brightness
*add notification led
Sent from my MI 3W using Tapatalk

audahadi said:
Sorry for corrupt zip. This is new build.
https://docs.google.com/file/d/0B3JXRJM_jo8LQ1BzLXdCb3JBM1k/edit?usp=docslist_api
*fix auto brightness
*add notification led
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
Also your ROM is in wrong section
It should be in android development but is in general.

Shahan_mik3 said:
Also your ROM is in wrong section
It should be in android development but is in general.
Click to expand...
Click to collapse
Mod edit until I revamp my OP (this weekend-busy days). Will do proper with all guide and credits.
Sent from my MI 3W using Tapatalk

audahadi said:
Mod edit until I revamp my OP (this weekend-busy days). Will do proper with all guide and credits.
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
You can just copy paste from miui thread and edit credit part.
For now then properly edit it later

audahadi said:
Sorry for corrupt zip. This is new build.
https://docs.google.com/file/d/0B3JXRJM_jo8LQ1BzLXdCb3JBM1k/edit?usp=docslist_api
*fix auto brightness
*add notification led
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
thanks for this, i had problems too with previous zip. will try asap.
what do you mean with auto brightness fixed? i mean, it doesn't even work in cm...?!
thanks!!

audahadi said:
Sorry for corrupt zip. This is new build.
https://docs.google.com/file/d/0B3JXRJM_jo8LQ1BzLXdCb3JBM1k/edit?usp=docslist_api
*fix auto brightness
*add notification led
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
Also Dynamic statusbar is not available. can you please confirm if its available in the build???

moly82 said:
thanks for this, i had problems too with previous zip. will try asap.
what do you mean with auto brightness fixed? i mean, it doesn't even work in cm...?!
thanks!!
Click to expand...
Click to collapse
Don't try cm yet...but my previous build can't enable auto brightness..
Missing config.
Shahan_mik3 said:
Also Dynamic statusbar is not available. can you please confirm if its available in the build???
Click to expand...
Click to collapse
Dynamic status bar and new recent not available in unofficial build. Need to wait for PA release source and got merge in aospa-legacy source.
Sent from my MI 3W using Tapatalk

audahadi said:
Don't try cm yet...but my previous build can't enable auto brightness..
Missing config.
Dynamic status bar and new recent not available in unofficial build. Need to wait for PA release source and got merge in aospa-legacy source.
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
It is available for legacy devices dude....I tried it on my galaxy s2 2/9 build

Shahan_mik3 said:
It is available for legacy devices dude....I tried it on my galaxy s2 2/9 build
Click to expand...
Click to collapse
yup it is work with legacy device, but mi3 is not yet a PA legacy device....

i04055 said:
yup it is work with legacy device, but mi3 is not yet a PA legacy device....
Click to expand...
Click to collapse
I know...he told the sources are not merged for legacy device that's why I told.

Shahan_mik3 said:
I know...he told the sources are not merged for legacy device that's why I told.
Click to expand...
Click to collapse
Unofficial mean device that not officially supported by PA members. PA build internally for rom released. Not directly from their source. When features is stable, they will release source.
Sent from my MI 3W using Tapatalk

[Guide] Source-build Android for Zuk Z2

Requirements
- Linux Mint 18 XFCE
- 20GB SWAP
- 130 GB HDD space
Configuring the OS
When the OS is installed, open terminal and issue:
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update && mkdir ~/bin && PATH=~/bin:~/sdk/tools:~/sdk/platform-tools:~/sdk/build-tools:$PATH && sudo apt-get install curl bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush repo schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline6-dev lib32z1-dev && curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Download the Android SDK tools: https://dl.google.com/android/android-sdk_r24.4.1-linux.tgz
Extract them to your home folder and rename the folder containing them to 'sdk', so it matches the path that was set.
After issue the following in terminal:
Code:
android
Update it and get all of the required things for the version of Android you're building.
Downloading the source
We'll use my own personal choice... Issue the following in terminal:
Code:
PATH=~/bin:~/sdk/tools:~/sdk/platform-tools:~/sdk/build-tools:$PATH && repo init -u git://github.com/SlimRoms/platform_manifest.git -b mm6.0
It will ask you to configure your git Username and PW, you can either do it or ignore it; it's your prerogative.
After issue into terminal:
Code:
repo sync
Prepare to wait for quite a few hours.
Understanding the Layout
The layout of AOSP or any android firmware looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The important folders for basic building are the following:
- Device
The configurations for your device files should follow this layout.
Device/OEMname/Devicename
In the case of Z2 Pro it is 'Device/Zuk/Z2pro'
- Kernel
Kernel/OEMname/kernelname
The name of the kernel is specified in the main makefile of the Device configurations.
The kernel can be called anything in reality...
Vendor is where the files we cannot generate from source go; they are proprietary files that have already been created and must be pulled from an already working ROM that shares the same HW as the phone you are developing for.
Device Makefile operations explained
In my SlimROM Z2 configurations, the main makefile of relevance here is slim.mk
Code:
# Props
PRODUCT_PACKAGES += \
libloc_api_v02 \
libthermalclient \
datastatusnotification \
QtiTelephonyService \
shutdownlistener \
TimeService \
CNEService \
com.qualcomm.location \
dpmserviceapp \
qcrilmsgtunnel \
QtiTetherService \
colorservice \
ims \
imssettings \
qcnvitems \
libtime_genoff \
libbtnv \
qcrilhook
Normally VENDOR files are defined in the vendor folder; but I have defined them here instead which is fine.
Code:
$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)
$(call inherit-product, vendor/zuk/z2pro/z2pro-vendor.mk)
The inherit-product command adds an outside makefile to the main makefile.
By noticing 'inherit vendor z2pro-vendor.mk' we are observe that SlimROM will use the makefiles in Vendor that has been specified.
Code:
$(call inherit-product, vendor/slim/config/common_full_phone.mk)
As we can see, this 'Common_full_phone' config is generic, it should be used for every model.
Certain models will inherit certain makefiles; as this is a x64 phone we are using:
Code:
$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
This should be used on any x64 phone; things are quite generic across makefiles very few things are device-specific in reality.
Inside the device folder there is a .dependencies file; for example the contents of one file are as follows:
Code:
[
{
"repository": "android_device_qcom_common",
"target_path": "device/qcom/common"
},
{
"repository": "android_vendor_nxp-nfc_opensource_frameworks",
"target_path": "vendor/nxp-nfc/opensource/frameworks"
},
{
"repository": "android_vendor_nxp-nfc_opensource_libnfc-nci",
"target_path": "vendor/nxp-nfc/opensource/libnfc-nci"
},
{
"repository": "android_vendor_nxp-nfc_opensource_Nfc",
"target_path": "vendor/nxp-nfc/opensource/Nfc"
}
]
"target_path" will show you additional folders you may need from Github that are required for the device to function properly.
If you do not have your device dependencies it will not build, they must also be obtained.
Kernel explanation
Some kernels are useful across multiple devices; but how are they defined for an individual device?
They are defined with a file called 'defconfig', it is located here:
On a x86 device, we would use the ARM folder and not ARM64 but I digress.
In the 'Device' folder, there is a file called 'Boardconfig.mk', this is relevant to building the kernel.
Code:
TARGET_KERNEL_SOURCE := kernel/zuk/msm8996
TARGET_KERNEL_CONFIG := z2p_defconfig
TARGET_SOURCE = The kernel folder
TARGET_CONFIG = The defconfig for your device.
When trying to build with another kernel; the kernel author may be calling the defconfig something else so this field will need to be changed; or the name of the defconfig file will need to be changed.
I will not explain much about the 'Vendor' folder in this time, it requires higher-end methodology to determine what proprietary files a phone does and does not need.
Anyway, for the Z2 I have already made vendor configs so people here do not need to worry much about it although they are a little incomplete...
Understanding Github
Github is fantastic, rather than to mess around with terminal for pulling things from it I'd rather demystify it and for this reason am encouraging people to DL, unzip and stage things manually rather than to depend on .xmls
Notice "android_device_xiaomi_libra"
This is to say the contents of this git should end up in device/xiaomi/libra; you will need to create these folders and place the contents inside of them manually.
It is the same with kernel, and vendor files.
Building the OS
Now that device, kernel and vendor configurations are in place it's time to attempt a build, eh?
issue the following into terminal:
Code:
PATH=~/bin:~/sdk/tools:~/sdk/platform-tools:~/sdk/build-tools:$PATH && . build/envsetup.sh
The build engine will now start.
Issue the following:
Code:
breakfast z2
The breakfast command will prepare all the ingredients; if no error is thrown here next issue:
Code:
brunch z2
This will begin the building process for the Zuk Z2.
This will take a really long time to complete.

InterfaceNode said:
As the title says.
Click to expand...
Click to collapse
Slim would be nice.
Do you own device? Wouldn't it be hard to build a rom without having hardware to test/debug?
CM build for Z2 Pro has number of bugs and is not maintained.
Thanks.

crubbish said:
Slim would be nice.
Do you own device? Wouldn't it be hard to build a rom without having hardware to test/debug?
CM build for Z2 Pro has number of bugs and is not maintained.
Thanks.
Click to expand...
Click to collapse
I'll build an initial test of something closer to AOSP like Slim, or Omni.
I'll then ask for ADB logcat from users to determine which HW is not good.
The HW that is not good, it may be the result of vendor files being used; I will then look at a phone that uses identical HW and use their vendor files in applicable places to update it if required.
It's really easy to build for this device if CM will build for it; that's a great starting place and a lot of the heavy lifting has already been done by others to bring it up

InterfaceNode said:
I'll build an initial test of something closer to AOSP like Slim, or Omni.
Click to expand...
Click to collapse
Thanks for quick response. I'm prepared to be a tester when you have something ready. Good luck!

crubbish said:
Thanks for quick response. I'm prepared to be a tester when you have something ready. Good luck!
Click to expand...
Click to collapse
I'll have a build for you to test in maybe an hour or so..
Since we're all scratching each-others back; does anyone have a pull of the 6.0 Z2 stock ROM?

crubbish said:
Thanks for quick response. I'm prepared to be a tester when you have something ready. Good luck!
Click to expand...
Click to collapse
Good god I really hope so, I always want immediate feedback
If you're interested in testing for me on a more daily basis; I'll bring amazing firmware to this device that people have never heard of..
Edit: Maybe it will take a little under 2 hours? this device does not really seem to have configurations for an AOSP ROM.
I'm very sure that my configurations will be good; but I'm not going to lie I did use some prebuilt things so I may run into conflicts if the device configurations want something that doesn't exist in AOSP.
At some point I'll write about this, source-building for a device is not a mystical process that requires a person to own the device; the only benefit to owning the device would be to extract ADB after building has finished.
Owning a device will not assist you in the build process unless it is to pull proprietary files from the stock ROM, users generally post Stock ROMs anyway so really.
I see people getting ready to collect donations and building this up like it's some kind of epic challenge or whatever.
This device is already being staged for Mokee, it's not going to be hard to build for it since someone else has already done all of the hard stuff.
Making this thread is more or less like seeing people on the sidewalk; I'm driving by and it's raining so I want to go through the puddle on the side of the street where they are walking.
Naturally I'll also accept donations, either PayPal or BTC is fine for me!!!!!!!!!!!
But I'm going to begin working irrespective of that because fundamentally It's not about the money for me
The funny thing is on a morality level it feels almost spiritually wrong to even accept donations since another person brought up all of the core configurations every other person; including people in the Nameless ROM thread will use in the future lol

You are doing this for Z2 or Z2 Pro?

shaunydub said:
You are doing this for Z2 or Z2 Pro?
Click to expand...
Click to collapse
Fk it, I'll do both right?
The Z2 is building presently but I guess I could also do the Z2 pro
But I guess it would take another hour or so, if I also add the Z2 pro to my s-tuff2do list

InterfaceNode said:
Fk it, I'll do both right?
The Z2 is building presently but I guess I could also do the Z2 pro
Click to expand...
Click to collapse
I'm excited for that to happen. Since mokee rom has a few minor bugs which didn't get fixed by now, I would be surprised if someone walks by and build like that. Nevertheless, time will tell and it would be nice if you could build dirty unicorns ????

MacLaughlin said:
I'm excited for that to happen. Since mokee rom has a few minor bugs which didn't get fixed by now, I would be surprised if someone walks by and build like that. Nevertheless, time will tell and it would be nice if you could build dirty unicorns ????
Click to expand...
Click to collapse
I would hope interested folks can give me the name of their device and the ADB.
Z2 is confirmed by me (looking at it) as stable enough to begin bringup of the following ROMs:
http://www.vibeui.com/
Zuk OS 6.0
I would like to begin collecting feedback on builds of these two ROMs at the same time as feedback on all AOSP builds.
To build DU is easy, I will write about how to do it for end-users and post configs to be used with it; but for now I want to first push stable AOSP and then consider what firmware to bring that is actually interesting.
Who cares in reality about DU or whatever, it all is essentially AOSP anyway compared to vendor ROMs

hardware/qcom/media-caf/msm8996/mm-video-v4l2/vidc/vdec/src/omx_vdec_v4l2.cpp: In function 'void* async_message_thread(void*)':
hardware/qcom/media-caf/msm8996/mm-video-v4l2/vidc/vdec/src/omx_vdec_v4l2.cpp:259:29: error: 'V4L2_EVENT_BITDEPTH_FLAG' was not declared in this scope
if(ptr[2] & V4L2_EVENT_BITDEPTH_FLAG) {
^
hardware/qcom/media-caf/msm8996/mm-video-v4l2/vidc/vdec/src/omx_vdec_v4l2.cpp:263:29: error: 'V4L2_EVENT_PICSTRUCT_FLAG' was not declared in this scope
if(ptr[2] & V4L2_EVENT_PICSTRUCT_FLAG) {
^
target thumb C++: libOmxVenc_32 <= hardware/qcom/media-caf/msm8996/mm-video-v4l2/vidc/venc/src/omx_video_base.cpp
hardware/qcom/media-caf/msm8996/mm-video-v4l2/vidc/vdec/src/omx_vdec_v4l2.cpp: In member function 'virtual OMX_ERRORTYPE omx_vdec::component_init(OMX_STRING)':
hardware/qcom/media-caf/msm8996/mm-video-v4l2/vidc/vdec/src/omx_vdec_v4l2.cpp:2343:25: error: 'MSM_VIDC_PIC_STRUCT_PROGRESSIVE' was not declared in this scope
m_progressive = MSM_VIDC_PIC_STRUCT_PROGRESSIVE;
Click to expand...
Click to collapse
Build for Z2 errored with that code.
To resolve it the important thing to note is: V4L2_EVENT_BITDEPTH_FLAG
Doing a search of it in Git brings me to:
https://github.com/MoKee/android_ke...mmit/b9534998dcc1c20afd01ed95bb4ef5b3a34fbdbd
Although this device is not Nubia, Nubia is very close and can clearly be used as a guide-line to determine the commits this kernel needs.
The red HW errors during building indicate the kernel does not align with the source; to resolve this I would need to either remove the functions relating to this from the source-code of AOSP or I would need to add it to the kernel.
In the spirit of not being regressive, I decided to add it to the kernel and am building again.
I guess I'll write about how I resolved certain things here as I go along

Mokee kernel for this ROM is broken somehow, I speculate this is intentional so other people cannot build it but who knows right.
Meanwhile I've begun bringup on the kernel found here: https://github.com/RoyMcBaster/kernel_zuk_8996
No idea who this guy is, but his kernel doesn't seem to be sabotaged just incomplete so I'll use it as a base
Edit: Under my hardware, a build with no pre-built binaries takes around 40 minutes.
Each time I need to resolve the kernel in this way, I must rebuild entirely from the ground up; I am unsure of how many other alignment errors exist in this kernel but I imagine a few.
In a perfect world none but probably thats not happening, but it is ok I enjoy being challenged

Gonna follow this thread with much interest. You might want to have a look at this thread: http://zukfans.eu/community/threads/development-of-cyanogenmod-need-help.395/
Perhaps it helps you, at least for the ZUK Z2 Pro.

Here is one more kernel: http://zukfans.eu/community/threads/kernel-port-cm13-m-kernel-v1-1-port-22-09-2016.478/
Also you may take smth from existing CM builds: http://bbs.zuk.cn/z2/t135170/ (download link)

.: SID :. said:
Here is one more kernel: http://zukfans.eu/community/threads/kernel-port-cm13-m-kernel-v1-1-port-22-09-2016.478/
Also you may take smth from existing CM builds: http://bbs.zuk.cn/z2/t135170/ (download link)
Click to expand...
Click to collapse
Thank you, I've resolved the kernel for Z2 plus and will begin pushing builds of it as part of open-alpha.
Once I can determine both are stable we'll begin engaging in satanism; I'll try to do something interesting like TouchWiz or Sense.
I'm going to buy this device, but true to style I want to forward the development of it, bring some incredible OS to it.
Once both of my builds are stable I'll add more to this thread because I will be able to post my configs and explain how2use; things will move quickly here I hope

InterfaceNode said:
Thank you, I've resolved the kernel for Z2 plus and will begin pushing builds of it as part of open-alpha.
Once I can determine both are stable we'll begin engaging in satanism; I'll try to do something interesting like TouchWiz or Sense.
I'm going to buy this device, but true to style I want to forward the development of it, bring some incredible OS to it.
Once both of my builds are stable I'll add more to this thread because I will be able to post my configs and explain how2use; things will move quickly here I hope
Click to expand...
Click to collapse
That's great!
Please stay with AOSP and don't get to TouchWiz, Sense or whatever OEM framework!

vittogn said:
That's great!
Please stay with AOSP and don't get to TouchWiz, Sense or whatever OEM framework!
Click to expand...
Click to collapse
Well I always feel why be limiting, right?
Additionally I noticed the CM configs I was basing off of from Z2 has intentionally broken code-lines.
There's nothing worse than an overprotective developer

InterfaceNode said:
Well I always feel why be limiting, right?
Additionally I noticed the CM configs I was basing off of from Z2 has intentionally broken code-lines.
There's nothing worse than an overprotective developer
Click to expand...
Click to collapse
Thanks

InterfaceNode said:
Well I always feel why be limiting, right?
Additionally I noticed the CM configs I was basing off of from Z2 has intentionally broken code-lines.
There's nothing worse than an overprotective developer
Click to expand...
Click to collapse
I see your point?
What do you mean with intentionally broken code-lines?
Are you developing also a CM?
Thanks again.
Look forward to buy a Z2 when your rom will be ready!

Flyme would be nice to Even on a few of my Meizu's it's not stable XD