I wanna tweak the build prop by adding extra lines to make the photo quality less compressed and maybe some speed optimizations.
Is this possible on a device running Intel?
I take it I just add the build prop tweaks to the end of the build prop itself?
If i learn that this is possible I may try make a ROM for the RAZR i.
Related
TwkdMod- The Rom that will speed your phone!
Tested for a week to test if it it stable.it is not my fault if this messes up your phone.
Features:
-based off of the latest cm10.1 nightly
-tweaked with different tweaks (seeder, supercharger, pimp my rom, and more!) (maybe in the next release i will include supercharger )
-fast
-stable
-light
-small
-faster 3g
-faster scrolling
-faster everything!
-better benchmarks
-debloated
Changelog:
v1
Credits:
all the developer in the this section
mods
::indie:: (helped a lot. Omega rom dev.)
salesale (NeatROM dev. a great person.)
westcrip (awesome rom which helped me learn about this.)
-people who run this
Downloads:
wup, wup!
i added the download link to the op. please let me know how it is!
what are the tweaks you added that made it faster scrolling/3g/etc?
jarjar124 said:
what are the tweaks you added that made it faster scrolling/3g/etc?
Click to expand...
Click to collapse
mostly init.d tweaks and some build.prop tweaks. build in the future will be supercharged. just try it and please let me know how it is!
does anybody download? how is it?
You need to flash gapps too I believe.
EDIT: error in zip could not install, will try again.
not install ...
Hi,
OMG!!!
I just looked into your init.d folder...
You collect lots of scripts to put in your ROM, fine, but put them all together, less good..., just my opinion. Would have had to sort out and look a bit some values, more than half are completely useless.
For the same tweak you have two, three or four times the same values in different scripts or even 2 different values in the same script...
For the same tweak you have x value in a script and y value in another one (and for some tweaks you have 2 different values in the same script!)...
At boot one erase another while a third erase yet the previous (according to the execution order at boot).
Your scripts for RAM "management" is the best example of against productivity, two scripts for zipalign, your scripts for "net speed" are also the same, etc...
30 init.d scripts running, obiously, at boot... it is not a bit much? Check the duplicates (or more) lines and tweaks, removes unnecessary scripts and makes a little cleaning...
It is not because you have 30 different scripts with multiple lines and values that is necessarily great, remove all your scripts (or keep one for the "RAM management" maybe (and still not sure ) and your ROM will runs perfectly.
Sometimes "more is the enemy of the good", here it's a good example... And don't say the user can choose or edit... probably the most (or all) people who flash this don't know the point of this or that script...They will flash the whole zip with all your scripts inside without knowing what they do... It's totally useless. People see "speed" "fast", "smooth", "performance", etc... ok GO GO GO! flashing! + placebo effect...
You'll have the same goal without the whole script , the ROM will runs perfectly without all this... bunch of scripts...
Ask some devs the usefulness of these scripts, you'll be surprised. I've already tested some of your scripts... Most do little or nothing, are not adapted to JB or needs to be reworked when we have 2 Go of RAM (the scripts for RAM "management"), or are not adapted to our phones (look at your "14enable_touchscreen", where do you find the path in our N4 ??? the path /sys/class/touch/switch/set_touchscreen does not exists... you are echoing a value wich does not exist-> totaly useless script), etc...
Just my opinion and some tips...
Keep the good works up !
Waiting for most features
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
Keep the good works up !
Waiting for most features
This was the same guy who posted a fake 4.2.2...
Sent from my Nexus 4 using Tapatalk 2
Imppy said:
This was the same guy who posted a fake 4.2.2...
Click to expand...
Click to collapse
build.prop and init.d hero :good:
You should be ashamed of yourself dude.. I really have no idea why mods are so easy on ppl like you.
I encourage new devs, honestly if you had compiled stock cm I would've congratulated you.. but if you're gonna skip the steps and just BS your way through then we'll shoot your plan full of holes.
Nobody flash this ROM it's junk..
Sent from my Nexus 4
Ok mate, I'm going to say this slow and easy.
Getting a cm10.1 base, removing apps and just collecting all init.d scripts is not the way to make a rom.
Go to guides, and read more until you know what exactly you are doing.
Or else, you'd see thousands of roms here.
Plus, changing the android version in build.prop doesn't make it Android 10.
mv_style said:
Guys dont bother downloading this
he just added like 10 different scripts which conflict
every values comes up like 5 times at least
he is banned cause of posting fake work
Click to expand...
Click to collapse
Moderator please close thread.
I want to know how to create different types of init.d scripts
Right now I need a LMK init.d script, so that I won't lose values on each reboot while using CM10.2
Shiningb said:
I want to know how to create different types of init.d scripts
Right now I need a LMK init.d script, so that I won't lose values on each reboot while using CM10.2
Click to expand...
Click to collapse
I think the best way it to search XDA. For example, I have no idea how to do it. :angel:
@Shiningb
Code:
echo '2048,3584,20736,24064,27136,30464' > /sys/module/lowmemorykiller/parameters/minfree
You can also use supercharger script to change your minfree values.
EDIT : Sorry quoted the wrong person.
So I just modify those values to:
4mb 8mb 16mb 32mb 48mb and 64mb
Which is the moderate values of OMNI, right??
I always modify my LMK values with Super Manager, these values work with cm only, using it on stock will result in super laggy performance...
If i remember right, is 48mb for CM and Omni.
Powered by CM10.2
I came across this tweak a while ago while I still had a Nexus 6P and I've used it ever since so I figured that i'd make it into a Magisk module and post it here to see if anyone else would benefit from it.
I am not the original creator of this tweak. I am unsure who is but I have linked the source of where I have found it below.
This tweak if fairly simple. All it does is add a couple of lines of code to the build.prop.
This tweak is aimed to provide a smoother experience when navigating in android. It may be a placebo effect but I definitely see a difference when this tweak is enabled.
Tested to work on Oreo on both Nexus 6P and Oneplus 5.
# FluidsTweak 2.0
- Creates a more fluid experience in android.
# Prerequisites
- Magisk v15.0 or higher
# How it works
Adds the following values in build.prop:
persist.sys.dalvik.hyperthreading=true
cpu.fps=auto
gpu.fps=auto
ro.sys.cpu.defaultfreq=auto
ro.sys.gpu.defaultfreq=auto
# Links
- [Magisk](https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
- [Support](https://forum.xda-developers.com/apps/magisk/module-nosense-tweak-t3762099)
- [Source](https://forum.xda-developers.com/nexus-6p/general/nosense-tweak-super-fluid-smooth-t3498982)
# Change Log
- v1
Initial Release
Click to expand...
Click to collapse
Currently your module does nothing. You also have to change PROPFILE to true in config.sh or it won't load the props.
Didgeridoohan said:
Currently your module does nothing. You also have to change PROPFILE to true in config.sh or it won't load the props.
Click to expand...
Click to collapse
Oops. Definitely forgot to change that to true. Re-Uploaded the file accordingly.
Anyone do further testing with this thing? Across Android versions or even closer observation on single device for actual changes made (measurable or just user experience?)
I attach the build prop from mi 5(Gemini). Which is rooted via magisk 16 and I extracted the build prop file. As I'm not a developer, but very active user. So I let you guys see the new MIUI 10 build.prop if you can do something with this. Thanks in advance.
The build.prop is just a set of values, I don't think you can "extract features" since if they are present, those are built into that specific rom, even if you put that "new" values on another rom, you won't add any extra functionality (Example is Camera 2 API, you can enable it into the MIUI but it is just disabled by default, you're not "adding a feature", just enabling it)
lukypuie said:
The build.prop is just a set of values, I don't think you can "extract features" since if they are present, those are built into that specific rom, even if you put that "new" values on another rom, you won't add any extra functionality (Example is Camera 2 API, you can enable it into the MIUI but it is just disabled by default, you're not "adding a feature", just enabling it)
Click to expand...
Click to collapse
Okay thanks, so in order to retrieve new features from that version which file do I need to access? Can you show me!
Have TeamExyKings ROM with Magisk on the build prop I want to add more volume steps. I can't find the audio section where do I paste this. I added this on the bottom of the build prop and it didn't work? "ro.config.media_vol_steps=".
https://www.**********.com/add-more-volume-levels-to-volume-slider-on-android/
R77 said:
Have TeamExyKings ROM with Magisk on the build prop I want to add more volume steps. I can't find the audio section where do I paste this. I added this on the bottom of the build prop and it didn't work? "ro.config.media_vol_steps=".
https://www.**********.com/add-more-volume-levels-to-volume-slider-on-android/
Click to expand...
Click to collapse
did you put =15 or 20 or 30?
also you can use samsung smart things to change the steps.
edit:
my doppelganger is right, its sound assistant and not smart things.
and the other thread he referred to btw is also from yourself. so the same answers would still apply.
R77 said:
Have TeamExyKings ROM with Magisk on the build prop I want to add more volume steps. I can't find the audio section where do I paste this. I added this on the bottom of the build prop and it didn't work? "ro.config.media_vol_steps=".
https://www.**********.com/add-more-volume-levels-to-volume-slider-on-android/
Click to expand...
Click to collapse
Someone else posted about this earlier in the year,
https://forum.xda-developers.com/galaxy-note-9/help/to-paste-vol-steps-build-prop-t3953139
You could try setting the value to the BP file to a number between 1-10, lower the number, the more adjustments made to the volume media step. At least that's how sound assistant describes the way it changes the volume steps.
But ultimately, you can just install sound assistant using goodlock and you will get the same effect.