Related
Hey guys!
Im new to rom development/porting but I have some experiences in development/linux in general, so I tried to port B2G to my i9001 using
h t t p s:// wiki.mozilla.org/B2G/Porting (I really like the idea of B2G).
I ran into some questions during the process:
Clone B2G repo,Create local backup of the original Android system - piece of cake
Add new device in config.sh
seems not to hard
default.xml
i took the s2 config and changed simply
<project path="device/samsung/galaxys2" name="android-device-galaxys2" remote="b2g" revision="master" />
<project path="hardware/broadcom/wlan" name="platform/hardware/broadcom/wlan" />
to
<project path="device/samsung/galaxysplus" name="android-device-galaxysplus" remote="b2g" revision="master" />
Create configuration tree for new device
I found most files on arcos github-page.
h t t p s://github.com/arco/android_device_samsung_ariesve
I couldnt figure out where to get the sources for the kernel (or get a working boot.img for this project).
The canges in the init.rc (init.qcom.rc I guess) are pretty self-explanatory. Editing the flash.sh is also pretty straight, since s2 tools should work here (I hope).
I hope somebody can help me here
Hey I figured out that Id only need a boot.img that would work with arcos files so I extracted mine (CM9 alpha 5). Seems to work but Im really not sure if I should flash it. Anything else I need to do? Does this affect my recovery? Any help would be great!
Resource:
h t t p://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Could somebody please move this to the i9001 dev-section? I dont want to spam 10 times just to be able to repost there.
i need 5 more messages so ill spam here
spam spam spam
asdasd
happy spamming
last
This is a guide to build CyanogenMOD 10.2 (Android 4.3) for Google Nexus 4. This guide is for OS X Mountain Lion (10.8).
[size=+1]Pre Requirements:[/size]
1) go to App Store on your OS X and Download Xcode 4. Once that is installed, open Xcode and go to preferences. There you find a tab “DOWNLOADS”, open it and there you can find “Command line tools” and next to it click INSTALL. It will take a few minutes to download and install
2) Make sure you have the android-sdk downloaded and setup adb and fastboot, so they work. It is recommended to place the android-sdk to /usr/local/
[size=+1]Initializing the build environment[/size]
First we need to set up our OS X to be able to build Android. This needs some extra things compared to for example, building in Linux, but the main stuff is pretty much the same. So let’s get started then, shall we?
Open up Terminal and type
Code:
java
If you don’t have java installed you will get a prompt to install it.
Next we will install homebrew (you can also use macports if you like)
Code:
ruby <(curl -fsSk https://raw.github.com/mxcl/homebrew/go)
Now make sure android-sdk and homebrew are in $PATH
Code:
touch ~/.bash_profile && echo "PATH=/usr/local/bin:/usr/local/sbin:$PATH:/usr/local/android-sdk/tools:/usr/local/android-sdk/platform-tools" >> ~/.bash_profile
I also recommend to add this edit to the .bash_profile file:
Code:
nano –w ~/.bash_profile
Code:
export BUILD_MAC_SDK_EXPERIMENTAL=1
Now run this and see if you need to update anything.
Code:
brew doctor
If you do (and you probably will once a day) type:
Code:
brew update
Now we need to get our dev packages
Code:
brew install git coreutils findutils gnu-sed gnupg pngcrush repo
Once that is done, run
Code:
brew outdated
if it shows anything, run
Code:
brew upgrade
Now run this the correct a few symlinks [Not sure if these are needed anymore]:
Code:
ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed
Now to create our case sensitive image for our CM work [NOTE: the 60g can be changed to anything. It only takes up what it needs but I used 60GB]:
Code:
hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 60g -volname "android" -attach ~/Desktop/Android
Now to create our working directory
Code:
cd /Volumes/Android && mkdir cm10.2 && cd cm10.2
[size=+1]Getting the source[/size]
Now to initialize the git and to download it
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Download the sources:
Code:
repo sync
Wait until it is finished. It will take a long time, depending on your internet connection.
[size=+1]Obtain the device build files and proprietary files:[/size]
To do this we will use CyanogenMods "tool" called roomservice. Roomservice is replacing the old local_manifest.xml file. Just run the code below to create the file directly into the folder.
Code:
nano -w /Volumes/android/cm10.2/.repo/local_manifests/roomservice.xml
Paste the following lines into the file:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>
</manifest>
It seems that nowadays you only need to have the TheMuppets repo there, the roomservice process takes care of the rest and downloads the needed mako bits automatically. And actually it doesn't matter what you name the xml file under the local_manifests directory. The process loads every xml file from there in a alphabetical order. If you still have that local_manifest.xml file in your .repo directory, i suggest you remove that, because at that case that file will be read first and after that all the other from the local_manifests folder
Save the file. And rerun the code:
Code:
repo sync
Download the necessary pre-builts:
Code:
/Volumes/android/cm10.2/vendor/cm/get-prebuilts
That is all. The sources are now ready.
[size=+1]Building CyanogenMOD[/size]
If you build now, you're probably gonna get kernel build errors regarding the missing elf.h header (this error might be device specific). Fortunately, we already have this file downloaded, so we only need to copy it to /usr/local/include:
Code:
cp /Volumes/android/cm10.2/external/elfutils/libelf/elf.h /usr/local/include
FINALLY, we are ready to build:
Code:
cd /Volumes/android/cm10.2 && source build/envsetup.sh && brunch mako
Change “mako” to something else if you want to build for another device (of course needs to be supported by CM)
Then we just let the Mac do the rest. Remember that it will take a while to do the build, and meantime you Macs fans will scream for mercy while CM punishes your system ☺
After the build is finished successfully you can find your newly created flashable zip by typing:
Code:
cd $out
Look for .zip file with a tag UNOFFICIAL
Happy building!
[size=+2]Credits:Imperticus (borrowed some stuff from his guide
ArmanUV (borrowed some stuff from his guide[/size]
Build errors
jeroenqui said:
if you get a similar error like this when building, here is the solution:
Zcat: /volumes/android/cm10.1/out/target/product/mako/ramdisk.img.z: No such file or directory
then it's because zcat is old and broken. Do this to fix it and use the newer version: Gzcat
sudo mv /usr/bin/zcat /usr/bin/broken-zcat
sudo ln -s /usr/bin/gzcat /usr/bin/zcat
Click to expand...
Click to collapse
And this too
Is it possibile to build on osx leopard 10.5?
Inviato dal mio Nexus 4
Excellent write up
Cice96 said:
Is it possibile to build on osx leopard 10.5?
Inviato dal mio Nexus 4
Click to expand...
Click to collapse
Not totally sure but it should be possible.
kennyp987 said:
Excellent write up
Click to expand...
Click to collapse
Thanks!
Can you do same things for aokp
Awesome work !
Envoyé depuis mon Nexus 4 avec Tapatalk
Excellent! Will give it a try and let you know how it goes! Can you maybe add instructions for cherry picks?
Thanks!!!
Sent from my Nexus 4 using xda premium
+1
Sent from my Nexus 4 using Tapatalk 2
This worked for me. Thanks OP!
how much time takes to build ?
Zasuk said:
how much time takes to build ?
Click to expand...
Click to collapse
Build times will depend on what Cpu, memory and hardrive you have.
My Macbook pro is a little older (2009) and is running a core 2 duo, with 8gigs of ram and a Momentus hybrid XT hardrive.
My build times are about 2.5 hours. Using ccache, and not doing a make clobber before the build, build times will drop down to about 30 minutes or less for me.
Just wanted to say thanks to the OP for the guide. Everything worked like a charm.
One thing I did, just to avoid any unknown problems was to download the 10.6 sdk and add it to the Xcode sdk folder just for a little extra insurance being new to building with my Mac.
i have this error any idea ? thank you for this excellent thread !
hdiutil: create failed - Ressource occupée
hey man,
what would the local_manifest.xml look like for the AT&T Galaxy S3 (d2att) ?
[GUIDE] Building CM10.1 for Nexus 4 with Mac OS X Mountain Lion (aka OS X 10.8)
jakew02 said:
hey man,
what would the local_manifest.xml look like for the AT&T Galaxy S3 (d2att) ?
Click to expand...
Click to collapse
No idea
jakew02 said:
hey man,
what would the local_manifest.xml look like for the AT&T Galaxy S3 (d2att) ?
Click to expand...
Click to collapse
This is what mine looks like for d2vzw. I'd imagine you just replace the vzw with att:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung/" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
</manifest>
Re: [GUIDE] Building CM10.1 for Nexus 4 with Mac OS X Mountain Lion (aka OS X 10.8)
How big is the sparseimage you guys made? I tried with 5gb and it filled up without finishing. My Mac partition only got 10gb of free space.
Sent from my Nexus 4 using Tapatalk 2
[GUIDE] Building CM10.1 for Nexus 4 with Mac OS X Mountain Lion (aka OS X 10.8)
sh0td0wn said:
How big is the sparseimage you guys made? I tried with 5gb and it filled up without finishing. My Mac partition only got 10gb of free space.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
5gigs isä way too small.
The source hogs at least 15gb (about) and building takes at least the same. So I made a 70gb image so it wouldn't fill up
Awesome guide! Any chance you can tell us how to build it with the Linaro toolchain and Bionic stuff everyone says makes android faster?
---------- Post added at 01:27 PM ---------- Previous post was at 12:34 PM ----------
FYI this command is failing:
/usr/bin/ruby -e "$(/usr/bin/curl –fsSL https://raw.github.com/mxcl/homebrew/master/Library/Contributions/install_homebrew.rb)"
Looks like the URL is no good any more.
EDIT: This is the new command for downloading homebrew:
ruby <(curl -fsSk https://raw.github.com/mxcl/homebrew/go)
Hey guys
I guess you already know the drill It's more-less the same as we did on CM11, but Adam77Root isn't actively developing for the device anymore and also Demetris isn't working on this project anymore. I am pretty busy lately myself, which is why you shouldn't expect any miracles soon.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, and we will most likely merge it happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let us know about it before you release it and give credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
You tell me
Possibly more
Working:
Everything else
Now, the most important part:
Download
All builds can be found on my goo.im account:
CM12
CM12.1
Please note that goo.im is currently having issues, which is why the latest builds are available from the devDB downloads tab.
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[ROM] [WIP] Unofficial CM12.1 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf, Adam77Root, sunsettrack4
Source Code: https://github.com/P880-dev/android_kernel_lge_x3/tree/cm-12.0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-11-09
Last Updated 2015-04-06
Reserved
I have used the following local_manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- p880 specific stuff -->
<project name="P880-dev/android_device_lge_p880" path="device/lge/p880" remote="github" revision="cm-12.0" />
<project name="P880-dev/android_kernel_lge_x3" path="kernel/lge/x3" remote="github" revision="cm-12.0" />
<project path="vendor/lge" name="P880-dev/proprietary_vendor_lge" revision="cm-12.0" />
<remove-project path="device/asus/fugu" name="device/asus/fugu" groups="device,fugu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/fugu-kernel" name="device/asus/fugu-kernel" groups="device,fugu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/grouper" name="device/asus/grouper" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/asus/tilapia" name="device/asus/tilapia" groups="device,grouper" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder" name="device/htc/flounder" groups="device,flounder" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/htc/flounder-kernel" name="device/htc/flounder-kernel" groups="device,flounder" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu" name="device/moto/shamu" groups="device,shamu" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/moto/shamu-kernel" name="device/moto/shamu-kernel" groups="device,shamu" clone-depth="1" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
<remove-project path="device/samsung/manta" name="device/samsung/manta" groups="device,manta" remote="aosp" revision="refs/tags/android-5.0.0_r2" />
</manifest>
if you run into some errors, just remove the according "remove-project" line and you should be fine
Thank you!
Thank you @laufersteppenwolf, @Demetris for all your efforts! I'll build it later, and try to help you with logs and anything else i can do, as much as i can! Keep up, mates, brilliant job!
Thanks man! I will go download sources now!
SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
Tim_Pan said:
SurfaceFlinger problem again...
SurfaceFlinger will initialize failed with our old blobs on the hacked framework native,and it will crash with n7 blobs as well.
edited:
n7 2012 factory image leaked.
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
Click to expand...
Click to collapse
SF issues should be gone, is you've got the latest sources. It was related to SELinux, which is why I completely killed it via kernel for now
Also, I highly doubt that you're gonna have much success using the stock blobs (which is why I'm not even gonna try)
I wil try building when I get home
Any News?
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
Yeah good idea.
fritzcola said:
Any News?
Click to expand...
Click to collapse
Not really haven't got much free time lately to test...
iSWORD14 said:
If you could kindly upload the ZIP you would save me 8 hours of building on my i3 laptop. I know i need to rebuild it if i wanted to make any changes, but at least i might be able to fix a few things by only building a couple binaries and sideloading them instead of building the whole OS.
Click to expand...
Click to collapse
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
laufersteppenwolf said:
Not really haven't got much free time lately to test...
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
No Problem
Keep up the great work.
Im sure you are going to fix it soon.:good:
laufersteppenwolf said:
I will most definitely not publically upload something that's not working. I may PM you a build if you want, but not publically.
If you want the build, let me know.
Click to expand...
Click to collapse
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.
If anyone get a bootable Build, can he upload it!!
Thx
fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
Help us to achieve that
If i could of course i would but im sure i cant help you. My skills are very little
iSWORD14 said:
You can put a warning next to the link. I think someone did something similar with an HTC sense port IIRC.
Anyway, if you prefer not to share it in public, I'd appreciate it if you can PM it to me.
Click to expand...
Click to collapse
Well, some may do that, but I am not like that I have seen just too many things happen to phones just because people didn't read and just downloaded something with the name of their device on it.
fritzcola said:
If anyone get a bootable Build, can he upload it!!
Thx
Click to expand...
Click to collapse
The same thing as last time is going to happen: As soon as we've got a halfway working build, it will be released. Until then, there won't be a public release.
And I also ask anyone to please not publically post a build until it doesn't properly work (and by properly I mean the important things like network, audio, ... )
Alright, a general update on the situation:
SF issues are gone and we've got a boonanimation. But ATM, we are bootlooping due to audio issues.
The problem is, I have no idea what exactly is causing the issues, as the logs do not specify it (it's literally being shown as <unknown>). I was hoping that fixing the AudioWrappers would at least resolve the bootloop, but no dice.
If you want to look into it yourself, logcat and a strace from mediaserver is located HERE
Thanks to @LGaljo for the logs
News?
Busaton said:
News?
Click to expand...
Click to collapse
Dont think so
There are no news, because we keep everything private and deliberately not telling anything about the progress that have been made. :beer:
THIS MODULE ENABLES UNLIMITED FULL RESOLUTION UPLOAD IN GOOGLE PHOTOS
REPORTS SAY IT DOESN'T WORK
Update 3 – Uploads May Still Count Against Drive Storage
We’re hearing reports that this trick was discovered by the team over at OpenGapps a few months back and was quietly patched by Google already. In that case, applying this trick will still result in uploaded photos to apply against your Google Drive storage (ie. it doesn’t work). We haven’t confirmed this ourselves, but if/when we do we will update the above tutorial.
Click to expand...
Click to collapse
Update 4 – Google Photos Unlimited Storage Not Working, Pixel Wallpapers Still Work
I have confirmed that photos uploaded in “original quality” using this trick still count against your Drive storage. My Drive shows that I uploaded 0.2GBs of photos and videos from yesterday. This means that the trick was patched, likely when it was discovered by the people over at OpenGapps. It’s strange that this trick somehow still triggers Google Photos into showing you the original quality onboarding message, though.
Click to expand...
Click to collapse
Code:
Thread will be updated to look nicer. Atm I was in a hurry to post this for everyone to use
FLASH IN RECOVERY, FLASHING THROUGH MAGISK MANAGER ISN'T WORKING
What about photos already uploaded?
Inviato dal mio Nexus 6P utilizzando Tapatalk
---------- Post added at 10:33 ---------- Previous post was at 10:28 ----------
dariomrk said:
THIS MODULE ENABLES UNLIMITED FULL RESOLUTION UPLOAD IN GOOGLE PHOTOS
Code:
Thread will be updated to look nicer. Atm I was in a hurry to post this for everyone to use
Click to expand...
Click to collapse
Install fails on Magisk Manager 5.3.0 (on MagiskSu v14)
Inviato dal mio Nexus 6P utilizzando Tapatalk
Helpful module will try to install this on my S6
Sent from my SM-G920F using Tapatalk
CyberZeus1977 said:
What about photos already uploaded?
Inviato dal mio Nexus 6P utilizzando Tapatalk
---------- Post added at 10:33 ---------- Previous post was at 10:28 ----------
THIS MODULE ENABLES UNLIMITED FULL RESOLUTION UPLOAD IN GOOGLE PHOTOS
Install fails on Magisk Manager 5.3.0 (on MagiskSu v14)
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Works if you Install it via Recovery.
Does this module makes every app think that my phone is Pixel?
Shished said:
Does this module makes every app think that my phone is Pixel?
Click to expand...
Click to collapse
Yes... Could anybody make a module that only adds the nexus.xml?
Simeonico said:
Yes... Could anybody make a module that only adds the nexus.xml?
Click to expand...
Click to collapse
There you go
https://drive.google.com/open?id=0B35Q-_-S5yi-SENWYkNyTU1JX3M
Does this module edit build.prop and change device name to Pixel 2 XL ?
Sent from my Nexus 6 using XDA Labs
StaticBlaze said:
There you go
https://drive.google.com/open?id=0B35Q-_-S5yi-SENWYkNyTU1JX3M
Click to expand...
Click to collapse
Thank. This module works and does not changed the device name.
Edit: I will upload my module without Pixel 2 XL build.prop later as an alternative (just the nexus.xml)
dariomrk said:
Edit: I will upload my module without Pixel 2 XL build.prop later as an alternative (just the nexus.xml)
Click to expand...
Click to collapse
Thanks for the awesome module! I was able to modify the system.prop, in the common folder, to match my device. Seemed to do the trick.
Will not work!
https://www.xda-developers.com/enable-google-photos-unlimited-storage/amp/
Update 3 – Uploads May Still Count Against Drive Storage
We’re hearing reports that this trick was discovered by the team over at OpenGapps a few months back and was quietly patched by Google already. In that case, applying this trick will still result in uploaded photos to apply against your Google Drive storage (ie. it doesn’t work). We haven’t confirmed this ourselves, but if/when we do we will update the above tutorial.
Click to expand...
Click to collapse
Update 4 – Google Photos Unlimited Storage Not Working, Pixel Wallpapers Still Work
I have confirmed that photos uploaded in “original quality” using this trick still count against your Drive storage. My Drive shows that I uploaded 0.2GBs of photos and videos from yesterday. This means that the trick was patched, likely when it was discovered by the people over at OpenGapps. It’s strange that this trick somehow still triggers Google Photos into showing you the original quality onboarding message, though.
Click to expand...
Click to collapse
zpower said:
Will not work!
https://www.xda-developers.com/enable-google-photos-unlimited-storage/amp/
Click to expand...
Click to collapse
Thanks for the info
Not sure where else to put this, but if you just want the wallpapers, you only need the following in the XML (which I named google_wallpapers_2017.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.feature.PIXEL_EXPERIENCE" />
</config>
This is meant for the unlimited Google Photos (now patched, xml named google_unlimited_photos.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.apps.photos.NEXUS_PRELOAD" />
<feature name="com.google.android.apps.photos.nexus_preload" />
</config>
You do not need any of this:
Code:
<!-- Enable Zero Touch Provisioning support for 2016 and newer Nexus devices. -->
<feature name="com.google.android.feature.ZERO_TOUCH" />
<!-- Allow Google unbundled tethering entitlement app in background -->
<allow-in-power-save package="com.google.android.tetheringentitlement" />
<!-- Allow ssr detector service in background -->
<allow-in-power-save package="com.google.SSRestartDetector" />
<!-- Allow ramdump uploader service in background -->
<allow-in-power-save package="com.android.ramdump" />
<!-- These are telephony components that need to run in the background -->
<allow-in-power-save package="com.qualcomm.atfwd" />
<allow-in-power-save package="com.qualcomm.embms" />
<allow-in-power-save package="com.qualcomm.qti.telephonyservice" />
<allow-in-power-save package="com.qulacomm.qcrilmsgtunnel" />
<allow-in-power-save package="com.qualcomm.qti.ims" />
<allow-in-power-save package="com.qualcomm.qti.radioconfiginterface" />
i will try it later but let me thanx, it might be the best module for me if it works
It works for me, just flashed through twrp nothing else
StaticBlaze said:
There you go
https://drive.google.com/open?id=0B35Q-_-S5yi-SENWYkNyTU1JX3M
Click to expand...
Click to collapse
Thank you!!!!!
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
chazarss said:
It works for me, just flashed through twrp nothing else
Click to expand...
Click to collapse
Read the article i post above
SpasilliumNexus said:
Not sure where else to put this, but if you just want the wallpapers, you only need the following in the XML (which I named google_wallpapers_2017.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.feature.PIXEL_EXPERIENCE" />
</config>
This is meant for the unlimited Google Photos (now patched, xml named google_unlimited_photos.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<config>
<feature name="com.google.android.apps.photos.NEXUS_PRELOAD" />
<feature name="com.google.android.apps.photos.nexus_preload" />
</config>
You do not need any of this:
Code:
<!-- Enable Zero Touch Provisioning support for 2016 and newer Nexus devices. -->
<feature name="com.google.android.feature.ZERO_TOUCH" />
<!-- Allow Google unbundled tethering entitlement app in background -->
<allow-in-power-save package="com.google.android.tetheringentitlement" />
<!-- Allow ssr detector service in background -->
<allow-in-power-save package="com.google.SSRestartDetector" />
<!-- Allow ramdump uploader service in background -->
<allow-in-power-save package="com.android.ramdump" />
<!-- These are telephony components that need to run in the background -->
<allow-in-power-save package="com.qualcomm.atfwd" />
<allow-in-power-save package="com.qualcomm.embms" />
<allow-in-power-save package="com.qualcomm.qti.telephonyservice" />
<allow-in-power-save package="com.qulacomm.qcrilmsgtunnel" />
<allow-in-power-save package="com.qualcomm.qti.ims" />
<allow-in-power-save package="com.qualcomm.qti.radioconfiginterface" />
Click to expand...
Click to collapse
Somebody should make a new thread for a "Pixel Wallpapers Enabler" module.
How to see whether the wallpapers of pixel are enabled or nor???
Sent from my Redmi Note 4 using Tapatalk
Any news about LOS 15 for Xiaomi Mi Mix2?
https://drive.google.com/file/d/1Xf-ULJcr0UptEutLxUFPDrcoTGVzUm3G/view?usp=sharing
I'm confused, what is that link?
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
Its Arasthels lineage 15.1 build, does this guy have permission to issue it?
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
I wanned to ask as well. Who merged that and who has given the shout of the link. Getting LOS15 indtalled would blow up my f...en brain right on to the ceiling for sure
---------- Post added at 07:34 PM ---------- Previous post was at 07:32 PM ----------
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
fbousk said:
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
Click to expand...
Click to collapse
Aaaah now I get it. Thank you. We'd better wait on him to say something when he feels it's ready enough.
armsar1978 said:
Any news about LOS 15 for Xiaomi Mi Mix2?
https://drive.google.com/file/d/1Xf-ULJcr0UptEutLxUFPDrcoTGVzUm3G/view?usp=sharing
Click to expand...
Click to collapse
Seriously, what's that thread ?
Is your link coming from a reliable source (in that case, make a proper OP with bugs, issues, credits, sources) ? Or did you just download a zip from github branch wich means it's a "[email protected]#!*!!#€upyourphone" ?
If it's the second case, this is really a bad joke considering people awaiting here.
If it's just a question, it's also a bad joke and not the right place to post.
Envoyé de mon MI Mix 2 en utilisant Tapatalk
yeyeoke said:
I'm confused, what is that link?
Click to expand...
Click to collapse
fbousk said:
Arasthel build close the thread please its unnoficial your not allowed to link without autorizations.
Click to expand...
Click to collapse
Aaaah now I get it. Thank you. We'd better wait on him to say something when he feels it's ready enough.
I almost got an heart attack
So, I tried and I can confirm it's legit.
Benjimaestro said:
So, I tried and I can confirm it's legit.
Click to expand...
Click to collapse
So, it boots ? No real major issue for the moment ?
Thx
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="vendor/xiaomi/chiron" name="LineageOS-chiron/android_vendor_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="device/xiaomi/chiron" name="LineageOS-chiron/android_device_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="kernel/xiaomi/msm8998" name="LineageOS-chiron/android_kernel_xiaomi_msm8998" remote="github" revision="chiron-oreo-8.1" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" />
<project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" remote="github" />
<project path="packages/lineage/livedisplay" name="LineageOS/android_hardware_lineage_livedisplay" remote="github" />
</manifest>
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Arasthel said:
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="vendor/xiaomi/chiron" name="LineageOS-chiron/android_vendor_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="device/xiaomi/chiron" name="LineageOS-chiron/android_device_xiaomi_chiron" remote="github" revision="los-15.1-verevka" />
<project path="kernel/xiaomi/msm8998" name="LineageOS-chiron/android_kernel_xiaomi_msm8998" remote="github" revision="chiron-oreo-8.1" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" />
<project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" remote="github" />
<project path="packages/lineage/livedisplay" name="LineageOS/android_hardware_lineage_livedisplay" remote="github" />
</manifest>
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Click to expand...
Click to collapse
Thank you so much !
Wahoux said:
Thank you so much !
Click to expand...
Click to collapse
Absolutely terrific. Do I need to get thru Xiaomi 7.1 firmware or can I just switch from MIUI Oreo beta. That Is my major concern. Thanks for this beauty
enzo_cz said:
Absolutely terrific. Do I need to get thru Xiaomi 7.1 firmware or can I just switch from MIUI Oreo beta. That Is my major concern. Thanks for this beauty
Click to expand...
Click to collapse
I came from Miui Oreo, and just formated data before flashing LOS, and works fine
Wahoux said:
Thank you so much !
Click to expand...
Click to collapse
Wahoux said:
I came from Miui Oreo, and just formated data before flashing LOS, and works fine
Click to expand...
Click to collapse
Thanks man, I appreciate that
Amazing timing, my Mi Mix 2 is being delivered tomorrow, i cannot wait to play!
Thank you!
Arasthel said:
Hello everyone. This build works almost fine - usual issues with low quality camera, etc., that we had on 7.1 are still there - and has been made thanks to the effort of a group of devs: @hondajohn88, @StoneTrapper, @pappschlumpf and me. I'd also like to give credit to @Verevka, NisseCool and thune-xiaobai for their awesome base for Mi 6, which helped a lot in getting this ROM working.
I didn't want to post it yet as I wanted to experiment a bit on it before, but since it's already here, I guess this is as good a place as any to share the code also - although it's already online for a while and easy to find on Github:
Sources used are in https://github.com/LineageOS-chiron/. My local manifest to build LOS 15.1 is:
Code:
After cherry picking the changes on the 'required_patches.txt' file.
Anyway, I hope you enjoy the ROM and this repos are used to build even better ones! Happy tinkering!
Click to expand...
Click to collapse
@Arasthel
Well, this is pretty good news ! But in an unconventional way. This thread is going to be spammed with questions about how to flash, which twrp, from what firmware do we need to come, dirty flash over LOS14, what's working, what's not and so on ...
Couldn't it be better that you start an official new thread and ask mods to merge this one as replies ?
Anyway, I was waiting for this. Great job Man ! Waiting for some more infos / procedure before flashing.
Envoyé de mon MI Mix 2 en utilisant Tapatalk
For flash, I'm coming from Oreo bêta Miui and have juste full wipe.
For me, the Best custom rom (Aosp) so far !!! No bug for the moment and buttery smooth !!!
Wahoux said:
So, it boots ? No real major issue for the moment ?
Thx
Click to expand...
Click to collapse
Boots very quickly. No major issues so far. Calls, SMS, mobile data, BT, camera, audio, performance are all good.
Input lag seems to be better than nougat.
For a sketchy looking alpha release it's VERY good.
Only issue is that the FP scanner vibrates if touched at any time, which causes the phone to vibrate. Just a minor annoyance.
Shuyin10 said:
For flash, I'm coming from Oreo bêta Miui and have juste full wipe.
For me, the Best custom rom (Aosp) so far !!! No bug for the moment and buttery smooth !!!
Click to expand...
Click to collapse
wow, thats encouraging! Great work to all involved. :good:
I've applied for unlock, just waiting for the sms, so by the time all that comes through this (or a proper thread) will have expanded a little.
I've missed tinkering with my phones, not done it since my htc one