[ROM] [4.4.4_r2] Builds from TeamCanjica's CM11 sources

[ROM] [4.4.4_r2] Builds from TeamCanjica's CM11 sources - Galaxy Ace II Android Development

{
"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"
}
CyanogenMod 11.0 for the Samsung Galaxy Ace 2 ( GT-I8160 )
------------------------------------------------------------------------------------------------------------------------------------------
It happens to me that I got some build capacity and like to share my CyanogenMod/TeamCanjica builds. I am hardly developing, just cherry-picking and some light debugging. Some of these builds are untested, so feel free to report your experiences here.
These builds are compiled from TeamCanjica's sources, found on GitHub. For installation instructions, credits, changelogs, see Rox original thread. There you also find information about donations. For a changelog in CM sources, you may find CM review helpful.
Let me repeat: all CREDITS to the guys mentioned here. They did all the work.
These builds come in two versions:
Full version, "Rox-like" with all CM apps except CMupdater
Stripped (slim) version without: build-in sounds/ringtones, Apollo, Videoeditor, most of the screensavers, CMhome, CMupdater, CMwallpaper, Exchange provider.
Each of these two versions has a build for the codinap device (with NFC) and the codina device (without NFC). In case you don't know, you probably have a codina device. Personally, I use the stripped-codinap-version, so this will be updated quite often, the others not so frequently.
If your device breaks: you did this on your own responsibility. However, bleeding edge may be worth it.
Link to my dev-host downloads.
FAQ:
Question: How often do you release? How long will this be maintained?
Answer: I don't now. At the moment (October 2014) quite often. Weekly. Daily.
Question: Is XYZ working? (answer valid for the LATEST STRIPED version)
Answer: Live Streaming: Camera and YouTube works.
Answer: Call logs: Contact app is up-to-date and working.
Answer: Swap Storage: don't know. CPU gpu oc: don't know.
Question: How can I get ringtones and notifications back?
Answer: Install the full version. OR: or the internal sdcard, create files like /media/audio/notifications/MyFavourite.ogg and /media/audio/ringtones/MyFavourite.ogg and they will be there forever, even if you install the stripped version.
How to build:
Code:
repo init -u https://github.com/TeamCanjica/android.git -b cm-11.0
repo sync -j32
./cherry-pick.sh
./vendor/cm/get-prebuilts
. build/envsetup.sh
brunch codina
The cherry-pick.sh is taken from here, but maybe some more picks are needed. Note that the code above is more a concept than a working script. Getting your own build environment is not very hard, but not topic of this thread. If it does not compile, feel free to solve it and post the SOLUTION here.
Issues:
Camera FC after video rec
Some videos only play in fullscreen, e.g. in browser (see here and following).

download / changelog
What's all these files? Which device do I have? Please read post #1 first.
IMPORTANT: I had to buy a new device. These files won't be updated anymore or only very very occasionally. Thank you for understanding and supporting me in the past.
These ZIP-files includes a working kernel, based on the stock kernel. There is a good alternative , described here (there are probably more good alternatives I did not test so far).
Stripped: cm-11-20141108-poppmensa-codinap.zip - 190.67 MB, cm-11-20141108-poppmensa-codina.zip - 190.11 MB
Full: cm-11-20141108-poppmensa-codinap.zip - 218.06 MB, cm-11-20141108-poppmensa-codina.zip - 217.49 MB
CM sources updates
ISSUES: camera FC after video-rec (BUT: camera works again, in contrast to 20141101 build)
Stripped: cm-11-20141101-UNOFFICIAL-codinap.zip - 190.54 MB, cm-11-20141101-UNOFFICIAL-codina.zip - 189.98 MB
CM sources updates
remove NovaThor from stripped and full version (until it works with ace2nutzer's kernel)
remove CMUpdate from stripped and full version
ISSUES: there seems to be a (new) problem with video/camera. Better use older build.
Stripped: cm-11-20141029-poppmensa-codinap.zip - 190.69 MB
CM sources updates
Stripped: cm-11-20141023-UNOFFICIAL-codinap.zip - 190.65 MB, cm-11-20141023-UNOFFICIAL-codina.zip - 190.09 MB
Full: cm-11-20141023-UNOFFICIAL-codinap.zip - 218.18 MB, cm-11-20141023-UNOFFICIAL-codina.zip - 217.61 MB
CM sources updates
Kernel based on this code
Older builds:
Stripped: cm-11-20141021-UNOFFICIAL-codinap.zip - 190.64 MB, cm-11-20141021-UNOFFICIAL-codina.zip - 190.08 MB
CM sources updates (lots of camera updates, MAYBE fixes camera2.apk-issues)
Kernel based on this code
Stripped: cm-11-20141019-UNOFFICIAL-codinap.zip - 190.55 MB
CM sources updates
Full: cm-11-20141017-UNOFFICIAL-codinap.zip - 218.07 MB, cm-11-20141017-UNOFFICIAL-codina.zip - 217.51 MB
Stripped: cm-11-20141016-UNOFFICIAL-codinap.zip - 190.55 MB, cm-11-20141017-UNOFFICIAL-codina.zip - 189.99 MB
CM sources updates
Stripped: cm-11-20141014-UNOFFICIAL-codinap.zip - 190.33 MB, cm-11-20141014-UNOFFICIAL-codina.zip - 189.76 MB
CM sources updates
Revert to stable Kernel from 20141011
Includes STE-OMX: video streaming fix from Meticulus
Stripped: cm-11-20141013-UNOFFICIAL-codinap.zip - 190.32 MB, cm-11-20141013-UNOFFICIAL-codina.zip - 189.76 MB
CAUSES SEMI-BRICK (Odin helps).
CM sources updates, Kernel updates (see sources)
NovaThor Settings included again (also in striped version)
Stripped: cm-11-20141012-UNOFFICIAL-codinap.zip - 190.17 MB, cm-11-20141012-UNOFFICIAL-codina.zip - 189.61 MB
CM sources updates, Kernel updates (see sources)
Full: cm-11-20141010-UNOFFICIAL-codinap.zip - 217.80 MB, cm-11-20141010-UNOFFICIAL-codina.zip - 217.24 MB
CM sources updates, (reached M11)
fixes contacts/call log, camera (compared to TC 20141003-build)

Hello,
Where do i find ./cherry-pick.sh? Is it on github too? I synced it but there is no script.
Thanks a lot!
Regards,
sgace2

sgace2 said:
Where do i find ./cherry-pick.sh? Is it on github too? I synced it but there is no script.
Click to expand...
Click to collapse
No, it's not. https://github.com/TeamCanjica/BuildBot/blob/master/cherry-pick.sh
You probably need to create your own script from that. It put a snipped for your convenience. If it does not compile, feel free to solve it and post the SOLUTION here.
Code:
echo -e $CL_BLU"Cherrypicking Core Patch - Reboot/shutdown fix"$CL_RST
cd system/core
git fetch https://github.com/TeamCanjica/android_system_core cm-11.0
git cherry-pick 347658ad1b53234b52d32d42fba2a72878b883c5
git cherry-pick 8aa242d1827875506ce3339d2df3e0fed6f89e42
cd ../..
echo -e $CL_BLU"Cherrypicking OK Google patch"$CL_RST
cd frameworks/base
git fetch https://github.com/TeamCanjica/android_frameworks_base cm-11.0
git cherry-pick de30387b3c32c2a9cf653590c8454bd002bf0dd1
cd ..
echo -e $CL_BLU"Cherrypicking Legacy sensors"$CL_RST
cd native
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_native refs/changes/11/59311/1
git cherry-pick FETCH_HEAD
cd ../..
echo -e $CL_BLU"Cherrypicking ART fix"$CL_RST
cd art
git fetch https://github.com/cernekee/android_art monitor-stack-v1
git cherry-pick fc2ac71d0d9e147c607bff9371fe2ef25d8470af
cd ..
echo -e $CL_BLU"Cherrypicking OMX Patch - android_frameworks_av"$CL_RST
cd frameworks/av
git fetch https://github.com/TeamCanjica/android_frameworks_av cm-11.0
git cherry-pick 87618c1ea54009c2e5e5dfb60060f9cc2e9bcc52
git cherry-pick cfcb60d66b01783c274dc625bf32a44899d1e603
cd ..
echo -e $CL_BLU"Cherrypicking OMX Patch - android_frameworks_native"$CL_RST
cd native
git fetch https://github.com/TeamCanjica/android_frameworks_native cm-11.0
git cherry-pick f5a8698ce9a3568cea95c03302deb068eff765bd
cd ../..
echo -e $CL_BLU"Cherrypicking vold patch to allow switching storages"$CL_RST
cd system/vold
git fetch http://review.cyanogenmod.org/CyanogenMod/android_system_vold refs/changes/15/56515/2
git cherry-pick FETCH_HEAD
cd ../..
echo -e $CL_BLU"Cherrypicking Low-InCall fix"$CL_RST
cd packages/services/Telephony
git fetch https://github.com/TeamCanjica/android_packages_services_Telephony cm-11.0
git cherry-pick fdf281fdabe5e7517eb96f2faf159bbcc74ae4a6
cd ../../..

Okay..
I'll leave my trace here, in case of fast accessing the thread.
Hope you'll be a famous codina devs just like rox. @poppmensa
I mean not only just cherry-picking, but a real development stuff. Like building cm12 in the future.

How about changelog? Is everything working now? There where various problems with Rox 03/10 build. Call log? Camera? Other things? Would be great if You could write sth more about it.

@poppmensa - can we have the build for codina (non-p) at least once a month? It will be great.
I'm asking 'cause you wrote before, that you'll mainly work on codinap version.

poppmensa said:
Striped: cm-11-20141012-UNOFFICIAL-codinap.zip - 190.17 MB
CM sources updates
Kernel updates (see sources)
Click to expand...
Click to collapse
For non-p please... :good:

I use the codina version for about two days, i feel that is all good.
contact log is ok
youtube is working
i have not check the live stream at the moment
The move to (internal) sd from application manager just does not work but i dont care because i have reparted internal memory

@poppmensa finally, you did it.
Keep this thread live & updated. Strip version is so smooth...no bloatware from CM11. :good:

I installed Striped CM11 just because I was curious. Then it got my attention and now I think it will stay for a while on my Ace 2.
Striped Rom Rocks!

I'm not use the phone very often, bcoz buy new one, but decide to try this rom(striped version too) and feel it very good. Just want to ask what's the way to swap storages here?

As I don't see anyone mentioning it, I wonder if I'm one of the few experiencing this bug:
https://jira.cyanogenmod.org/browse/CYAN-4134
I noticed the widget behaves correctly if I change the cLock resolution to a higher value using App Setting module in Xposed. Perhaps something is wrong with the MDPI layout/resources?...
Is there any chance that this bug will get fixed in this build? It appears the CM developer is focusing on the Chronus app and not on the CM cLock app...
And thanks for this build! As someone already mentioned, a monthly release with CM source update would be just fine!

Can someone tell me where can I find last Novathor Settings version for flash via recovery? Thanks.

MarquesYOLO said:
Can someone tell me where can I find last Novathor Settings version for flash via recovery? Thanks.
Click to expand...
Click to collapse
I think that you can take it from an older version of rox rom, put it in the zip file of this rom and flash at app folder.
or
you can try this http://forum.xda-developers.com/showthread.php?t=2729459

MarquesYOLO said:
Can someone tell me where can I find last Novathor Settings version for flash via recovery? Thanks.
Click to expand...
Click to collapse
it will be included again in the next builds.

Live streaming is working or we will wait for next build?

manthes said:
Live streaming is working or we will wait for next build?
Click to expand...
Click to collapse
What exactly do you mean by "live streaming"? how can I test it?

I care if it is working on apps like filmon because i read the problem with streaming has been fixed

poppmensa said:
What exactly do you mean by "live streaming"? how can I test it?
Click to expand...
Click to collapse
I think its same with video streaming like on youtube. try to test with youtube.

Related

{All 2011}[GUIDE][DEV] How to build CyanogenMod 12.1

This thread is intended for devs & advanced users only.
Here you can learn how to build CyanogenMod 12.1 for any of the 2011 xperia devices.
I will use 'smultron' as an example device, you should replace the codename with the device you want to build.
For the first time you try to build CM12.1
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Initialize the CyanogenMod source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
ln -s vendor/extra/updates.sh updates.sh
./updates.sh
Setup the build environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-12.1-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-12.1-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Some suggestions for faster builds:
* Enable ccache
* Use the fastest hdd on your pc to store the source, build output & ccache
* You can also buy an ssd, if it's not large enough to hold everything, just store the build output & ccache
* mount /tmp on tmpfs (RAM).
The above have greatly improved my dirty build times with removed /out/target from 1h30m to 30m.
Mounting /tmp on tmpfs made the biggest improvement for me.
Credits: Thanks to hnl_dk for the initial CM9 & CM10 guides.

Reserved

getting insuficiant storage aviable in pa gappps (pico/micro) packages

Druboo666 said:
getting insuficiant storage aviable in pa gappps (pico/micro) packages
Click to expand...
Click to collapse
yes...same here
from build of 21st...i am getting this error
and even other zips are not getting flashed

TWRP
delete

Other than a fast HDD, does you computer need to be fast to build it? (Running a 2007 Core 2 Duo...)
Theonew said:
More cores are better. Here are the requirements to build it from source:
- 6GB of download.
- 25GB disk space to do a single build.
- 80GB disk space to build all AOSP configs at the same time.
- 16GB RAM recommended, more preferred, anything less will measurably benefit from using an SSD.
- 5+ hours of CPU time for a single build, 25+ minutes of wall time, as measured on a workstation (dual-E5620 i.e. 2x quad-core 2.4GHz HT, with 24GB of RAM, no SSD).
Click to expand...
Click to collapse
And I would say that a fast internet connection is also recommended, since the full source for initial sync is more than 10GBs (on ICS it already was, probably like 20GBs for lollipop).

brunch build error 12.1
Hi,
I am trying to build the image from the sources as per the build instructions to make my own test build.
After repo downloads, while building i am getting error "init/Kconfig:953: can't open file "usr/Kconfig"" in the brunch smultron command.
I am following these commands:
1) repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
2) curl https://raw.githubusercontent.com/Le...-12.1/semc.xml > /tmp/android/system/.repo/local_manifests/semc.xml
3) repo sync
4) ln -s vendor/extra/updates.sh updates.sh
5) ./updates.sh
6) . build/envsetup.sh
7) breakfast smultron
8) brunch smultron
{
"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"
}
Can you tell me whats wrong.
Thanks.

joshipallav said:
Hi,
I am trying to build the image from the sources as per the build instructions to make my own test build.
After repo downloads, while building i am getting error "init/Kconfig:953: can't open file "usr/Kconfig"" in the brunch smultron command.
I am following these commands:
1) repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
2) curl https://raw.githubusercontent.com/Le...-12.1/semc.xml > /tmp/android/system/.repo/local_manifests/semc.xml
3) repo sync
4) ln -s vendor/extra/updates.sh updates.sh
5) ./updates.sh
6) . build/envsetup.sh
7) breakfast smultron
8) brunch smultron
Can you tell me whats wrong.
Thanks.
Click to expand...
Click to collapse
Delete the folder ~/android/system/kernel
repo sync again and make sure you get no errors
run make clean
try to build again

@Langes
hi.. just wanted to know.. any guide to Build for AOSP 5.1.1 Lollipop for Xperia Devices 2011 like cm12.1 here
and silly question time.. lol
is it possible that AOSP Android M source can also be built for Xperia Play (2011 Devices) .. I mean changes made by Mike (the AOSP Mike) + Source of Android M .. will it give us some output or :/

I built this rom today with new 3.10 kernel. It seems to be improved in some points (what isn't neccessary because of kernel), but with new kernel I can't use wifi and mobile data seems to be not working too. To build I fetched the new kernel and cherry-picked following commits:
Code:
#msm7x30-common: Update USB configuration for 3.10
cherries+=(LX_594)
#Use common msm7x30 kernel
#cherries+=(LX_422)
#msm7x30-common: Use common msm7x30 kernel
cherries+=(LX_421)
#mogami-common: wl12xx updates for 3.10
cherries+=(LX_407)
#media/msm7x30: Update for 3.10 support
cherries+=(LX_403)
#display/msm7x30: Update for 3.10 support
cherries+=(LX_402)
#audio/msm7x30: Update for 3.10 support
cherries+=(LX_401)
#kernel
#usb: Import msm charger changes from 6.2.B.0.200
cherries+=(LX_430)
#usb: msm72k_otg: Remove userspace events [REVISIT]
cherries+=(LX_428)
Is there something I missed to get working internet connection? (I didn't really test the rom for other things so far)

Getting this error when building AOSP rest all goes fine..
build also starts but getting this error.. any suggestion ?

Hey Mike, I tried to build CM14 and it fails. After some investigation it seems that imgdiff is missing. This was fixed on CM13: http://review.cyanogenmod.org/#/c/135193, which can't be applied to CM14 (no RECOVERY_PATCH_INSTALL).
I hope this helps.

zweif said:
Hey Mike, I tried to build CM14 and it fails. After some investigation it seems that imgdiff is missing. This was fixed on CM13: http://review.cyanogenmod.org/#/c/135193, which can't be applied to CM14 (no RECOVERY_PATCH_INSTALL).
I hope this helps.
Click to expand...
Click to collapse
I already have a cm14 zip for anzu, just unable to flash it because it's about 330MB and device runs out of memory when attempting to flash. Will try to find a solution/hack on the weekend

I managed to build cm14 zip for mango (installation fails as expected).
I modified build/core/Makefile, I don't fully understand how these dependencies work, but maybe there is a dependency issue.
There are dependencies: imgdiff <- RECOVERY_FROM_BOOT_PATCH <- INSTALLED_SYSTEMIMAGE <- BUILT_TARGET_FILES_PACKAGE (where make_recovery_patch is called, which needs imgdiff)
Now INSTALLED_SYSTEMIMAGE is defined before RECOVERY_FROM_BOOT_PATCH, but dependencies of INSTALLED_SYSTEMIMAGE are defined after that. Could this cause an issue?
After moving
Code:
INSTALLED_SYSTEMIMAGE := $(PRODUCT_OUT)/system.img
SYSTEMIMAGE_SOURCE_DIR := $(TARGET_OUT)
from line 1284 to line 1314 build was successfull.

mikeioannina said:
I already have a cm14 zip for anzu, just unable to flash it because it's about 330MB and device runs out of memory when attempting to flash. Will try to find a solution/hack on the weekend
Click to expand...
Click to collapse
I managed to flash cm14 after disabling dex-preoptimization. Zip size decreases to ~260MB. I didn't do extensive testing - messaging seems to work, dialing a number causes restart (system, not kernel), the only sounds I noticed were dialing sounds, i miss a browser and other apps - but it seems nice for a first impression.
Concerning my problem with imgdiff: After reading some make documentation I have no clue why it isn't built. Maybe these dependencies aren't tracked because RECOVERY_FROM_BOOT_PATCH is set to an empty string when BOARD_CANT_BUILD_RECOVERY_FROM_BOOT_PATCH is defined?
I can manually call 'make imgdiff' as workaround.
I tried some things that could have affected imgdiff before my last post, and I'm not sure if I cleared output directory. Did you try a clean build or could imgdiff come from a previous build on your machine?

bro, How much space does it need to sync the repo??
& if I want to port a ROM based on CM (Like Resurrection Remix or Liquid Smooth), would I have to use the command "repo sync"?

I'm trying to build CM14.0, but jack server is giving me a bad time with out of memory error. I have tried changing jack.server.max-service to 1, heap size to 2g, 3g and 4g, even to build without ninja, but always getting out of memory. In CM13.0 I could build without jack, but now the built is failing without it. I'm using Ubuntu 16.04 on an i3 with 4g RAM and 8g swap, I've seen cases with machines with better specs failing (e.g. i5, 8g RAM). Is it a bug with jack, or my specs is the limiting factor?
Edit: I guess this is the EOL for me :crying:.

azakosath said:
I'm trying to build CM14.0, but jack server is giving me a bad time with out of memory error. I have tried changing jack.server.max-service to 1, heap size to 2g, 3g and 4g, even to build without ninja, but always getting out of memory. In CM13.0 I could build without jack, but now the built is failing without it. I'm using Ubuntu 16.04 on an i3 with 4g RAM and 8g swap, I've seen cases with machines with better specs failing (e.g. i5, 8g RAM). Is it a bug with jack, or my specs is the limiting factor?
Edit: I guess this is the EOL for me :crying:.
Click to expand...
Click to collapse
Jack troubleshooting
If your computer becomes unresponsive during compilation or if you experience Jack compilations failing on “Out of memory error”
You can improve the situation by reducing the number of Jack simultaneous compilations by editing your $HOME/.jack-server/config.properties and changing jack.server.max-service= to a lower value.
Description with default values follows:
jack.server.max-service=<number> Maximum number of simultaneous Jack tasks. Default is 4.
jack.server.max-jars-size=<size-in-bytes> Maximum size for Jars, in bytes. -1 means no limit. Default is 100 MiB.
jack.server.time-out=<time-in-seconds> Time out delay before Jack gets to sleep. When Jack sleeps, its memoryusage is reduced, but it is slower to wake up. -1 means "do not sleep".Default is 2 weeks.
jack.server.service.port=<port-number> Server service TCP port number. Default is 8076. Needs to match theservice port defined in $HOME/.jack-settings on the client host (SeeClient section).
jack.server.admin.port=<port-number> Server admin TCP port number. Default is 8077. Needs to match theservice port defined in $HOME/.jack-settings on the client host (SeeClient section).
jack.server.config.version=<version> Internal, do not modify.

Mardon said:
Jack troubleshooting...
Click to expand...
Click to collapse
Thanks for answering, but I have already read these. I tried several combinations (max services and "-Xmx") without luck. Even:
Code:
export USE_NINJA=false
to build without ninja. The result was always the same, jack server was hanging and failing after 30 or more compilations.
P.S. I did use the changes that are not merged yet, but I don't think this is related.

You also can try
breakfast devicename
And after that
make -j1 bacon
To force 1 job compiling only
Gesendet von meinem GT-I8190 mit Tapatalk

[REFERENCE] [3.10.105] Stock kernel with upstream Linux patches - May 9th

Introduction
Hello all, I am bringing you this thread as a jumping off point to compiling kernels and working with upstream Linux. I will include a guide, some links, and some terms that will help you get started with modifying kernel source. This is also a good reference point for existing developers as I have consolidated all upstream patches into one repo. Let's get down into it!
What in the world is upstream Linux?
When an OEM sets up a device, they will pick a stable longterm branch from the Linux kernel to base their modifications around (drivers and such). In the case of Angler, they picked 3.10.73. Currently, the Linux kernel's 3.10 is updated to 3.10.105, as you can see on kernel.org. This means that Google is "missing" versions 3.10.74 to 3.10.105. Now, why does this matter? Well, the way that the Linux kernel runs its stable branches, the only things that get merged into there are bug fixes and security updates. That's it, there are no wonky features or unstable patches. The only way you get a patch into a stable branch is by having it be in the mainline branch first. Some developers have an aversion to adding upstream because they claim it is excessive and not necessary and they are partially right since not all the patches that come in are relevant to our architecture (arm64). However, upstream Linux is not unstable and by adding each version one at a time, you can verify this. I found only two patches between 3.10.73 and 3.10.105 that gave me issues and it is easy enough to either fix/revert them. Being up to date is good since you keep yourself protected from bugs and security issues that crop up. Google has been better about doing this lately with their monthly security updates but it never hurts to take matters into your own hands.
I suggest watching one of these talks given by Greg Kroah-Hartman, it is really interesting to see how the process goes:
https://www.youtube.com/watch?v=SPY0LyTU53w | https://www.youtube.com/watch?v=L2SED6sewRw
What did you do?
All I did was fetch the latest kernel.org patches from here and cherry pick them on top of the latest kernel source from Google.
I merge these patches by cherry-picking each version individually (3.10.73 to 3.10.74, 3.10.74 to 3.10.75, etc), that way I can verify that the kernel compiles fine and that there are no merge conflicts. Google will sometimes pick certain commits from upstream that are of a higher importance than others which can result in conflicts if you try to pick it again. Additionally, upstream might fix a bug one way and Google has done it another (which is not really good, Google should be pushing their fixes back to upstream so everything stays in sync).
What do I do with this?
I have created two repos below: one with the latest N security update branch with the latest upstream patches picked up on top of it (the angler-upstream branch) and another one with a plain AnyKernel source for you to modify (angler-stock is the most basic, angler-decrypt contains an fstab file that will disable both forced encryption and dm-verity). You are free to fork these or base other branches on them, that's the whole point of this post. I have verified that all the patches contain no major detectable issues. I would like some credit if you do use it but it's not required since the kernel is licensed under GPL Another reason I offer this is I have seen a lot of developers picking in upstream in patch sets, so you get one single commit for an upstream version. This is detrimental as you start to add your own patches as you cannot fully tell what was modified and for what reason without the individual commits. It might look cleaner but you don't get full history which hurts you in the long run.
Links
Kernel source: https://github.com/nathanchance/angler/tree/7.1.2-upstream
AnyKernel source: https://github.com/nathanchance/AnyKernel2/tree/angler-stock-decrypt
Toolchain source: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
How to compile
This will be a quick, step by step guide on how to compile this kernel from source. By using this process, you can start to make modifications to the kernel source and make a flashable zip.
Clone the kernel source, the AnyKernel source, and toolchain source
Code:
cd ~
mkdir Kernel && cd Kernel
git clone https://github.com/nathanchance/angler.git source
git clone https://github.com/nathanchance/AnyKernel2.git anykernel
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 AOSP-4.9
Explanation:
First command: make sure you are in your home directory (or whatever directory you want to hold the kernel folder we are about to make.
Second command: make a Kernel folder and move into it
Third command: clone the kernel source from my repo into a folder named source
Fourth command: clone the AnyKernel source from my repo into a folder named anykernel
Fifth command: clone the Google 4.9 toolchain into a folder named AOSP-4.9
AnyKernel is the name of the zip we are going to make which allows the kernel to be flashed over any ROM.
A toolchain is a set of compiler tools that allow us to compile the kernel on any computer architecture.
Make sure you are on the correct branches
Code:
cd source && git checkout 7.1.2-upstream
cd ../anykernel && git checkout angler-stock-decrypt
Explanation:
First command: move into the source directory and checkout the branch "n7.1.2-upstream", which has all of the necessary patches in it.
Second command: move into the AnyKernel directory and checkout the branch "angler-decrypt". If you don't want to disable forced encryption, use the "angler-stock" branch.
Tell the compiler what you are are compiling
Code:
export CROSS_COMPILE=${HOME}/Kernel/AOSP-4.9/bin/aarch64-linux-android-
export ARCH=arm64 && export SUBARCH=arm64
make clean && make mrproper
make angler_defconfig
Explanation:
First command: point the compiler to the location of your toolchain. If you have done anything different with the folder locations, you will need to modify the "${HOME}/Kernel/AOSP-4.9" part.
Second command: tell the compiler which architecture we are compiling for. In this case, our device is an arm64 device.
Third command: clean out any compiled files and remove our previous defconfig.
Fourth command: tell the compiler which options we want in the kernel using the angler_defconfig.
A defconfig is a file that will tell the compiler which features we want in the kernel. No computer ever uses all of the options in the kernel since there are different drivers for various devices.
Make the kernel!
Code:
make -j$(grep -c ^processor /proc/cpuinfo)
Explanation:
make tells the compiler to make the kernel (duh) and the -j$(grep -c ^processor /proc/cpuinfo) tells the compiler to use the maximum number of cores your computer has available
Make the AnyKernel zip
Code:
cp -v arch/arm64/boot/Image.gz-dtb ../anykernel/zImage-dtb
cd ../anykernel
zip -r9 stock-upstream.zip * -x README stock-upstream.zip
Explanation:
First command: copies the completed kernel (Image.gz-dtb) into the AnyKernel folder
Second command: moves us into the AnyKernel folder
Third command: makes the zip file (named stock-upstream.zip) in the AnyKernel folder.
If you ever want to do this again, run these commands and go straight to step 3:
Code:
cd source && git clean -fxd && git pull
cd anykernel && git clean -fxd && git pull
NOTE: This thread is aimed to be a breeding ground for kernel development, a place to jump off if you will. I am happy to answer how to questions about building kernels or flashing the one I have provided but this is not supposed to be a general Q&A thread. Please use another thread or create your own in Q&A if you need assistance.

Reserved

Nice

Awesome! Thanks
Sent from my ONEPLUS A3000 using Tapatalk

This is awesome! Can't wait to try this out. I've been looking for a good guide on building kernels for a long time.

I have cleaned up and reworded the OP a bit, I write better at 12pm than 4am it seems :silly:

This is nice
Sent from my Nexus 6P using XDA-Developers mobile app

Any performance or any other benefits? Normally I would just flash. But I've been trying to stay completely stock on N these days.

Smallsmx3 said:
Any performance or any other benefits? Normally I would just flash. But I've been trying to stay completely stock on N these days.
Click to expand...
Click to collapse
Most likely not. Just bug fixes and stability improvements.
Sent from my Nexus 6P using XDA Labs

Been using this kernel all day today and it seems pretty solid and good on battery life
{
"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"
}
Sent from my Nexus 6P using XDA-Developers mobile app

syrkles said:
Been using this kernel all day today and it seems pretty solid and good on battery life
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Guess that means I did a good job adding all the necessary patches haha.

Will this be updated as more patches are released?
Sent from my Nexus 6P using XDA-Developers mobile app

bossofindy said:
Will this be updated as more patches are released?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
That's the goal. I'll rebase on top of new Android security releases as they are available and I'll add Linux versions as they come out.

Github and the kernel in the OP are updated to 3.10.104.

Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P

Work on 7.1???

I'm going to nickname this the Streak Kernel for myself.
I quite like keeping up to date stability wise. Bleeding edge is nice but I've learned my lesson.

Pheoxy said:
I'm going to nickname this the Streak Kernel for myself.
I quite like keeping up to date stability wise. Bleeding edge is nice but I've learned my lesson.
Click to expand...
Click to collapse
@Pheoxy how are the folks at the i9305 forum going with their ROMs, I left there with a terrible build of cm13,,, i really hope that they had sorted out the RIL issue in source instead of using a really dirty hack of using chmod with cm12.1 to get Radio working... glad to see you here in the 6p forums though
Sent from my Nexus 6P using XDA-Developers mobile app

winxuser said:
@Pheoxy how are the folks at the i9305 forum going with their ROMs, I left there with a terrible build of cm13,,, i really hope that they had sorted out the RIL issue in source instead of using a really dirty hack of using chmod with cm12.1 to get Radio working... glad to see you here in the 6p forums though
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
It was time to upgrade. Still got the old S3 but I must have left around the same time as you. Bit to busy to really do anything of my own anymore so @theflash makes some awesome but not clogged full stuff stuff and seems alright.
Have to take this to PMs [emoji1].

Nathan, say I have stock kernel source and I just want to update it to 3.10.74 how to u upstream/Cherry pick just 3.10.74 updates all at once instead of having the source update to 3.10.104. WITHOUT having to download the patch file
Sent from my Nexus 6P using XDA-Developers mobile app

[OFFICIAL][a5xelte][SM-A510F]Lineage OS 16.0 for A5 2016

{
"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"
}
Introduction
LineageOS 16.0 is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What worksCalls, SMS, Mobile Data
Camera
NFC
WiFi
Bluetooth
Torch
Sensors
GPS
SELinux Enforcing
HWCWhat doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS. Installation
Install the latest TWRP (Available Here)
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Dalvik Cache, Data, System)
Download the latest LOS build and transfer it to your phone
Install LOS
If you are installing GApps do it at the same time (preferably in the same install queue)
And finally boot, the first boot can take several minutes as it optimises all the apps Downloads
Latest official releases HERE
Latest unoficial releases are uploaded HERE
OpenGapps HERE
TWRP is availableHERE
Magisk is available HEREThanks
@Stricted
@l-0-w
@sekil
@alexax66
@macs18max (BT call audio fix)
@Borduni
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and presentA special thanks to my donorsMarkus Anders
@D4ND310
@epicwilmo
@tyson
@thebinf
@Herti
@pixelou
@xavier66
XDA:DevDB Information
Lineage OS 16.0 for A5 2016, ROM for the Samsung Galaxy A Series
Contributors
danwood76, stricted
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
Based On: LineageOS
Version Information
Status: Stable
Created 2019-06-25
Last Updated 2019-08-22

Changelog
Code:
Changes in the 18/08/19 release:
[INDENT]Fixed GPS SEPolicy (thanks @stricted)
[/INDENT]
Older changes listed below:
Code:
Chaages in the 16/08/19 release:
[INDENT]Revert one HWC change to correct slight UI lag
LOS updates[/INDENT]
Code:
Chaages in the 11/08/19 release:
[INDENT]More HWC improvements (thanks @Stricted)
Added volume keys as a wakeup source (now visible in button settings)
Corrected fingerprint sensor location on the "add fingerprint" GUI
Synced WiFi config with stock (now same as A3)
August security patches[/INDENT]
Code:
Changes in the 23/07/19 release:
[INDENT]Fixed remaining HWC issues (we now build with no hacks to upstream LOS)
Added buildprop to skip waiting for buffer fences to signal (thanks @stricted and @ivan_meler)
Build new HIDL lights HAL
[/INDENT]
Code:
Changes in the 19/07/19 release:
[INDENT]Fixed TWRP device list so it will now install correctly on variants other than A510F (thanks @dariotr)
Fixed SSWAP
Synced with latest LOS sources[/INDENT]
Code:
Changes in the 07/07/2019 release:
[INDENT]Fixed HWC (Improves UI fluidity and power usage)
SELinux cleanup (thanks @Stricted)
Migrate to new HIDL LiveDisplay and Touch HALs (thanks @Stricted)
July Android Security Patch
LOS updates[/INDENT]
Code:
Changes in the 27/06/2019 release:
[INDENT]SEPolicy: Fixed SELinux denial that broke fingerprint on some variants
kernel: added config option to fix WiFi hotspot
[/INDENT]
Code:
Changes in the 25/06/2019 release:
[INDENT]
Initial release
[/INDENT]

Build Instructions
1. Setup a LineageOS build environment based on one of the supported LineageOS 16.0 devices: https://wiki.lineageos.org/index.html
Note: All commands below are executed from the LineageOS root directory
2. Initialise the LineageOS repositories
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
3. Sync the repos (can take a log time, around 30GB of downloads)
repo sync
4. Create the .repo/local_manifests directory and add the a5xelte manifest (attached)
mkdir .repo/local_manifests/
cp ~/Downloads/a5xelte.xml .repo/local_manifests/
5. Sync our device trees in
repo sync
6. Setup the build environment
source build/envsetup.sh
7. Finally start the build:
brunch lineage_a5xelte-userdebug
To pull in new changes it is usually only necessary to repeat steps 5 - 7.

thank you so much for bringing Los Pie to our little device
Downloading it right away

Can I dirty flash it over Bunny's Los 16 build ?

MBechirM said:
Can I dirty flash it over Bunny's Los 16 build ?
Click to expand...
Click to collapse
No, I wouldn't try that.
Our device tree is very different so a clean flash is the only way.

Great ROM
Runs smoothly on my phone everything seems to work just fine, only problem is the system seems to read the fingerprint scanner as an on display scanner.

Lungss said:
Runs smoothly on my phone everything seems to work just fine, only problem is the system seems to read the fingerprint scanner as an on display scanner.
Click to expand...
Click to collapse
How do you mean?
The fingerprint scanner location variable can only be front/back/left/right and I configured it for the front. It is working fine for me.
Regards,
Danny

danwood76 said:
How do you mean?
The fingerprint scanner location variable can only be front/back/left/right and I configured it for the front. It is working fine for me.
Regards,
Danny
Click to expand...
Click to collapse
The thumbnail under the instruction to locate fingerprint scanner shows the scanner location on the screen, while the scanner itself doesn't respond to any input.
This is what I see:

danwood76 said:
No, I wouldn't try that.
Our device tree is very different so a clean flash is the only way.
Click to expand...
Click to collapse
Ok then I'll clean flash it thanks for keeping this phone alive

Lungss said:
The thumbnail under the instruction to locate fingerprint scanner shows the scanner location on the screen, while the scanner itself doesn't respond to any input.
This is what I see:
--snip--
Click to expand...
Click to collapse
I think you are taking that image too literally .
The fingerprint scanner is the home button and it doesn't work whilst the charger is plugged in (not tested that on stock but it doesn't work whilst plugged in for me on LOS).
If you are having issues with the scanner then please dump a full logcat in matlog or via ADB which should help me debug.

Fingerprint scanner don't work like on the first builds of 15.1 los

Wow, that was fast ! :good:
Thank you for bringing Pie on our A510F !
I try your ROM asap.
Guigui

skaptes said:
Fingerprint scanner don't work like on the first builds of 15.1 los
Click to expand...
Click to collapse
Ah, I have missed the additional SEPolicy rule for the FP scanner on some variants.
I will correct this later.

I've tried your ROM, and everything is working fine for me exept the firgerprint scanner, but I understand that this will be solved soon.
Very happy with this ROM, thanks for the job !
Guigui

@danwood76, I am trying to build lineageos for microg 16.0 based on your rom, but failing evertime due to the following error :-
Syncing branch repository
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
[Wed Jun 26 10:23:17 UTC 2019] Can't detect the android version
the error log, suggests this :-
"Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists"
I know this has got to do something with the ssh thing and I even tried to generate a ssh key for my local device but nothing happened.
Could you possibly suggest a solution to this.
Thanks.
The local manifest is the same that you have posted in this forum.

ashwini215 said:
@danwood76, I am trying to build lineageos for microg 16.0 based on your rom, but failing evertime due to the following error :-
Syncing branch repository
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
sed: can't read build/core/version_defaults.mk: No such file or directory
[Wed Jun 26 10:23:17 UTC 2019] Can't detect the android version
the error log, suggests this :-
"Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists"
I know this has got to do something with the ssh thing and I even tried to generate a ssh key for my local device but nothing happened.
Could you possibly suggest a solution to this.
Thanks.
The local manifest is the same that you have posted in this forum.
Click to expand...
Click to collapse
I have changed the manifest in the build post to https so it should work if you update yours.
Regards,
Danny

I have a few questions, mini review and bugs report. (and sorry for my English, i'm from Poland)
1. HWC is a Hardware Composer? Why is disabled?
2. WiFi hotspot doesn't work.
3. I saw glitches when I switched to Youtube Vanced from playback in background for a few seconds (but this is probably a problem with this app)
4. ROM is a bit faster compared to Lineage 15.1 build by danwood76, but it still having a 2D animation stuttering sometimes.

KaroloBC said:
I have a few questions, mini review and bugs report. (and sorry for my English, i'm from Poland)
KaroloBC said:
1. HWC is a Hardware Composer? Why is disabled?
Click to expand...
Click to collapse
HWC is buggy on Pie so you get black screens / lockups. We use the graphics hardware acceleration instead and it works well.
KaroloBC said:
2. WiFi hotspot doesn't work.
Click to expand...
Click to collapse
Looks like I was missing a config option for Pie, I have added this and it will work in the next build (uploading now).
KaroloBC said:
3. I saw glitches when I switched to Youtube Vanced from playback in background for a few seconds (but this is probably a problem with this app)
Click to expand...
Click to collapse
I am not the author of YouTube Vanced.
KaroloBC said:
4. ROM is a bit faster compared to Lineage 15.1 build by danwood76, but it still having a 2D animation stuttering sometimes.
Click to expand...
Click to collapse
The phones hardware isn't the quickest, when I had stock on the A5 it ran very slow. We may see slight improvements if we ever manage to fix HWC.
Click to expand...
Click to collapse

Hi,
I'm currently uploading a quick bug fix release.
Code:
Changes in the 27/06/2019 release:
[INDENT]SEPolicy: Fixed SELinux denial that broke fingerprint on some variants
kernel: added config option to fix WiFi hotspot
[/INDENT]
Regards,
Danny

Closed [Unofficial] XenonHD Pie - Galaxy Note 4 (Snapdragon) [trlte][tblte][trlteduos]

{
"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"
}
triplr's ( pronounced triple r )
My first Rom thread !!
http://www.xenonhd.com/
XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 16.0 with additional features, performance and battery life improvements.
The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".
See notes in Post 2
Device Source:
github.com/triplr-dev
Download Links:
Download tiny.cc/triplr
Story:
I have been a user of the Samsung Galaxy Note 4 (910v) since it was released.
I had been watching for the opprotunity to use Cyanogenmod on my phone,
but alas , about the time a root method was found I Cyanogen closed up.
Thankfully the codebase was pulled into Lineageos
and there I watched some wonderful development in Lineage14 by several developers
including but not limited to @_mone , who started posting how-to build for the note4
Following his successful port into Oreo one of my friends @ripee started building and took over a lot of maintaining the builds.
When @mickey387 successfully ported for Pie on the note 4, we were off to the races so to speak.
Now @ripee has lots of roms ported including this one .
working with our development group on a build server with other helpful devs and coders
we have combined all information on how to build for the note 4
at github.com/triplr-dev
special thanks and appreciation to
( if i miss you please msg me )
@micke 387
@_mone and @ripee
@mobspyguy
@khalvat
thanks to @shizzle2889 for starting the xda threads for maintenance
and all the legacy note4 devs ( adding as i can go back thru my bookmarks )
and a special thanks to a HUGE help we get from @logosA
testing, testing flashing etc !! who declined this thread.
Which is dedicated to him! I nominate him for RC if that was availble to do.
Please see the next 3 reserved posts for special information on this rom !
XDA:DevDB Information
[Unofficial] XenonHD Pie - Galaxy Note 4 , ROM for the Samsung Galaxy Note 4
Contributors
tripLr, ripee, shizzle2889, and @Inkypen and.. and... and.. All the previous devs, too many to list who made the note4 snapdragon accesseble for development, especially the verizion varient! Current Development for all the note 4 varients is due to the hard work of @ripee
Source Code: github.com/triplr-dev
ROM OS Version: 9.x Pie
Based On: LineageOS
Version Information
Status: Testing
Created 2019-08-12
Last Updated 2019-08-21

How To Build This Rom.
1. Set up your version of Linux on your computer the way you like.
2. This is a Pie version of AOSP so all the instructions at Google, are for Ubuntu and it's relatives such as what it's derived from Debian Linux all have the same naming methods for the software libraries.
I use Fedora, based off Red hat, centos, etc. I have a guide for installing these libraries on another thread and in my personal Github.com/tripLr account
Start Here
https://source.android.com/
3. Download your tools and binaries like compilers and such
Follow these instructions from Google for Ubuntu or MacOS
https://source.android.com/setup/build/initializing
Then the next page is to download the source code
You will need git ( installed above )
You will need repo ( install directly from Google , instructions in web page below )
https://source.android.com/setup/build/initializing
4 Once you have repo command installed you are ready to download any Rom you want.
We have a good collection of roms for the note 4 we build for but in this case we will download XenonHD
So first make a folder for XenonXD
Code:
mkdir -p ~/android/XenonHD/.repo/local_manifests
This step creates all the folders we need to use, now let's download our Rom
5. Repo init.
SAVE SPACE INSTRUCTIONS HERE
If you follow exactly the Google directions and most suggestions of developers YOU WILL DOWNLOAD ALL THEIR CODE not just what you need.
So the Github source code is located here for all of XenonHD code
Github.com/TeamHorizon
What we need is located on one file called the platform_manifest
https://github.com/TeamHorizon/platform_manifest
It has the instructions for downloading the ROM
Now on your computer , goto your Rom directory
Code:
cd ~/android/XenonHD
Now copy the line from the TeamHorizon manifest, but add the control to tell the server you ONLY want to download the Pie branch, not all the others.
This step is called the repo init
The version of the command they have is
"repo init -u https://github.com/TeamHorizon/platform_manifest.git -b p"
We want
Code:
repo init --depth=1 -u [url]https://github.com/TeamHorizon/platform_manifest.git[/url] -b p
6. Sync the source code.
This downloads the lists of what needs to be downloaded for the Rom,
Let's sync that.
To save space and time use,
Code:
repo sync -c --force-sync --no-clone-bundle --no-tags
If you have a fast internet connection , go make a coffee and come back. You will be downloading about 80 gb, compared to 150 or more .
7. roomservice.xml
All the goodies for the note 4 snapdragon...
Once completed now you need the roomservice to build for the note 4 snapdragon variants.
It goes in the local_manifests folder you created above, it and all the source code from Our Github account
Github.com/triplr-dev
You should be in the build folder now so..
Code:
wget -O ~/android/XenonHD/.repo/local_manifests/roomservice.xml [url]https://raw.githubusercontent.com/triplr-dev/local_manifests/xenonhd-p/master.xml[/url]
roomservice.xml can be ANYFILENAME.xml but to make it easy we all use roomservice when compiling for multiple devices
8. Sync the goodies...
Code:
repo sync -c --force-sync --no-clone-bundle --no-tags
this step wont take long..
9. Setup the environmentt OR in other words, tell the compilers where everything is.
Make sure your in your rom folder
~/android/XenonHD
and run this command
Code:
. source/envsetup.sh
what this means is tell your shell, in our case, bash,
Hey bash, there is the file located in ~/android/XenonHD/source called envsetup.sh , would you be so kind and run it so i can build my rom ? Pretty please, like right now when i press the enter key ?
You will see a list of what the script accomplishes.
Now its time to
10. Build your rom !
Hey , guess what you downloaded code for 3 devices.
Pick the one you want
Code:
# build trlte
breakfast trlte
brunch trlte
# build tblte
breakfast tblte
brunch tblte
# build trlteduos
breakfast trlteduos
brunch trlteduos
wait a bit...... wait some more...,
now browse to your output folder , use a usb cable to download to your phone, or upload to the cloud and share to the world ...

Options
Check developer options
Tons of settings for Bluetooth, codecs and bitrates
There is a section all in one place for the XenonHD settings.
Lots of cool stuff.

reserved 3
reserved 3

Thank you dev for this new and beautiful rom for our Note4.
Thank you for everything you are doing for us @tripLr
:good::good:

This rom so fast but navebar not working , also I want to ask about battery optimization is it a bug in all pie roms? I use GSM modul in magisk And still not working .

@tripLr
I gave this a good few days testing, and for me on my 910G it was just too sim deathy for me, as in i had higher than usual sim death and my usual automate script failed to recover from sim death far more often...
Currently back on AICP

73sydney said:
@tripLr
I gave this a good few days testing, and for me on my 910G it was just too sim deathy for me, as in i had higher than usual sim death and my usual automate script failed to recover from sim death far more often...
Currently back on AICP
Click to expand...
Click to collapse
Actually I had the same issue before one month , I flashed 4 different pie roms with sim death all of them , and finally I figured out the main problem I did push the sim card till the end , I just move it little out and the signal was stable again like nothing , try it maybe it works with you
I'm running last build of this rom on my N910F and signal is full always
This is the most debloated pie rom till now and battery life is nice for me

After a week on this, i can say, really awesome.
Hope you all like it.

NEW build is up guys, alive and kicking, give it a try.
Thank you dev @tripLr
:good::good:

Hi thanks for your amazing rom. How can i have play store. Thanks again.

Ok, one thing i have to have that no other rom has is multitasking phone.
Normaly when i answer a call to my ear, the display locks black and wont wake / unlock
then i have to press buttons to try and activate the screen so i can swipe to return to the call, but half the time it locks black screen again.
I have had this sissue for a loooong time,
This rom has at least 3 options to wake .
Double tap to wake
press home to wake
press power to wake.
So much nicer than pulling the battery becsuse you cant end the call of a telemarketer

vikclaus said:
Hi thanks for your amazing rom. How can i have play store. Thanks again.
Click to expand...
Click to collapse
You need gapps

logosA said:
NEW build is up guys, alive and kicking, give it a try.
Thank you dev @tripLr
:good::good:
Click to expand...
Click to collapse
I updated to 14/8 Rom become more smoother and faster , but still can't activate the navebar don't know why , always when I check Enable on-screen nav bar I have system UI restart only and navbar not shown up , going to flash 16-8 build , thanks ?

ALPHA85 said:
I updated to 14/8 Rom become more smoother and faster , but still can't activate the navebar don't know why , always when I check Enable on-screen nav bar I have system UI restart only and navbar not shown up , going to flash 16-8 build , thanks ?
Click to expand...
Click to collapse
I see the navbar setting, havent tried it yet on my own daily driver.
Please check and see if it's a system app in titanium backup , in your working copy, save it , and try to restore it in a non working copy,
If so I'll check the build log for errors, and send a note up to team horizon

tripLr said:
Options
Check developer options
Tones of settings for Bluetooth, codecs and bitrates
Click to expand...
Click to collapse
Screenshots of Bluetooth settings
Change versions to get better connection ?
Default is set for lowest / oldest release.
I'm gonna play with this for a while
Thanks @mobspyguy

tripLr said:
Options
Check developer options
Tons of settings for Bluetooth, codecs and bitrates
There is a section all in one place for the XenonHD settings.
Lots of cool stuff.
Click to expand...
Click to collapse
So there is also a setting for swipe once quick access to settings . set for left or right pull down.
Also swipe the status bar setting for brightness.
Pretty slick

Show network activity

tripLr said:
Show network activity
Click to expand...
Click to collapse
This is handy.

Clean installed 08-20 with the latest GAPPS and got bootloop. I tried flashing with no GAPPS but still didn't work.
I am so excited to try this ROM. Thank you so much for the hardwork! :good:
Samsung Galaxy Note Edge (Qualcomm)
MM Bootloader
TWRP Recovery 3.3.1-0

[ROM] [Android 10] [Stable] (AOSP) Android Open Source Project | android-10.0.0_r29

m_vaisakh said:
Vaisakh Murali:
Actually I've come to a decision, I feel like I should stop android development
It's just that for the past few days I've been away from android mostly, and it felt pretty good
I guess its time for me to be a user
Or a tester perhaps
I'm taking a break from android development, I'm really sorry to give you all hopes for Android 11 from my side. But I want to focus on my studies more. I spend too much time on android discussions and bug fixes
I hope you guys can understand
Click to expand...
Click to collapse
(from Telegram)
Tl;dr: No more updates for this./This is discontinued.
(Try out my MintOS! It is an mix of AOSP and LineageOS)

Build Instructions:
Make Sure you have setup your build system according to Android Guidelines, if not, official way to do so can found here. There are certain specifications to be met before you can build aosp, make sure you have enough specifications on your computer!
Also you have to setup repo tool from google
Code:
# Prepare folder to setup repo tool
$ mkdir ~/.bin
$ PATH=~/.bin:$PATH
# Downloading and setting up permissions for repo tool to work (You require python for repo tool to work!)
$ curl [url]https://storage.googleapis.com/git-repo-downloads/repo[/url] > ~/.bin/repo
$ chmod a+x ~/.bin/repo
Initialise AOSP Source Code from your favourite source (Here, aosp is being used.)
Code:
# Make sure you sync the code in a directory other than your home directory
$ mkdir ~/aosp
$ cd ~/aosp/
# Initialise the AOSP source code (Warning the code is several hundred gigabytes large!)
$ repo init [url]https://android.googlesource.com/platform/manifest[/url] -b android-10.0.0_r20 --depth=1
Clone my manifests, for both proper build system and device specfic requirements.
Code:
$ git clone [url]https://github.com/mvaisakh/aosp_cedric_local_manifest[/url] -b android-10 .repo/local_manifests/
Now to syncing! (This might take several hours depending on your internet connection speed!)
Code:
$ repo sync -c --no-tags --no-clone-bundle -j$(nproc --all)
Building AOSP for cedric! (This will take a while to build, depending upon your specifications.)
Code:
$ . build/envsetup.sh
$ lunch aosp_cedric-userdebug
$ mka bacon
After the Build succeeds, your rom zip will be found at:
Code:
~/aosp/out/target/product/cedric/
Flash and Enjoy!
NOTE: My device tree can be used to build other roms too! Just use the cedric.xml from my local manifest and modify device tree according to your rom and enjoy!
NOTE 2: I will not help with build errors that you might face with building, there are many guides and resources on the internet for doing that. Please keep the thread clean and void of such posts!

Releases
8th January 2020
Changelog:
* January Security Patch.
* Based on tag android-10.0.0_r25.
* Added theming (was removed by Google in android-10.0.0_r14).
* New and Amazing Fonts.
* Customisation is available in Settings > Display
* Improved Dark Theme.
* Improved Launcher & UI speeds!
* Fixed video recorder crash.
Download: https://sourceforge.net/projects/mv...-QQ1D.200105.002-20200108.033922.zip/download
6th February 2020
? Changelog:
• February security patch
• Massive theming from DerpFest, you can find it by tap and holding on the launcher home > Styles and Wallpaper.
• Enforced SELinux Build.
• Enable TypeFace Clock (Lockscreen Clock customisations)
• Improved Scrolling Cache
• Screen densities can be set to lower sizes.
• Loads of Fonts to choose from.
• A fresh new wallpaper
• WFD fix applied (untested)
Do not report bugs without proper logs.
Download: https://sourceforge.net/projects/mv...-QQ1D.200205.002-20200206.062144.zip/download
24th April 2020
? Changelog:
Platform specific:
* April Security Patch
* New fonts to choose from (some might not work, sorry for that, will remove with next update)
* Change primary colours
* More accents
* MicroG support
* Signature spoofing
* Removed unused videos from Framework
* Updated all animations from Pixel 4
* Optimised Android Runtime (Smoother than ever before)
* Better scrolling
Device specific:
* Use QCOM Surfaceflinger
* Eva EAS+ 3.0 as default kernel
* EAS Fine tuning for both better battery and performance!
* Safetynet Passes by default
* Switched to common dtb tool
* Network settings v2
* Display Colour Calibration
Download:
https://sourceforge.net/projects/mv...-QQ2A.200405.005-20200424.060707.zip/download
7th May 2020
? Changelog
Platform specific:
* Security Patch Bump
* May Security patch
Device specific:
* Eva EAS+ 1.2 as default kernel
Download: https://sourceforge.net/projects/mv...2A.200501.001.B3-20200506.204702.zip/download
14th June 2020
? Changelog:
Platform specific:
* Security Patch Bump
* June Security patch
Device specific:
* Fixed WiFi Display (screen mirroring), thanks to @CodeZero
* Kernel Security and Performance fixes from @OmegaPrimus7
Download: https://sourceforge.net/projects/mv...3A.200605.002.A1-20200613.153520.zip/download
9th August 2020
? Changelog:
• August security patch
• Kernel upgraded to Eva EAS+ v1.3
• Kernel compiled with GCC 10 for optimal performance
Download: https://sourceforge.net/projects/mv...-QQ3A.200805.001-20200808.184024.zip/download
Like my work?
Hit thanks button.
If you want to donate, please donate to a noble causes like UNESCO, and Environment Fund.

Is it the same as lineage 17 or is it another rom? Do you require arm64?

Alejandro miranda said:
Is it the same as lineage 17 or is it another rom? Do you require arm64?
Click to expand...
Click to collapse
It is another rom, Lineage has some amount of customisations, this one doesn't. Only aimed on stability and smoothness.
Yes, all ROMs since Oreo are arm64

The Moto g5 Cedric it did not come with support for Project Treble Official, if I install TWRP with Project Treble, will this ROM work and others too?

Darkyuuki said:
The Moto g5 Cedric it did not come with support for Project Treble Official, if I install TWRP with Project Treble, will this ROM work and others too?
Click to expand...
Click to collapse
this twrp from JarlPenguin: https://github.com/JarlPenguin/releases/releases/twrp3.3.1-3-cedric/
It has 32/64 bit & treble support, but it can also flash "normal" roms
I use this rom, very fast & responsive :good:

GApps
Please, i would like know more about Gapps for this rom?
What kind ? Only arm64 android 9 is available on opengapps.org. .
Thanks a lot.

morcego.surf said:
Please, i would like know more about Gapps for this rom?
What kind ? Only arm64 android 9 is available on opengapps.org. .
Thanks a lot.
Click to expand...
Click to collapse
You can use bitgapps, or other Q compatible gapps. If you use minimal gapps, they'll be limited to play store. Some modified gapps and theming support is available on the Cedric Telegram Chat.

m_vaisakh said:
It is another rom, Lineage has some amount of customisations, this one doesn't. Only aimed on stability and smoothness.
Yes, all ROMs since Oreo are arm64
Click to expand...
Click to collapse
the truth is I am left with lineage is 17 because this "ROM" is very good but when installing all the Google apps from the play store when the bootloader does not pass, and it is a bug that they have to fix, this is like android Q stock

@m_vaisakh What bugs does this ROM have?
Is she already at the flash point and?
Sorry for English because I'm using a translator.

Darkyuuki said:
@m_vaisakh What bugs does this ROM have?
Is she already at the flash point and?
Sorry for English because I'm using a translator.
Click to expand...
Click to collapse
Well, I have tested this stock Android 10 ROM, the truth is very fluid and that, but it has the same lineage errors as the Chrome videos and the camera, although here the launcher is more optimized than lineage, but I am left with lineage because it's bring more customizations it's not bring any of that, this is clean android stock, but it's ok

Alejandro miranda said:
Well, I have tested this stock Android 10 ROM, the truth is very fluid and that, but it has the same lineage errors as the Chrome videos and the camera, although here the launcher is more optimized than lineage, but I am left with lineage because it's bring more customizations it's not bring any of that, this is clean android stock, but it's ok
Click to expand...
Click to collapse
Thank you for answering my questions.

If anyone's interested, they can use my Eva Kernel EAS version and tell me how it feels to use it with AOSP.

m_vaisakh said:
If anyone's interested, they can use my Eva Kernel EAS version and tell me how it feels to use it with AOSP.
Click to expand...
Click to collapse
I will try to see, although once installed and consumed a lot of energy, a question! When will you get another update of this project? Will it be for ota?

Alejandro miranda said:
I will try to see, although once installed and consumed a lot of energy, a question! When will you get another update of this project? Will it be for ota?
Click to expand...
Click to collapse
Yes, this project will be maintained and receive monthly updates. About ota, I'll take it into consideration and will look into it when i have time.

m_vaisakh said:
Yes, this project will be maintained and receive monthly updates. About ota, I'll take it into consideration and will look into it when i have time.
Click to expand...
Click to collapse
thank you very much, I'll keep this one for now everything is fine

Can anyone confirm if Pokemon Go is working on this ROM without Magisk please? App says not compatible on Lineage 17. This is my sons phone so I really don't want to root it.

audinswfc said:
Can anyone confirm if Pokemon Go is working on this ROM without Magisk please? App says not compatible on Lineage 17. This is my sons phone so I really don't want to root it.
Click to expand...
Click to collapse
If it doesn't work on Lineage, it won't work on this. What module does it require?

m_vaisakh said:
If it doesn't work on Lineage, it won't work on this. What module does it require?
Click to expand...
Click to collapse
Well on my own device (Xiaomi Redmi Note 7, Pixel Experience 10 ROM) Pokemon Go doesn't work unless I flash Magisk and then use Magisk hide on it. However on my sons Moto G5 I have tried Lineage and even with Magisk and Magisk hide enabled Pokemon Go doesn't work unless I manually open Magisk Manager first, which I can't have him doing he's only 9 and he's going to cause some damage to his device if i'm not careful. Really don't want to go back to stock as it's awful on Moto G5. Was previously using Pixel Experience but as they've stopped developing it I wanted to try something more current. Also I found that Pixel Experience took up too much space leaving him not a lot of room for apps.
I'll just keep trying different ROMs.

Better Mobile App

welcome