Hi,
Previously, I would edit the build prop to change the DPI on my Nexus however with CM12 nightlies, it is annoying to have to edit it every day. I noticed in CyanDelta that there's an option to flash a zip after updating and I'm wondering whether or not there is (or if I could create) a zip that lowers the DPI.
Thanks!
p3ntyne said:
Hi,
Previously, I would edit the build prop to change the DPI on my Nexus however with CM12 nightlies, it is annoying to have to edit it every day. I noticed in CyanDelta that there's an option to flash a zip after updating and I'm wondering whether or not there is (or if I could create) a zip that lowers the DPI.
Thanks!
Click to expand...
Click to collapse
Extract the zip and edit build_prop.sh to your liking, the one default in this zip changes 480 to 470.
You could probably also use a backuptool/addon.d script instead of flashing a zip if your ROM supports it.
Edit: Reuploaded, forgot to save
Lethargy said:
Extract the zip and edit build_prop.sh to your liking, the one default in this zip changes 480 to 470.
You could probably also use a backuptool/addon.d script instead of flashing a zip if your ROM supports it.
Edit: Reuploaded, forgot to save
Click to expand...
Click to collapse
Thanks! I've just edited it to my preferred DPI and I'll see if it works with tomorrow's nightly! I'm just wondering what a backuptool/addon.d script is? Would it be easier to use even though the zip will automatically be flashed with the ROM update (through CyanDelta)?
EDIT: I just found an addon.d folder in the System directory. Can I just leave the '.sh' file in there?
p3ntyne said:
Thanks! I've just edited it to my preferred DPI and I'll see if it works with tomorrow's nightly! I'm just wondering what a backuptool/addon.d script is? Would it be easier to use even though the zip will automatically be flashed with the ROM update (through CyanDelta)?
EDIT: I just found an addon.d folder in the System directory. Can I just leave the '.sh' file in there?
Click to expand...
Click to collapse
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Lethargy said:
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Click to expand...
Click to collapse
I've just put the .sh file in the addon.d folder and I'll see if it works tomorrow.
Thanks for your help!
Lethargy said:
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Click to expand...
Click to collapse
I just received today's update and unfortunately the addon.d method didn't work. Following that, I tried flashing the zip but TWRP says, 'E:Error executing updater binary in zip '/sdcard/Download/ro.sf.lcd_density.zip'
Do you know what this might be?
p3ntyne said:
I just received today's update and unfortunately the addon.d method didn't work. Following that, I tried flashing the zip but TWRP says, 'E:Error executing updater binary in zip '/sdcard/Download/ro.sf.lcd_density.zip'
Do you know what this might be?
Click to expand...
Click to collapse
Yeah redownloaded and noticed I missed a line.
Lethargy said:
Yeah redownloaded and noticed I missed a line.
Click to expand...
Click to collapse
Thanks! Before I save it, I just want to make sure it is the second number that I should change to my preferred dpi (it says 480 and 470).
p3ntyne said:
Thanks! Before I save it, I just want to make sure it is the second number that I should change to my preferred dpi (it says 480 and 470).
Click to expand...
Click to collapse
Yep
Lethargy said:
Yep
Click to expand...
Click to collapse
Awesome, thanks! Once again, I'll test it out tomorrow.
Related
This can make filenames with special characters to be shown correctly when using cifs.
The module was extracted from the kernel in this post.
The script I wrote would load modules by insmod. You can select which modules to load on boot by editing the config file located at /data/init.insmod.conf.
The config file will be re-generated after delete / data wipe.
The attached file is also hosted here
Hi man
I traid to boot this on a CM6.1 RC2 but it give an error in the load what I have to do to boot it
Czaro said:
Hi man
I traid to boot this on a CM6.1 RC2 but it give an error in the load what I have to do to boot it
Click to expand...
Click to collapse
I cant understand you completely, but please try the new zip I've just uploaded.
chrisanddarla
I installed cm6 and lost the market. Can anyone tell me if it is possible to get it back and if so how? Thanks
chrisanddarla said:
I installed cm6 and lost the market. Can anyone tell me if it is possible to get it back and if so how? Thanks
Click to expand...
Click to collapse
With cm6, you must also install the GAPPS add on for Google apps.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-20101020-signed.zip
I hate having to copy the apk to system/app, changing the permissions, and rebooting the phone every time I update with nightly which is like every other day
You could add it to the ROM before you flash it. Not sure this would save you any time though.
Sent from my SAMSUNG-SGH-I727
yingjai said:
I hate having to copy the apk to system/app, changing the permissions, and rebooting the phone every time I update with nightly which is like every other day
Click to expand...
Click to collapse
I doubt that my friend CM roms are pretty versatile but the base there content on pure performance and awesome mods I doubt they will ever add this permanently. You can try make it a flash zip so when you update the ROM you can flash TWM right after
Sent from my SAMSUNG-SGH-I727 using xda premium
yingjai said:
I hate having to copy the apk to system/app, changing the permissions, and rebooting the phone every time I update with nightly which is like every other day
Click to expand...
Click to collapse
Why would you want that anyway?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yes, you'll need to create a flashable zip that implements the addon.d scripting supported in CM builds.
Look here for some examples of how it's done.
Take one of the zips, and open it up (7-zip is my preference), drop your apk into \system\app (delete whatever other apks are in that folder).
Next, rename the script in \system\addon.d to something like 94-twm.sh and then edit the section under list_files() so that it looks like this:
Code:
list_files() {
cat <<EOF
app/nameofyourtwmapk.apk
EOF
}
Obivously replace nameofyourtwmapk.apk with the real name of the apk you're flashing.
Now flash your zip in CWM. This will install your apk in /system/app and the script in /system/addon.d so that every time a new CM rom is flashed the install script will backup and restore your apk.
This is exactly how CM handles backing up and restoring the gapps during a CM flash.
Great explanation schmitty! I knew about the addon.d restore for gapps, but wouldn't've had a clue on how to include any personal additions. Thanks!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
cschmitt said:
Yes, you'll need to create a flashable zip that implements the addon.d scripting supported in CM builds.
Look here for some examples of how it's done.
Take one of the zips, and open it up (7-zip is my preference), drop your apk into \system\app (delete whatever other apks are in that folder).
Next, rename the script in \system\addon.d to something like 94-twm.sh and then edit the section under list_files() so that it looks like this:
Code:
list_files() {
cat <<EOF
app/nameofyourtwmapk.apk
EOF
}
Obivously replace nameofyourtwmapk.apk with the real name of the apk you're flashing.
Now flash your zip in CWM. This will install your apk in /system/app and the script in /system/addon.d so that every time a new CM rom is flashed the install script will backup and restore your apk.
This is exactly how CM handles backing up and restoring the gapps during a CM flash.
Click to expand...
Click to collapse
I followed your instructions exactly and it didn't work. Do I need to edit the manifest or something also? I used the Nova Launcher 1.3.1 zip.
yingjai said:
I followed your instructions exactly and it didn't work. Do I need to edit the manifest or something also? I used the Nova Launcher 1.3.1 zip.
Click to expand...
Click to collapse
What didn't work? Any error in CWM? Need details in order to help. Maybe post the zip you built so we can have a look.
After several tries, I've finally got it to work.
Posting here for other people who want it.
thanks
Thanks man! I really like this stock task manager better also... just like its simple features, works quickly, clears memory, uninstaller, etc... so, thanks for this! Nice to be able to add it to my roms...
~Dan~
Some people aren't sure how to create a flash-able zip. So here is a template zip file.
If you want to edit the updater-script (what shows up in recovery when you choose the .zip to flash. It it's in META-INF\com\google\android\updater-script, edit with notepad++, and edit in between the parentheses ui_print("Put Your Text Here");
add your boot.img to the spot where there is already a boot.img and replace it with yours
Most Kernels require different system/libs/modules
I added a spot for you to add these as well.
https://androidfilehost.com/?fid=313042859668275619
No need to seek permission for this or give any credits. Just something for those who need it.
Saved.
andybones said:
Some people aren't sure how to create a flash-able zip. So here is a template zip file.
If you want to edit the updater-script (what shows up in recovery when you choose the .zip to flash. It it's in META-INF\com\google\android\updater-script, edit with notepad++, and edit in between the parentheses ui_print("Put Your Text Here");
add your boot.img to the spot where there is already a boot.img and replace it with yours
Most Kernels require different system/libs/modules
I added a spot for you to add these as well.
http://d-h.st/MfA
No need to seek permission for this or give any credits. Just something for those who need it.
Click to expand...
Click to collapse
Would this work if we want to make a flashable zip for certain files? Say frameworks, systemui, etc?
droidkevlar said:
Would this work if we want to make a flashable zip for certain files? Say frameworks, systemui, etc?
Click to expand...
Click to collapse
Yes it should work
Sent from my Insanely powered M8 using Tapatalk
holla420 said:
Yes it should work
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
So I would just need to update the updater-script, correct? And remove the boot.img file?
droidkevlar said:
So I would just need to update the updater-script, correct? And remove the boot.img file?
Click to expand...
Click to collapse
No.. Use this thread for that..
http://forum.xda-developers.com/showthread.php?t=2745680
Could you please reupload this file?
Thanks.
revflash said:
Could you please reupload this file?
Thanks.
Click to expand...
Click to collapse
link updated.
Late reply, sorry -- just seen today.
I made a boot animation, and tried installing it using various methods. First I copied the bootanimation.zip to /system/media. Phone booted fine, but it only showed the Google boot logo (not my animation). I also tried copying it to /data/local, same results. I tried making a flashable zip, but when I tried flashing it in CWM it just said "Installing update… Installation aborted." I have also tried flashing the same animation on the Moto G with same methods, and same results.
What am I doing wrong?
Did you make the zip without compression? It can't be compressed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did you make the zip without compression? It can't be compressed.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I used the Keka app for Mac and set it to Store (no compression). I might try some other compression apps.
clavierkid said:
I tried making a flashable zip, but when I tried flashing it in CWM it just said "Installing update… Installation aborted."
Click to expand...
Click to collapse
I guess you didn't sign your zip file.
I always use the same structure for my boot animation so here are the differences with yours. Some of them don't matter though.
1. Into your zip, you have a folder bootanimation => you should directly have your partX folders and desc.txt
2. What is .DS_Store?
3. Naming:
part0 => 000.png / 001.png / 002.png....
part1 => 003.png / 004.png / 005.png....
4. desc.txt:
Code:
1080 1920 15
p 1 5 android
p 0 0 part1
Replace "android" by "part0"
BTW the second number is the delay between loops (in milliseconds) so "5" seems useless.
Primokorn said:
I guess you didn't sign your zip file.
I always use the same structure for my boot animation so here are the differences with yours. Some of them don't matter though.
Click to expand...
Click to collapse
Thanks for the feedback! I tried changing the structure of the zip file as you suggested, same results. DS_Store is an annoying hidden file Mac OS makes, I deleted it. I also changed the desc.txt. Still not working.
Would signing the zip make a difference?
clavierkid said:
Thanks for the feedback! I tried changing the structure of the zip file as you suggested, same results. DS_Store is an annoying hidden file Mac OS makes, I deleted it. I also changed the desc.txt. Still not working.
Would signing the zip make a difference?
Click to expand...
Click to collapse
The bootanimation.zip shouldn't be signed. Upload your new version and I'll have a look on my phone.
Primokorn said:
The bootanimation.zip shouldn't be signed. Upload your new version and I'll have a look on my phone.
Click to expand...
Click to collapse
Here it is
clavierkid said:
Here it is
Click to expand...
Click to collapse
Try this: https://www.dropbox.com/s/df7v0u1niexpvcd/bootanimation.zip?dl=1
It works now on my phone. I removed several png files (for testing purpose) because I resized them to 1080x1920.
I also changed desc.txt and removed DS_store file.
Copy this zip file into /system/media/ with 0644. Reboot.
Primokorn said:
Try this: https://www.dropbox.com/s/df7v0u1niexpvcd/bootanimation.zip?dl=1
It works now on my phone. I removed several png files (for testing purpose) because I resized them to 1080x1920.
I also changed desc.txt and removed DS_store file.
Copy this zip file into /system/media/ with 0644. Reboot.
Click to expand...
Click to collapse
It works! Thank you!
This zip is a pure stock firmware with no extra stuff added! Only the boot.img is bumped and the modem is hybrid(v30 + v20 to make bump compatible).
Features:
Added from the stock v30 base:
system.img
modem.img - hybrid one(contains v30 + v20 stuff)
boot.img - bumped
rpm.img
tz.img
cust.img
selinux is permissive
How to install:
Wipe system, data, cache, dalvik cache for a clean install.
Flash D850_V30_Bumped.zip
For root:
SuperSU - flash BETA-SuperSU-v2.52.zip.(No SafetyNet pass).
MagiskSU - get it from the official magisk thread.(Passes SafetyNet).
Reboot
Downloads:
v30A [2017-02-09] - Click here to download (MD5: 95ff1dd2e38439e2dea3c46f4a49c3ee)
BETA-SuperSU-v2.52.zip - Click here to download
SharpeningMOD fix - Click here for thread
Mirrors are welcome because this is most probably the first and the last firmware that will come to the D850. It will be good if someone share a picture of about-phone that shows the software info
Modems:
v30A + v20A - Click here to download
v20A - Click here to download
Q&A:
What's different in the hybrid modem?
Check this post - click here
How is this different to other MM stock rom's out there?
This not an extracted system.img rom like others. It contains extracted .kdz files and just flashes them. Permissive selinux is included, alongsite 3 build.prop changes to make for better compatibility(this is an D850PR kdz). Nothing else, no tweaks, no other stuff added.
What does [2017-02-09] mean?
That's build date of the kdz(can be checked in build.prop, kernel build date...)
These are the build.prop changes:
Code:
ro.build.target_country=[B]COM[/B]/ro.build.target_country=[B]US[/B]
telephony.lteOnCdmaDevice=[B]0[/B]/telephony.lteOnCdmaDevice=[B]1[/B]
ro.product.locale=en-[B]GB[/B]/ro.product.locale=en-[B]US[/B]
Thanks man! Great work!
Noob Question: I am on Stock KitKat ROM with KitKat Modem. To upgrade into this, do I also need to flash the hybrid modems as well, then flash this ROM? Or the MM ROM already has the modem on it, and do I just need to flash the ROM?
souler456 said:
Noob Question: I am on Stock KitKat ROM with KitKat Modem. To upgrade into this, do I also need to flash the hybrid modems as well, then flash this ROM? Or the MM ROM already has the modem on it, and do I just need to flash the ROM?
Click to expand...
Click to collapse
The modem is already included in the full zip. I don't think you will have any problem. Most partitions from kdz are already included, so it should work fine. If not you must update to LP but that's only if this doesn't work.
Dear OP,
Please add Theme engine support to Stock Launcher, rest is awesome.
hemal_4404 said:
Dear OP,
Please add Theme engine support to Stock Launcher, rest is awesome.
Click to expand...
Click to collapse
Hello. It's strange because it's there but I guess just disabled. LGHome is the same like other variants. Do you use xposed? With xposed there may be an easy fix but without it need to investigate little more.
I am not using Xposed, and kept rom completely stock.
But Theme engine is not available.
hemal_4404 said:
I am not using Xposed, and kept rom completely stock.
But Theme engine is not available.
Click to expand...
Click to collapse
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
MESA said:
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
Click to expand...
Click to collapse
I think something is wrong with attached file as it's size is only 160 KB.
hemal_4404 said:
I think something is wrong with attached file as it's size is only 160 KB.
Click to expand...
Click to collapse
No it's not. Try it.
MESA said:
No it's not. Try it.
Click to expand...
Click to collapse
Tried but makes no difference.
MESA said:
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
Click to expand...
Click to collapse
You must make changes in etc/permissions...
Ducatuca said:
You must make changes in etc/permissions...
Click to expand...
Click to collapse
Done but no changes.
hemal_4404 said:
Done but no changes.
Click to expand...
Click to collapse
What do you mean? What did you change in etc/permissions?
MESA said:
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
Click to expand...
Click to collapse
I followed exactly same as mentioned.
hemal_4404 said:
I followed exactly same as mentioned.
Click to expand...
Click to collapse
Yes, but I wrote to @MESA to make changes in file which is in etc/permissions...
Ducatuca said:
Yes, but I wrote to @MESA to make changes in file which is in etc/permissions...
Click to expand...
Click to collapse
What file are you talking about? If you have any idea about the fix share it here.
[/COLOR]
MESA said:
What file are you talking about? If you have any idea about the fix share it here.
Click to expand...
Click to collapse
Try to download my rom which is the same for d850. And check the permissions folder. U will find the difference in size. I can't remember which exact file is for theme (it can be com.lge.permissions.xml but i'm not 100% sure)...
Ducatuca said:
You must make changes in etc/permissions...
Click to expand...
Click to collapse
Waiting for fix.
Ducatuca said:
[/COLOR]
Try to download my rom which is the same for d850. And check the permissions folder. U will find the difference in size. I can't remember which exact file is for theme (it can be com.lge.permissions.xml but i'm not 100% sure)...
Click to expand...
Click to collapse
All files from that folder are the same.
Do you use d850 system from kdz? Because all apk files are different.