Related
Hi guys, if you've tried making your own theme for the theme chooser from scratch, you'll know how ridiculously annoying it is to add every image to the concerned xml file. Well I got fed up with it and wrote a command line tool to generate the xml for you.
To use it, you put all the images that you want to add in a folder, and then run the following command (you need the Java runtime environment for your operating system) (note that your images can begin with "frameworks_res_" or other package names - the program will automatically detect most of the common package names and you can specify your own as shown below)
Code:
$java -jar XMLGenerator.jar [package_name_1] [package_name_2] [package_name_3] [etc] [/path/to/input/folder] [outputfile]
For a more detailed guide about how to set up java and use this program, see this.
Suppose you have a folder "myDir" with 3 images: com_nhnt11_image1.png, com_nhnt22_image2.png, and frameworks_res_image3.png.
Then run
Code:
$java -jar XMLGenerator.jar com_nhnt11 com_nhnt22 myDir output.xml
The output of the program would be a file "output.xml" containing this:
Code:
<item name="drawable/image1">@drawable/com_nhnt11_image1</item>
<item name="drawable/image2">@drawable/com_nhnt22_image2</item>
<item name="drawable/image3">@drawable/frameworks_res_image3</item>
Then you can copy and paste this to whichever XML you need.
Enjoy!
Here is a list of package names that are automatically detected
This is very helpful !!
Sent from my Optimus 2X
Much much love for this! Thanks man!
This will save me a lot of time..Thank you
Awesome, thanks.
thanks man!
I've been searching and I have the java sdk installed but is there a web page someone can point me to that can help me in what I need to run that command on windows?
tia
MrDSL said:
I've been searching and I have the java sdk installed but is there a web page someone can point me to that can help me in what I need to run that command on windows?
tia
Click to expand...
Click to collapse
Command prompt...
Sent from my Blade using XDA App
hehe i did actually figure that..i must have something wrong cause even after installing java sdk when i enter that command it errors out..ill look some more..
MrDSL said:
hehe i did actually figure that..i must have something wrong cause even after installing java sdk when i enter that command it errors out..ill look some more..
Click to expand...
Click to collapse
You probably havent set your path properly, look up stuff about putting Java in your path (environment variables)
Sent from my Blade using XDA App
This fixed me up, Might want to add to OP in case someone else has the issue! http://www.java.com/en/download/help/path.xml
I got it to work but had to change the command to:
java -jar XMLGenerator.jar drawable-hdpi/ Browser.xml
Click to expand...
Click to collapse
What it created:
<item name="drawable/com_android_browser_app_web_browser_sm">@drawable/com_android_browser_app_web_browser_sm</item>
<item name="drawable/com_android_browser_arcs">@drawable/com_android_browser_arcs</item>
<item name="drawable/com_android_browser_browser_thumbnail">@drawable/com_android_browser_browser_thumbnail</item>
<item name="drawable/com_android_browser_btn_close_window">@drawable/com_android_browser_btn_close_window</item>
<item name="drawable/com_android_browser_dialog_divider_horizontal_light">@drawable/com_android_browser_dialog_divider_horizontal_light</item>
<item name="drawable/com_android_browser_fav_icn_background">@drawable/com_android_browser_fav_icn_background</item>
Click to expand...
Click to collapse
I'm runnign Windows 7
You can use .txt for the output file too! Your choice!!!!
This is great Thanks again!!!!
djdarkknight96 said:
I got it to work but had to change the command to:
What it created:
I'm runnign Windows 7
You can use .txt for the output file too! Your choice!!!!
This is great Thanks again!!!!
Click to expand...
Click to collapse
Hmm, I should really add a feature to omit the com_android_browser part in the item name... I'll think about how best to implement it and update.
Sent from my Blade using XDA App
nhnt11 said:
Hmm, I should really add a feature to omit the com_android_browser part in the item name... I'll think about how best to implement it and update.
Sent from my Blade using XDA App
Click to expand...
Click to collapse
AH, I didn't even notice that:
Template:
<item name="drawable/btn_default_pressed">@drawable/frameworks_res_btn_default_pressed</item>
Click to expand...
Click to collapse
Script:
<item name="drawable/frameworks_res_btn_default_pressed">@drawable/frameworks_res_btn_default_pressed</item>
Click to expand...
Click to collapse
I guess it won't work till you fix it? well I rather hit Find "frameworks_res_" and press delete then type and copy paste!!!! Still better!!! Thanks for making life easier!!!
I have an Idea, can you have it use the original folder from the app before we rename it on the
<item name="drawable/frameworks_res_btn_check_on_disable_focused">
Click to expand...
Click to collapse
area anad then the folder with the files renamed for the
@drawable/frameworks_res_btn_default_pressed</item>
Click to expand...
Click to collapse
???
I had the same idea, but that has some other complications... Right now I have 3 possible ways to implement this, and will update soon when I figure out which is best.
nhnt11 said:
I had the same idea, but that has some other complications... Right now I have 3 possible ways to implement this, and will update soon when I figure out which is best.
Click to expand...
Click to collapse
Saweet! I'll wait cause I'm lazy that way! Hehe
DarkGingered CM7 G2x sent this with the DarkXDA app!
OK, here's how I've done it - the program will automatically do it for common package names (it does it for all the ones that Androidian uses). However, you can specify additional package names for it to replace. Here's the new syntax -
$java -jar <packagename1> <packagename2> <etc> <input dir> <output file>
Example:
$java -jar com_upwardspiral_wallpapers com_nhnt11_dummyapp myDir output.xml
Here's the list of the package names it automatically does:
Code:
"frameworks_res_",
"com_android_systemui_",
"com_android_browser_",
"com_android_calculator2_",
"com_android_calendar_",
"com_android_camera_",
"com_android_contacts_",
"com_android_deskclock_",
"com_android_email_",
"com_android_fm_",
"com_android_inputmethod_latin_",
"com_android_launcher_",
"com_android_mms_",
"com_android_music_",
"com_android_phone_",
"com_android_providers_calendar_",
"com_android_providers_downloads_ui_",
"com_android_quicksearchbox_",
"com_android_settings_",
"com_android_wallpaper_",
"com_cooliris_media_",
"com_google_android_apps_genie_geniewidget_",
"com_google_android_carhome_",
"com_google_android_gm_",
"com_google_android_googlequicksearchbox_",
"com_google_android_talk_",
"net_cactii_flash2_"
Let me know if I'm missing anything.
nhnt11 said:
OK, here's how I've done it - the program will automatically do it for common package names (it does it for all the ones that Androidian uses). However, you can specify additional package names for it to replace. Here's the new syntax -
$java -jar <packagename1> <packagename2> <etc> <input dir> <output file>
Example:
$java -jar com_upwardspiral_wallpapers com_nhnt11_dummyapp myDir output.xml
Here's the list of the package names it automatically does:
Code:
"android_",
"frameworks_res_",
"com_android_systemui_",
"com_android_browser_",
"com_android_calendar_",
"com_android_camera_",
"com_android_contacts_",
"com_android_deskclock_",
"com_android_email_",
"com_android_inputmethod_latin_",
"com_android_launcher_",
"com_android_mms_",
"com_android_music_",
"com_android_phone_",
"com_android_providers_calendar_",
"com_android_providers_downloads_ui_",
"com_android_quicksearchbox_",
"com_android_settings_",
"com_android_wallpaper_",
"com_cooliris_media_",
"com_google_android_apps_genie_geniewidget_",
"com_google_android_carhome_",
"com_google_android_gm_",
"com_google_android_googlequicksearchbox_",
"com_google_android_talk_",
"net_cactii_flash2_"
Let me know if I'm missing anything.
Click to expand...
Click to collapse
Damn, that was fast! I'm diving in to try it out! Your awesome!
DarkGingered CM7 G2x sent this with the DarkXDA app!
djdarkknight96 said:
Damn, that was fast! I'm diving in to try it out! Your awesome!
DarkGingered CM7 G2x sent this with the DarkXDA app!
Click to expand...
Click to collapse
Test this please, I would myself but I have nothing to test it on
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)
I installed an other device rom just that this command does not work even though it is written
<CscFeature_Launcher_EnableViewByAlphabetAsDefault >true</CscFeature_Launcher_EnableViewByAlphabetAsDefault>
pranto said:
I installed an other device rom just that this command does not work even though it is written
<CscFeature_Launcher_EnableViewByAlphabetAsDefault >true</CscFeature_Launcher_EnableViewByAlphabetAsDefault>
Click to expand...
Click to collapse
Seriously? Who uses the stock launcher.... Just nova launcher and you're done.
Sent from my Blackberry Torch
if I want to remain the current one does not stock that command where to be copied
Brava27 said:
Seriously? Who uses the stock launcher.... Just nova launcher and you're done.
Sent from my Blackberry Torch
Click to expand...
Click to collapse
ONE feature nova doesn't have. pin an action note in homescreen.
pranto said:
I installed an other device rom just that this command does not work even though it is written
<CscFeature_Launcher_EnableViewByAlphabetAsDefault >true</CscFeature_Launcher_EnableViewByAlphabetAsDefault>
Click to expand...
Click to collapse
I've been using this entry since I got my Note5. I'm using a stock rom.
I added a feature.xml file in system/csc with that command and it puts all apps alphabetically in the drawer.
possible that I can not make it work in this command others.xml
Notes 5 a-z automatic AppDrawer
Yeah I guess it might not work with others.xml
Just create feature.xml
how do you create this file and then write only in that row.
This is how mine looks like. Think I copied it over from another model.
<?xml version='1.0' encoding='UTF-8' ?>
<SamsungMobileFeature>
<Country></Country>
<CountryISO></CountryISO>
<SalesCode></SalesCode>
<FeatureSet>
<CscFeature_Launcher_EnableViewByAlphabetAsDefault>TRUE</CscFeature_Launcher_EnableViewByAlphabetAsDefault>
</FeatureSet>
</SamsungMobileFeature>
Hope it will work for you as well.
Alta1r said:
This is how mine looks like. Think I copied it over from another model.
<?xml version='1.0' encoding='UTF-8' ?>
<SamsungMobileFeature>
<Country></Country>
<CountryISO></CountryISO>
<SalesCode></SalesCode>
<FeatureSet>
<CscFeature_Launcher_EnableViewByAlphabetAsDefault>TRUE</CscFeature_Launcher_EnableViewByAlphabetAsDefault>
</FeatureSet>
</SamsungMobileFeature>
Hope it will work for you as well.
Click to expand...
Click to collapse
features within the file I added the part that you indicated to me but the same does not work.
The file name should be 'feature.xml' not 'features.xml'.
If that is not the problem, then I don't know it either.
Do note that when it's activated you don't have the A-Z option anymore in the app drawer; it will automatically put all your apps alphabetically. Also when you delete or add an app it will do that automatically.
Unfortunately it does not work
Friends possible that having installed a ROM for s6 and making all the changes I had no problem except with the automatic alignment of applications. csc is written in the words that should do what I requested. but nothing. can I do something missing.
no one can give me an explanation
news...news.....news.....thank you..thank you..thank you
328 <project path="frameworks/opt/telephony" name="CyanogenMod/android_frameworks_opt_telephony" groups="pdk" />
312 <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" groups="pdk" /
178 <project path="external/libexif" name="platform/external/libexif" groups="pdk-cw-fs,pdk-fs" remote="aosp" />
what is this? More "advanced" users will know
XTutorials said:
328 <project path="frameworks/opt/telephony" name="CyanogenMod/android_frameworks_opt_telephony" groups="pdk" />
312 <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" groups="pdk" /
178 <project path="external/libexif" name="platform/external/libexif" groups="pdk-cw-fs,pdk-fs" remote="aosp" />
what is this? More "advanced" users will know
Click to expand...
Click to collapse
Are you trying to build LineageOS/Cyanogenmod ? I guess you have errors where projects are conflicting.
For me, Problem was caused because XePeleatos external/libexif and 2 others you mentioned had same path= as lineageos's manifest. It helped when i removed those 3 lines from .repo/manifest.xml
Audriuskins said:
Are you trying to build LineageOS/Cyanogenmod ? I guess you have errors where projects are conflicting.
Click to expand...
Click to collapse
Yes, I am in state of building a custom rom, had some "same path" error at the .repo/manifest.xml file
Vika__ said:
For me, Problem was caused because XePeleatos external/libexif and 2 others you mentioned had same path= as lineageos's manifest. It helped when i removed those 3 lines from .repo/manifest.xml
Click to expand...
Click to collapse
lol, had same isssue, have you build a custom rom?
XTutorials said:
lol, had same isssue, have you build a custom rom?
Click to expand...
Click to collapse
I build just for my own fun
Vika__ said:
I build just for my own fun
Click to expand...
Click to collapse
And you succeded?
XTutorials said:
And you succeded?
Click to expand...
Click to collapse
I left lineage 14 since i trust its development on people who know whats doing and i moved to lineage 13. First build atm going and i don't think it's gonna boot
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