[ROM][KK][4.4.2][SABERMOD] CyanogenMod 11 [5/3][DEV DISCUSSION] - AT&T Samsung Galaxy S II SGH-I777

{
"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"
}
Welcome to the unofficial CyanogenMod 11.0 nightlies​
Here begins a new surge of CM11 builds. I have teamed up with @love4k21 and are looking at outputting weekly builds. My build machine is not up right now and between that and my two jobs, it's hard to get build going again when they take aver 10 hours to complete. With a great thanks to love4k21, he will be building the Roms while I build the kernels. These new builds will ALREADY have my kernel placed in the Rom and I will host these builds on my Mediafire account. I hope yall like this new pace as I am sure you will ​
Contributors
These are the people that have helped out this thread in their own way. Whether it by helpful info or by being or giving me motivation to do what I am doing.
@iXNyNe, @trevor.bman, @razen_kain, @mr-cook, @royahaun, @david72262, @SteveMurphy and so on. Practically EVERYONE on both my threads are helpful and contribute to the discussion.
Donators(I KNOW RIGHT?! I never set out to make money doing this but to have someone give me their hard earned money blows me away. THANKS!
@royahaun
@NePanicPas
This is cross compiled with Rom = Linaro 4.7.4 and Kernel = Sabermod 4.7
DISCLAIMER
Code:
Code:
/*
* Your warranty is now 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.
*/
Also I have noticed the superuser is not 100% for some reason so I am going to look at either incorporating SuperSU or just having everyone install SuperSU from the play store. Obviously the first suggestion would be easiest for the end user. But in the mean time if you want 100% working SU then download SuperSU from the Play Store and install it using the "Normal" install option.Once done reboot.
SuperSU from Play Store
HOW TO INSTALL
Make sure you are on CWM 6.0.4.4+ before flashing ROM! Thanks to @mr-cook you can now download and flash just the recovery/kernel!
Other handy scripts you can use from mr-cook can be found: Here
Download 6.0.4.5 Recovery/Kernel created by mr-cook : Here
Download the zip
Download compatible Gapps
WIPE DATA/FACTORY RESET
Wipe Cache/Dalvic Cache
Flash the Rom
Flash Gapps
Reboot
Enjoy
Already Installed CM11
Download the zip
WIPE Cache
WIPE Dalvik Cache
Flash the zip
(Optional) Flash updated Gapps
(Optional) Fix Permissions
Reboot
Changelog and Rom Downloads in POST #2
Source: https://github.com/CyanogenMod

Download Links and Changelog
CM Commit Changelog
Recommended GApps: CM11 Compatible GApps
If you dont like torrents in the above link use: This
OR Aroma GApps (But PLEASE READ thread to make sure this is for you)
Download Links
Current Build:4/03/2014 Build 9
Comes with the stock CM11 Kernel
Sync'd CM11 Source
Compiled with new Linaro Toolchain (4.7.4) custom made for Cortex A9!!!!
Older Builds
12/07/2013 Build 1
Initial Build
12/08/2013 Build 2
Cherry-picked Exynos Camera Fixes: should fix video recording (Not Tested yet)
12/11/2013 Build 3
Initial Linaro Build (4.7.4)
Updated Mali Drivers
12/12/2013 Build 4
Linaro
(New Governors)
hotplug author: Mike Turquette <[email protected]> &
Santosh Shilimkar <[email protected]>
lulzactiveq author: Mike Chan <[email protected]>
Improved by tegrak <[email protected]>
Tuned by: gokhanmoral-robertobsc"
(New I/O Schedulers)
Updated ROW to V4.
Tweaked SIO a bit.
Added V(R) authored by Aaron Carroll <[email protected]>.
Added BFQ v6r2 authored by:
-Jens Axboe <[email protected]>
-Fabio Checconi <[email protected]>
-Paolo Valente <[email protected]>
and improved by Arianna Avanzini <[email protected]>
12/19/12013 Build 5
Synced latest CM sources
Cherry-Picked Video Recording Fix
Tried to add Low RAM option but it doesnt work . . .for now
12/23/2013 Build 6 WIFI FIXED!
Integrated Kernel build 12/29/2013 For more info about kernel please see: Link
Synced CM sources
Reverted cherry-picks to hopefully resolve minor issues
2/24/2014 Build 8
Comes with the stock CM11 Kernel
Sync'd CM11 Source
This is the smoothest build so far!!
Compiled with new Linaro Toolchain (4.7.4) custom made for Cortex A9!!!!

Screen Shots​
courtesy of @@trevor.bman​
CM11 Build Instructions​
courtesy of @@iXNyNe​
most of this is ripped from http://wiki.cyanogenmod.org/w/Build_for_i777 so visit there for extra details and explanations
You will need:
A Galaxy S II running CyanogenMod
A Linux environment; you have multiple options here
A dedicated machine (probably the quickest to make builds)
A "Dual Boot" setup (also fast, but the build can take some time so expect to get familar with linux desktop while it's building)
a Virtual Machine setup such as VirtualBox (if you run just a basic command line setup this may be faster, but if you run the full environment it's likely to be slower because of the resources)
An internet connection (probably not a hotspot... you'll be downloading ~20GB)
A Micro USB cable
*Notes: you'll want to be using the 64-bit version of whatever linux distro you choose
**I'm not going to go into detail on setting up linux here, but there's lots of tutorials
***personally I use Ubuntu linux as my daily desktop environment (I'M FREE FROM WINDOWS!)
Phase 1: Setup that only has to be done once
You'll need to install ADB (and wouldnt hurt to have fastboot)
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
next is udev rules
on ubuntu press alt+f2 and enter
Code:
gksu gedit /etc/udev/rules.d/51-android.rules
you'll be asked for a password for elevated permissions *should have been setup when you setup linux
paste this
Code:
#Samsung
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0660"
There are other rules you can add for other vendors but this one should work for all samsung devices.
Next install the other tools required to build
Code:
sudo apt-get install bison build-essential curl flex git-core gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
*note this will install the 32 and 64 bit tools, if you're on 32 bit you're doing it wrong...
Next create some directories
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
Install repo command
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Allow repo to run outside of it's directory (so you can just type repo insteas of /home/user/bin/repo)
Code:
gedit ~/.bashrc
enter the following in the text editor then save and close
Code:
export PATH=${PATH}:~/bin
Initialize the CyanogenMod source repository
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
Download the source code
Your first sync will take forever! it's just under 20GB, I recommend doing it overnight - in the future your sync will be faster because it just downloads updates.
Code:
repo sync
*Note from Render - by default the repo sync command will download using 4 simultanous connections. If you have a fast internet connection you can add more connections like this:
repo sync -j6 (or -j8 and so on)
Get prebuilt apps
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
notice the dot!
Prepare the device-specific code
Code:
cd ~/android/system
source build/envsetup.sh
breakfast i777
Extract proprietary blobs
Now ensure that your Galaxy S II (AT&T) is connected to your computer via the USB cable and usb debugging is turned ON!
Code:
adb devices
if you see your device listed then proceed, if not come here to this thread and ask for help! you cannot go further! (and won't be able to go further in the future).
Code:
cd ~/android/system/device/samsung/i777
./extract-files.sh
*Note from Render - If you setup your roomservice.xml file like below then you already have the needed device files and the above few steps really are not necessary.
Setup and modify roomservice.xml
Code:
mkdir .repo/local_manifests
gedit .repo/local_manifests/roomservice.xml
Enter this
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_i777" path="device/samsung/i777" remote="github" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Save and quit
Phase 2: Building (finally!)
Let's assume from here that you finished all of the above and got bored and closed the terminal - or that you just finished a build and are starting a new one after opening a fresh terminal (or just continuing from the instructions above) the following commands in order will set up your build environment, sync the latest changes, and pull in the patches we need for the build to work and then initiate the build. All of the commands up until brunch shouldn't take long to run, brunch can take anywhere from 2-10 hours depending on your system specs
Code:
cd ~/android/system/
repo selfupdate
repo sync
cd device/samsung/i777/
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_i777 refs/changes/90/54090/1 && git cherry-pick FETCH_HEAD
croot
cd device/samsung/galaxys2-common/
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_galaxys2-common refs/changes/65/55865/1 && git cherry-pick FETCH_HEAD
croot
export USE_CCACHE=1
. build/envsetup.sh
brunch i777
#done (as long as the build shows the out file)
If your build succeeds and you have a file you can push it to your device over usb using adb like so
Code:
cd $OUT
adb push cm-11-20140107-UNOFFICIAL-i777.zip /sdcard/
*Note that the filename should match whatever your build name (depending on the date usually just change the number)
this takes a minute or two, but once it's done you can reboot into recovery and then flash your build!
Also since you used CCACHE=1 And build from here on will now take a fraction of the time to build.

Awesome
Sent from my LG-D801 using Tapatalk

Excited to try it out!!

Is this also compiled with linaro?
Sent from my SGH-I777 using Tapatalk 2

Not yet, Its just a fully working CM11 Build for now.

Thanks a lot for this man. I am downloading it right now. I will let you know of any bugs.
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
There is a problem. I clicked the link to the ROM but it says I need mega to download the file. I suggest using drop box or mega upload to upload the file. Thanks!

csfile said:
Is this also compiled with linaro?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
azeem40 said:
Thanks a lot for this man. I am downloading it right now. I will let you know of any bugs.
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
There is a problem. I clicked the link to the ROM but it says I need mega to download the file. I suggest using drop box or mega upload to upload the file. Thanks!
Click to expand...
Click to collapse
Damn, I was trying to use Dev Host but it crapped out SO many times. I will fix it. Thanks for the heads up

RenderBroken said:
Damn, I was trying to use Dev Host but it crapped out SO many times. I will fix it. Thanks for the heads up
Click to expand...
Click to collapse
NP. It still downloads just fine, though, and I get free 50gb storage! For others, it might be a problem.

RenderBroken said:
Damn, I was trying to use Dev Host but it crapped out SO many times. I will fix it. Thanks for the heads up
Click to expand...
Click to collapse
Anyone else having issues using Mega? I was able to initiate the download without a prompt to install/download Mega like Azeem says? Apparently Dev Host wants to work for me now :silly:

EDIT: Nvm, I figured out the problem. I forgot to reboot into recovery. It was showing the old recovery.

azeem40 said:
EDIT: Nvm, I figured out the problem. I forgot to reboot into recovery. It was showing the old recovery.
Click to expand...
Click to collapse
So you were able to download the file? What did you end up having to do?

azeem40 said:
EDIT: Nvm, I figured out the problem. I forgot to reboot into recovery. It was showing the old recovery.
Click to expand...
Click to collapse
Can you explain? I can't get it to install either. I was having the same metadata recursive error. The OP says use CWM 6.0.4.4, but the newest i can find is 6.0.1.0

lordmorphous said:
Can you explain? I can't get it to install either. I was having the same metadata recursive error. The OP says use CWM 6.0.4.4, but the newest i can find is 6.0.1.0
Click to expand...
Click to collapse
You have to install the cm10.2 latest nightly, which will have 6.0.4.5.

azeem40 said:
You have to install the cm10.2 latest nightly, which will have 6.0.4.5.
Click to expand...
Click to collapse
Ironically, I'm downloading that now. Thanks.

RenderBroken said:
So you were able to download the file? What did you end up having to do?
Click to expand...
Click to collapse
I still had to do what I explained in the previous page (download MEGA and sign up for an account).

lordmorphous said:
Ironically, I'm downloading that now. Thanks.
Click to expand...
Click to collapse
azeem40 said:
You have to install the cm10.2 latest nightly, which will have 6.0.4.5.
Click to expand...
Click to collapse
lordmorphous said:
Can you explain? I can't get it to install either. I was having the same metadata recursive error. The OP says use CWM 6.0.4.4, but the newest i can find is 6.0.1.0
Click to expand...
Click to collapse
I will make that more clear in the OP. Unfortunately there is not an easier way to install the recent recovery other than flashing the newer CM10.2 nightlies.

how come this is not on the cyanogenmod website for our device?
>> http://download.cyanogenmod.org/?device=i777

ksaul said:
how come this is not on the cyanogenmod website for our device?
>> http://download.cyanogenmod.org/?device=i777
Click to expand...
Click to collapse
That is because this is an unofficial nightly. RenderBroken ported cm11 for us.
---------- Post added at 05:59 PM ---------- Previous post was at 05:38 PM ----------
Render, did you forget to include the launcher in this? Cuz when I click home, the screen goes black. Also, when I restart the phone, it goes into a bootloop. I have tried reflashing it three times and each time, the same thing happens.

Related

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

{
"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.

{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

[ROM][BULLHEAD][UNOFFICIAL] LineageOS 13.0 for Nexus 5x + Compilation tutorial!!

{
"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"
}
I built this ROM based on LineageOS 13.0 for Nexus 5x, with latest security patches. See below for more details and ENJOY IT!
Disclaimer
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/KERNEL before flashing it! YOU are choosing to make these modifications, and if you point your finger at me for messing up your device, I will laugh at you.
About this build:
• This is the updated build with the latest security patches from Google and bug fixes from LOS Team.
• TWRP recommended: 3.0.2.
• Bootloader recommended: BHZ10R (MTC20K)
• Radio recommended: M8994F-2.6.36.2.20 (MTC20K)
• Vendor: MTC20K
Instructions (clean flash recommended):
1. Make sure you unlocked your bootloader.
2. Install TWRP (version 3.0.2 recommended)
3. Flash LOS 13.0 (DOWNLOAD LineageOS-13.0)
4. Flash Gapps (OpenGapps Pico recommended: http://opengapps.org/)
DOWNLOAD ROM!
Optional packages:
• Root ( https://mirrorbits.lineageos.org/su/13.0/addonsu-arm64-signed.zip )
Bugs:
• You tell me!
XDA: DevDB Information
[ROM][BULLHEAD][UNOFFICIAL] LineageOS 13.0 for Nexus 5x
Contributors
LineageOS whole team.
ROM OS Version: 6.0.X
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Source code: https://github.com/LineageOS/android...e_lge_bullhead & https://github.com/LineageOS/android...l_lge_bullhead
Changelog: https://review.lineageos.org/#/q/sta...branch:cm-13.0
Version Information
Status: Stable
Stable Release Date: Always updated!
Created: Always updated!
Last Updated: Always updated!
Compile your own LineageOS Rom 13.0:
Use Ubuntu 14.04LTS
Simply copy and paste:
Preparing packages to compile:
Code:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk openjdk-7-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev maven maven2 libnss-sss:i386 python-networkx ccache libc6-dev-i386 x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev unzip
Code:
sudo apt-get install g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
Code:
sudo apt-get install android-tools-fastboot android-tools-adb
Code:
sudo apt-get install phablet-tools
Code:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"
EXAMPLE:
Code:
git config --global user.email [email protected]
git config --global user.name johan88
Preparing environment:
Code:
mkdir ~/bin
Code:
PATH=~/bin:$PATH
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Code:
mkdir ~/source-LineageOS-13.0
Code:
cd ~/source-LineageOS-13.0
Code:
repo init -u git://github.com/LineageOS/android.git -b cm-13.0
Code:
cd ~/source-LineageOS-13.0
This is going to take ...
Code:
repo sync
Prepare code for our device "bullhead"
Code:
source build/envsetup.sh
Code:
breakfast bullhead
Add proprietary files to the code.
Go to route:
Code:
Personal folder/source-LineageOS-13.0/.repo/local_manifests/roomservice.xml
Add in the middle these 2 lines:
Code:
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
Resync:
Code:
cd ~/source-LineageOS-13.0
Code:
repo sync
Now start the compilation:
Code:
cd ~/source-LineageOS-13.0
Code:
. build/envsetup.sh && brunch bullhead
Once finished the compilation the rom will be in:
Code:
Personal Folder//source-LineageOS-13.0/out/target/product/bullhead/
To clean everything and recompile:
Code:
cd ~/source-LineageOS-13.0
Code:
make clobber
Code:
repo sync
Code:
. build/envsetup.sh && brunch bullhead
ATTENTION! I can not support compilation errors since I am not an expert.
This is for users who still do not want to go to Lineage 14.1, have an option to be able to use CyanogenMod / LineageOS 13 in a stable way.
veloz46 said:
This is for users who still do not want to go to Lineage 14.1, have an option to be able to use CyanogenMod / LineageOS 13 in a stable way.
Click to expand...
Click to collapse
How?
Sent from my Nexus 5X using Tapatalk
paul222008 said:
How?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Excuse me, what is your question exactly?
Enviado desde mi Nexus 5X mediante Tapatalk
veloz46 said:
This is for users who still do not want to go to Lineage 14.1, have an option to be able to use CyanogenMod / LineageOS 13 in a stable way.
Click to expand...
Click to collapse
Thanks! Works good!
Hi! Great to see this! I'll try it ASAP. Thanks, @lfuentes for this tip! :highfive: If you need help @veloz46, feel free to PM me. I'm an Spanish-English translator. I think some improvement can be made in the first post.
I am doing a new compilation.
@CLPose siéntate libre de ayudarme en lo que creas conveniente.
Enviado desde mi Nexus 5X mediante Tapatalk
I am doing a new compilation.
@CLPose siéntate libre de ayudarme en lo que creas conveniente.
Enviado desde mi Nexus 5X mediante Tapatalk
Updated with the patches of this month.
Many thanks to @CLPose for your help in complementing the information of the first post!
veloz46 said:
Updated with the patches of this month.
Click to expand...
Click to collapse
OK, Downloading...
Hi! Does anyone try this ROM in MTC20F bootloader, radio, vendor? I don't know why, but I can't flash a permanent TWRP in MTC20K. So I want to know if this could work in MTC20F. Is it risky to try it? Thanks!
CLPose said:
Hi! Does anyone try this ROM in MTC20F bootloader, radio, vendor? I don't know why, but I can't flash a permanent TWRP in MTC20K. So I want to know if this could work in MTC20F. Is it risky to try it? Thanks!
Click to expand...
Click to collapse
I do. It works well. Try to flash a full stock MM. Then flash twrp 3.1
Building May update request
Hey, thank you for this updated lineage 13 for bullhead ! Necessary for Xposed users... This April built is very stable for daily use. Can someone please build an updated version with May security ? Thanks
i-Pericles said:
Hey, thank you for this updated lineage 13 for bullhead ! Necessary for Xposed users... This April built is very stable for daily use. Can someone please build an updated version with May security ? Thanks
Click to expand...
Click to collapse
+1
Okay, a see I can do.
This month's patches have not yet been applied, the compilation is also uploading.
Enviado desde mi Nexus 5X mediante Tapatalk
OK. Waiting...
The ROM has been uploaded. Downloading now...
Official CM13 N5X maintainer review on Lineageos 13 by veloz46
Hey, thank you again veloz46 for your work on Lineageos 13, I asked a review from razorloves (official maintainer) about your ROM on official CM13 thread.
Can you clarify the work made on security patching in your ROM and answer razorloves here please ? Thanks

lineage-14.1-20190302-[Final Build] with microG for i9300

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is 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.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within 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 Gerrit Code Review.
Wiki
Official LineageOS Wiki: http://wiki.lineageos.org/devices/i9300
Known issues
 @curiousrom has a list of known issues/workarounds. You can see them here: https://forum.xda-developers.com/showpost.php?p=76224958&postcount=4419
Installation
(NOTE: if you experience robotic voice during calls: see the FAQ for a fix)
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Unfortunately, now you have to wipe to come from CM - see "First time LineageOS14.1 installation on your Galaxy S III", or if you're brave try the instructions on changing keys.
First time LineageOS 14.1 installation on your Galaxy S III:
Read the official Wiki page
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the Lineage 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the Lineage 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - Lineage Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 or higher to automatically install updates in Lineage 14.1)
Push the new Lineage 14.1 zip to your SD card
Boot into Recovery
Flash the Lineage 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Install packages: https://download.lineage.microg.org/i9300/lineage-14.1-20190302-microG-i9300.zip
Google Apps (arm): https://wiki.lineageos.org/gapps
Root add-on (arm): https://download.lineageos.org/extras
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modified system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
F.A.Q.
Root?
Flashable zips to install/uninstall root can be found here. Download the "arm" variants.
Robotic voice during calls?
Try using the I9300XXUGMK6 modem. Instructions are here.
GPS Issues?
Probably a hardware issue. Try tightening the screws on the back of the device, or see this video for more information (thanks to @baltics for the link)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
good job
i like what you have done, only there is 1 problem. when i install the rom its in a loop while searching for updates and when i try to put data from another phone to it and i enter my google account i got a message like this: the previous owner need to log in before you can use this phone.
when i use another rom i have no problems. can you please fix this?
Thank you very much for this ROM, works very good. Haven't noticed any big problems yet
Please re-insert the rom because the link has expired
recheck download link please !!!! ??
ataman76 said:
Please re-insert the rom because the link has expired
Click to expand...
Click to collapse
HANA.BICO said:
recheck download link please !!!! ??
Click to expand...
Click to collapse
Use up to date lineageOS 14.1 and nanodroid.
E.foundation also builds a lineageOS based ROM with microG.
kurtn said:
Use up to date lineageOS 14.1 and nanodroid.
E.foundation also builds a lineageOS based ROM with microG.
Click to expand...
Click to collapse
i don't understand !! where i can download this rom ?
download link don't work !!
HANA.BICO said:
i don't understand !! where i can download this rom ?
download link don't work !!
Click to expand...
Click to collapse
https://download.lineage.microg.org/i9300/
It's been deleted from the servers, if you want this particular rom you can build it yourself.
Sly Fox007 said:
https://download.lineage.microg.org/i9300/
It's been deleted from the servers, if you want this particular rom you can build it yourself.
Click to expand...
Click to collapse
how i can build it?
HANA.BICO said:
how i can build it?
Click to expand...
Click to collapse
With dokker
https://lineage.microg.org/#faq
HANA.BICO said:
how i can build it?
Click to expand...
Click to collapse
Easiest way is with docker
I'm assuming you're using windows, here's how to install docker.
Code:
docker run \
--name=i9300_build \
-e "BRANCH_NAME=cm-14.1" \
-e "DEVICE_LIST=i9300" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend FDroid FDroidPrivilegedExtension " \
-v "C:/Users/<user>/lineageBuild/lineage:/srv/src" \
-v "C:/Users/<user>/lineageBuild/zips:/srv/zips" \
-v "C:/Users/<user>/lineageBuild/logs:/srv/logs" \
-v "C:/Users/<user>/lineageBuild/cache:/srv/ccache" \
-v "C:/Users/<user>/lineageBuild/keys:/srv/keys" \
-v "C:/Users/<user>/lineageBuild/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
with microg.xml in manifests
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lineageos4microg/android_prebuilts_prebuiltapks" path="prebuilts/prebuiltapks" remote="github" revision="master" />
</manifest>
I can provide a mirror of the last version if it is ok?
lineage-14.1-20190302-microG-i9300.zip
IceXcube84 said:
I can provide a mirror of the last version if it is ok?
lineage-14.1-20190302-microG-i9300.zip
Click to expand...
Click to collapse
Please provide an alternate link. Or suggest me good microG rom
msb arkon said:
Please provide an alternate link. Or suggest me good microG rom
Click to expand...
Click to collapse
I would take non-microG lineage 14 and apply nanodroid patcher.
OK
Sly Fox007 said:
Easiest way is with docker
I'm assuming you're using windows, here's how to install docker.
Code:
docker run \
--name=i9300_build \
-e "BRANCH_NAME=cm-14.1" \
-e "DEVICE_LIST=i9300" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend FDroid FDroidPrivilegedExtension " \
-v "C:/Users/<user>/lineageBuild/lineage:/srv/src" \
-v "C:/Users/<user>/lineageBuild/zips:/srv/zips" \
-v "C:/Users/<user>/lineageBuild/logs:/srv/logs" \
-v "C:/Users/<user>/lineageBuild/cache:/srv/ccache" \
-v "C:/Users/<user>/lineageBuild/keys:/srv/keys" \
-v "C:/Users/<user>/lineageBuild/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
with microg.xml in manifests
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lineageos4microg/android_prebuilts_prebuiltapks" path="prebuilts/prebuiltapks" remote="github" revision="master" />
</manifest>
Click to expand...
Click to collapse
Where do I have to enter this code? What do I have to do with the xml? Is there a beginner-friendly declaration?
@HANA.BICO & @EVGENIJ88 @msb-arkon
https://web.archive.org/web/20190414130532/https://download.lineage.microg.org/i9300/lineage-14.1-20190302-microG-i9300.zip
This ROM was saved by archive.org (the internet archive).
https://web.archive.org/web/20190414130532/https://download.lineage.microg.org/i9300/lineage-14.1-20190302-microG-i9300.zip

[ROM][UNOFFICIAL] LineageOS 20.0 for Nexus 6

{
"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"
}
lineage-20.0-20230222-UNOFFICIAL-shamu.zip
lineage-20.0-20221217-UNOFFICIAL-shamu.zip
lineage-20.0-20221014-UNOFFICIAL-shamu.zip
Known issues:
- On some boots the camera may not be working. Simply reboot your phone to fix it.
How to enable encryption on the February build and newer:
- Data must be formatted. If you're using TWRP, click wipe and then format data
- Install the LineageOS zip
- Install the attached SetEncryption.zip
- Reboot and enjoy encryption
How to build from source:
I'm going to assume you've built LineageOS before and just describe the special steps
- Repo init with the LineageOS-UL sources here: https://github.com/LineageOS-UL/android
- Copy the attached roomservice.xml to .repo/local_manifests
- Sync the sources
- From the source root execute:
Code:
sed -i "s/.*TARGET_BUILD_UNBUNDLED.*/ifeq (0,1)/" build/make/core/tasks/platform_availability_check.mk
- If you want your builds to use encryption then run:
Code:
sed -i "s/latemount/latemount,fileencryption=adiantum/" device/moto/shamu/rootdir/etc/fstab.shamu
- cd to frameworks/opt/net/ims and run git apply path_to_attached_Ignore-SubId.patch
- DO NOT use an existing vendor repo . You must run ./extract-files.sh on the latest build I've provided
- Build as normal
Kernel Source: https://github.com/rootfan/android_kernel_moto_shamu
Special thanks to:
- LineageOS team
- Elektroschmock, npjohnson, and anyone else who has worked on shamu in the past
- abhishekt295 and wavedashdoc for getting IMS to work on android 10
- tarkzim and khalvat for their work on the LineageOS-UL project
Standard disclaimer: You're responsible for what you do to your devices, so don't blame anyone else if something goes wrong.
Enjoy android 13 on the Nexus 6
bravo!!!!!!!
any build plan for angler?
Which gapps to use with this build?
Hey, I'm here to do some reports.
My last OS is Mokee based on Oreo 8.1 and I flashed this from with TWRP 3.1.1-0.
When the first time I try to flash it notices that "This package is for shamu, and your device is [empty]." So I removed the asserts check from update-script and I made it this time.
Here are my steps to flash this:
1. Reboot into recovery, wipe data.
2. Wipe data, davlik, system, data, and cache.
3. Flash the rom
4. Format data
5. Reboot
Now it is stuck in the loop of lineage os boot animation. Any suggestions?
I happen to come across this thread and just had to poke my head in here real quick and say "hell yeah! ' " Long live the Nexus!! "I always like it when I see a Nexus still getting current rom love. I had all of the Nexus devices.
Those were the days!!
lepi said:
Which gapps to use with this build?
Click to expand...
Click to collapse
I used BiTGApps-arm-13.0.0-v1.4_signed.zip. I did dirty flash to lineage-19.1-20220919-UNOFFICIAL-shamu. lineage-20.0 booted without any problem.
MindTheGapps-13.0.0-arm-20221007_211145.zip may be used instead.
TatsuMasa said:
I used BiTGApps-arm-13.0.0-v1.4_signed.zip. I did dirty flash to lineage-19.1-20220919-UNOFFICIAL-shamu. lineage-20.0 booted without any problem.
MindTheGapps-13.0.0-arm-20221007_211145.zip may be used instead.
Click to expand...
Click to collapse
Used MindTheGapps 13, thanks
Thanks a lot! Great work!
the camera is not working, please tell me how to fix it
bccrosby said:
the camera is not working, please tell me how to fix it
Click to expand...
Click to collapse
Be patient. Release 20.0 is very early. Take a look at >chengelog<. Work continues, including on the camera.
bccrosby said:
the camera is not working, please tell me how to fix it
Click to expand...
Click to collapse
Just reboot your phone and then the camera should work fine.
rootfan said:
Just reboot your phone and then the camera should work fine.
Click to expand...
Click to collapse
thank you for android 13 on the nexus 6 although the play store cant update apps because it doesnt have a storage permission
for some reason
@rootfan
Thanks for your work !
I was feeling adventurous this morning so I tried to build with your repos
To do so I've gotten to adding the following lines to my roomservice.xml
XML:
<project path="kernel/moto/shamu" remote="github" name="rootfan/android_kernel_moto_shamu" revision="los-20.0" />
<project path="device/moto/shamu" remote="github" name="rootfan/android_device_moto_shamu" revision="los-20.0" />
<project path="vendor/motorola" remote="github" name="TheMuppets/proprietary_vendor_motorola" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" revision="lineage-18.1" />
but build is failing with
Code:
FAILED:
build/make/core/main.mk:1308: warning: device/moto/shamu/lineage_shamu.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
nfc_nci.bcm2079x.default
build/make/core/main.mk:1308: error: Build failed.
12:15:32 ckati failed with: exit status 1
--> What am I missing ?
I noticed you also have a android_frameworks_opt_telephony repo, but I have not used it as your initial post suggests only kernel source and device tree repos are necessary. --> Is it also required ?
Lastly, do you plan on merging the shamu: Kang DRM from angler commit that make NEtflix work again !
Looking forward to testing this on my shamu
dwardo said:
@rootfan
Thanks for your work !
I was feeling adventurous this morning so I tried to build with your repos
To do so I've gotten to adding the following lines to my roomservice.xml
XML:
<project path="kernel/moto/shamu" remote="github" name="rootfan/android_kernel_moto_shamu" revision="los-20.0" />
<project path="device/moto/shamu" remote="github" name="rootfan/android_device_moto_shamu" revision="los-20.0" />
<project path="vendor/motorola" remote="github" name="TheMuppets/proprietary_vendor_motorola" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" revision="lineage-18.1" />
but build is failing with
Code:
FAILED:
build/make/core/main.mk:1308: warning: device/moto/shamu/lineage_shamu.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
nfc_nci.bcm2079x.default
build/make/core/main.mk:1308: error: Build failed.
12:15:32 ckati failed with: exit status 1
--> What am I missing ?
I noticed you also have a android_frameworks_opt_telephony repo, but I have not used it as your initial post suggests only kernel source and device tree repos are necessary. --> Is it also required ?
Lastly, do you plan on merging the shamu: Kang DRM from angler commit that make NEtflix work again !
Looking forward to testing this on my shamu
Click to expand...
Click to collapse
Try to track this in your manifests, maybe it will work.
GitHub - LineageOS/android_hardware_broadcom_nfc
Contribute to LineageOS/android_hardware_broadcom_nfc development by creating an account on GitHub.
github.com
Furthermore,resync @rootfan 's repos for 20.0 branch when he make it up-to-date.
Can someone kindly confirm GPS works on this build? I have LinOS 20 on another phone (admittedly an ancient Sams. Note 2) and the GPS works but very sluggish. All else works fairly well.
On my Nexus 6, I have the well-cared for LinOS 18.1 and GPS is very quick- the whole ROM is rock solid. I can of course make a recovery copy but just want to know what to expect as this is still my daily driver. Some of the rebooting & charging issues also make me a bit uneasy. I know it is still early days and am only grateful for rootfan's efforts.
What have any of you lab rats (just kidding) experienced so far specifically regarding GPS with this 20 ROM on a nav map system e.g. Organic or Google Maps? Thanks
TotalChen said:
Try to track this in your manifests, maybe it will work.
GitHub - LineageOS/android_hardware_broadcom_nfc
Contribute to LineageOS/android_hardware_broadcom_nfc development by creating an account on GitHub.
github.com
Furthermore,resync @rootfan 's repos for 20.0 branch when he make it up-to-date.
Click to expand...
Click to collapse
That got me to the next issues .
tons of warnings turned to errors (found how to bypass that) as -Werror compile option is set
kernel includes not found by other projects
Seems rootfan's modification's are not up to date or all available on his github. Will check from time to time and see if updates become available.
Took the plunge as I can quickly and easily revert back to rock solid LOS18 if nec. with TWRP backup. So..
Unlocked phone and SIM card, dirty flashed ROM, BitGaps 1.6, Magisk 24.3s.....
Whole installation, a few reboots, some App checking, took like 10 Min. Dirty flash saves hours of re-confiuring and reinstalling files and apps. YMMV but as I am fully backed up, it was well worth a try.
All seems just fine. Banking apps, travel, cars etc. all good. My Open Camera app, and the built in Camera all sans problems. Even kept some deep Magisk modules. Will have to watch for a few days re GPS, notifications, battery life. It is slightly less smooth than LOS18 but can easily live with it, and it may improve over time. Have asked trusted wingman to also try and monitor.
@rootfan Nice one; hope you'll keep supporting and updating this great work.
Thank you @rootfan for bringing new up to date life to Shamu . Really amazing to see android 13 on it !
Just a heads-up. Reporting, not complaining.
I followed @esysfound in dirty flashing my N6, and it looked good, but today I've booted from cold and I'm in a bootloop - the LOS circles have been running for a while with occasional reboots. No problem - (a) I knew dirty flashing isn't reliable and (b) I can restore my OrangeFox 19.1 backup.
Just in case anyone is thinking of trying a dirty flash...

Categories

Resources