So I was reading on OC and I changed the AWAKE_MAX_FREQ="AUTO" line from AUTO to 1728000 but now that I wanna go back it says error file won't save.
I noticed there's this file underneath init.post_boot.sh and it's called init.post_boot.sh.bak I don't remember seeing that there, or if it was, what did I do wrong?
are you on mean ROM 3.9?
dude just add me on gTalk real quick if you are on your comp... we'll make this easy...
---------- Post added at 03:43 AM ---------- Previous post was at 03:16 AM ----------
[/COLOR]didn't see you online...
i have to go to bed so i will give you a really quick rundown of what you need to do.
first of all, the .bak file you see is a backup of the previously edited version. delete it. then set permissions for the new file you just edited. you will have to do this every time you edit a system file with root ex... i assume thats what you are using...
second..
i assume you are on zigs or chad's kernel, since you are clocking it that high...
if that is the case... here is what you need to know:
mikey's init.post_boot.sh file in 3.9 has a LOT of text in it that is simply just information for you to read so you have an idea of what you are doing....
if you open the file, you will be at the top, and you will read from top to bottom:
#!system/bin/sh (this is at the very top)...
then you will see a bunch of text wrapped in #### symbols.
example:
#####user configurable section#####################
####################################
# Undervolting only works with anthrax kernels####################
**** like that...
anyways, you scroll down a little more and you see this... which is your executable scripts that are modifiable to you, the user.
you'll see this line
# kernel Tweaks
after that, is where you want to do your editing...
the part right above that where you see this:
AWAKE_MAX_FREQ="AUTO"
AWAKE_MIN_FREQ="486000"
(one for two phase)
(then one for your governor)
and then the ones for sleep settings...
you do not want to edit these... these are just references for the script below, which is what actually is executing and changing things...
scroll down more...
you will see this:
fi
else
AWAKE_UPTHRESH="60"
AWAKE_DOWNDIFF="35"
SLEEP_UPTHRESH="80"
SLEEP_DOWNDIFF="50"
if [ $AWAKE_MAX_FREQ = "AUTO" ]; then
AWAKE_MAX_FREQ="1512000" <===this is the line you edit to change your governor max frequency.. punch whatever value you want, then save and exit, delete .bak file, make sure permissions are good to go, reboot.
if you are using root ex, you can also just select the file (tap it once) and a window will come up telling you that it is an executable file and if you would like to execute it. i always do this to make sure i didn't mess something up...
after you execute the init.post_boot.sh file, navigate with your root ex app, or whatever app you are using... to this directory...
/sys/devices/system/cpu/cpu0/cpufreq/(whatever governor you are using)/scaling_max_frequency
long press on the scaling_max_frequency file, and select "view as text"... your new value will be displayed there. check the directory for cpu1 as well. same file path, with the exception to cpu1
hope that helped. good luck
cobraboy85 said:
are you on mean ROM 3.9?
dude just add me on gTalk real quick if you are on your comp... we'll make this easy...
---------- Post added at 03:43 AM ---------- Previous post was at 03:16 AM ----------
[/COLOR]didn't see you online...
i have to go to bed so i will give you a really quick rundown of what you need to do.
first of all, the .bak file you see is a backup of the previously edited version. delete it. then set permissions for the new file you just edited. you will have to do this every time you edit a system file with root ex... i assume thats what you are using...
second..
i assume you are on zigs or chad's kernel, since you are clocking it that high...
if that is the case... here is what you need to know:
mikey's init.post_boot.sh file in 3.9 has a LOT of text in it that is simply just information for you to read so you have an idea of what you are doing....
if you open the file, you will be at the top, and you will read from top to bottom:
#!system/bin/sh (this is at the very top)...
then you will see a bunch of text wrapped in #### symbols.
example:
#####user configurable section#####################
####################################
# Undervolting only works with anthrax kernels####################
**** like that...
anyways, you scroll down a little more and you see this... which is your executable scripts that are modifiable to you, the user.
you'll see this line
# kernel Tweaks
after that, is where you want to do your editing...
the part right above that where you see this:
AWAKE_MAX_FREQ="AUTO"
AWAKE_MIN_FREQ="486000"
(one for two phase)
(then one for your governor)
and then the ones for sleep settings...
you do not want to edit these... these are just references for the script below, which is what actually is executing and changing things...
scroll down more...
you will see this:
fi
else
AWAKE_UPTHRESH="60"
AWAKE_DOWNDIFF="35"
SLEEP_UPTHRESH="80"
SLEEP_DOWNDIFF="50"
if [ $AWAKE_MAX_FREQ = "AUTO" ]; then
AWAKE_MAX_FREQ="1512000" <===this is the line you edit to change your governor max frequency.. punch whatever value you want, then save and exit, delete .bak file, make sure permissions are good to go, reboot.
if you are using root ex, you can also just select the file (tap it once) and a window will come up telling you that it is an executable file and if you would like to execute it. i always do this to make sure i didn't mess something up...
after you execute the init.post_boot.sh file, navigate with your root ex app, or whatever app you are using... to this directory...
/sys/devices/system/cpu/cpu0/cpufreq/(whatever governor you are using)/scaling_max_frequency
long press on the scaling_max_frequency file, and select "view as text"... your new value will be displayed there. check the directory for cpu1 as well. same file path, with the exception to cpu1
hope that helped. good luck
Click to expand...
Click to collapse
Nice post. Good to see people on xda still helping out the fellow user.
Sent from my PG86100 using xda premium
I tried to put them back to AUTO how it was before but it won't save it says error and that it won't save
EDIT:
Idk if this mattered but I clicked mount /system as writable and that saved it, and got rid of the .bak file
using root ex?
infEcted
marioca said:
I tried to put them back to AUTO how it was before but it won't save it says error and that it won't save
EDIT:
Idk if this mattered but I clicked mount /system as writable and that saved it, and got rid of the .bak file
Click to expand...
Click to collapse
This was the solution to the problem.....
It wouldn't allow you to save it the first go around because you didn't give the system permission to save it... When you mounted the system as writable that allows you to save it to the "system"
Sent from my PG86100 using Tapatalk
How come the first time I changed it I didnt have to do it
cobraboy85 said:
are you on mean ROM 3.9?
dude just add me on gTalk real quick if you are on your comp... we'll make this easy...
---------- Post added at 03:43 AM ---------- Previous post was at 03:16 AM ----------
[/COLOR]didn't see you online...
i have to go to bed so i will give you a really quick rundown of what you need to do.
first of all, the .bak file you see is a backup of the previously edited version. delete it. then set permissions for the new file you just edited. you will have to do this every time you edit a system file with root ex... i assume thats what you are using...
second..
i assume you are on zigs or chad's kernel, since you are clocking it that high...
if that is the case... here is what you need to know:
mikey's init.post_boot.sh file in 3.9 has a LOT of text in it that is simply just information for you to read so you have an idea of what you are doing....
if you open the file, you will be at the top, and you will read from top to bottom:
#!system/bin/sh (this is at the very top)...
then you will see a bunch of text wrapped in #### symbols.
example:
#####user configurable section#####################
####################################
# Undervolting only works with anthrax kernels####################
**** like that...
anyways, you scroll down a little more and you see this... which is your executable scripts that are modifiable to you, the user.
you'll see this line
# kernel Tweaks
after that, is where you want to do your editing...
the part right above that where you see this:
AWAKE_MAX_FREQ="AUTO"
AWAKE_MIN_FREQ="486000"
(one for two phase)
(then one for your governor)
and then the ones for sleep settings...
you do not want to edit these... these are just references for the script below, which is what actually is executing and changing things...
scroll down more...
you will see this:
fi
else
AWAKE_UPTHRESH="60"
AWAKE_DOWNDIFF="35"
SLEEP_UPTHRESH="80"
SLEEP_DOWNDIFF="50"
if [ $AWAKE_MAX_FREQ = "AUTO" ]; then
AWAKE_MAX_FREQ="1512000" <===this is the line you edit to change your governor max frequency.. punch whatever value you want, then save and exit, delete .bak file, make sure permissions are good to go, reboot.
if you are using root ex, you can also just select the file (tap it once) and a window will come up telling you that it is an executable file and if you would like to execute it. i always do this to make sure i didn't mess something up...
after you execute the init.post_boot.sh file, navigate with your root ex app, or whatever app you are using... to this directory...
/sys/devices/system/cpu/cpu0/cpufreq/(whatever governor you are using)/scaling_max_frequency
long press on the scaling_max_frequency file, and select "view as text"... your new value will be displayed there. check the directory for cpu1 as well. same file path, with the exception to cpu1
hope that helped. good luck
Click to expand...
Click to collapse
hey that part up top where u said not to change its just for references.. well when i change.. where it says AUTO.. i changed it to 1566000 and it works fine for me.. i saved it rebooted the phone and its sticks just fine.. i didnt have to change the part near the bottom...
Related
Ok, basically my linux knowledge is very limited and i need help modifying a file that gets written on boot (i don't know if this would even work, so if someone could answer that it would be very much appreciated).
The file i'm looking to change is '/sys/module/q6audio/parameters/speaker_max_gain'. In the latest 2.1 build this file is set to '602', which i think explains the slight volume increase from 1.6 (it was set to '600', but located in 'sys/module/msm8k_cad_volume/parameters/handset_max_gain' instead)
So, does anyone know how to alter this file? I know it gets re-written every time you boot the phone, but i can't find where it's being written from. Is it a kernel thing or am I completely wasting my time with this?
Cheers
UPDATE - Thanks to @VogelDerNacht, i've tried a few things like trying to change the value in the init.rc (echo "value" > sys/module/q6audio/parameters/speaker_max_gain) which didn't work, and i then tried to use a sysctl.conf in /system/etc/ to do the same thing, which also didn't work (don't think the kernel supports this), so now i'm pretty stuck
It seems like i may have to wait for the kernel source to be release now ><
how about creating a simple shell script and having it execute as a service from one of the init scripts ?
its possible the sys entry is not created until later in the boot sequence
DJ_Steve said:
how about creating a simple shell script and having it execute as a service from one of the init scripts ?
its possible the sys entry is not created until later in the boot sequence
Click to expand...
Click to collapse
could you give me an example please? i'm pretty new to all this linux stuff
The problem seems to be that when i add the line in to the init.rc (or any of the init files) it gets overridden by something else (probably the kernel) and i can't get it to apply my changes. I can change it fine whilst the phone is running, but that doesn't do anything because i think these files only get read from once when the phone boots.
I could be completely wrong though, like i said, my linux knowledge is pretty bad ><
First you need to confirm that entry boosts what you want
DJ_Steve said:
First you need to confirm that entry boosts what you want
Click to expand...
Click to collapse
That's the problem. I think it reads from the file only once when the phone boots but i don't know, that's why i want to change it on boot to see if it works
their should be a simple script (.sh extension) in /system/etc that you may be able to edit to add echo *your value > sys path to end of
DJ_Steve said:
their should be a simple script (.sh extension) in /system/etc that you may be able to edit to add echo *your value > sys path to end of
Click to expand...
Click to collapse
Tried that. Tired editing the init.rc, that didn't help. I tried adding a sysctl.conf but i don't think the kernel supports it. I tried editing every .sh file i could find but it looks like the kernel just overwrites everything
ok if you fancy a hand trying to get the volume to boost drop me a pm as i woudln mind being a tester ffor playing with werid options (and since iport android anyway i know my way around
This guide will assume the basics (image editing, apk manager setup, adb, etc..) are understood. Minus 9png's, I will go over that. The point is to have a base here for discussion on how to edit things properly. If anyone has something to add, please do.
OK, lets start with something that caught me off guard when switching to a phone with blur... there are certain apps that have dependencies. You have to set those dependencies up. The easiest way to do this is, from whatever ROM you are running, open the zip up with 7zip. Also open up your APK Manager and go into the "other" folder. From your ROM grab framework-res.apk, blur-res.apk, moto-res.apk, settings.apk and systemUI.apk and copy them into the "other" folder. Once there, open up a command prompt. change directories until you are in the "other" folder. Once there do this for each item. apktool d framework-res.apk and hit enter. Then, apktool if framework-res.apk. Do that for the rest.
9pngs.. Everyones afraid... they are a walk in the park. 1 extra step and its done. Decompile your apk, Edit it to your liking and save it. Open it up with draw9patch and add the guides back in and save it. The right and the bottom just make a big ass black line from one side of the image to the other (most of the time). The left and top side require a little fine tuning. Basic rule is to stick a dot in "the middle". Over on the right, see if it looks right. If it doesn't, adjust it. Once done, save it. Recompile and you are done. If using apk manager 4.9 or newer, make sure you delete the images you edited in the keep folder.
Editing xmls....
You are going to be editing xmls to either change background color or text color. Heres a general rule that will help... open the xml in notepad++ and hit ctrl +f. search for android:background .... you can change whatevers there to a hex color. like, if you wanted a dark red.. #ffbc1010. if changing text colors, do a search for android:textColor. Do the same thing with searching and changing.
Some edits will be found in the values folder... this would either take place in Colors.xml, drawables.xml or styles.xml
As I have found, some xmls just dont have a call to a bacground or text color so.. you just have to make one yourself. I always stick those in right after the androidrientation stuff. For example, you want a red background and nowhere in the xml can you find a spot to change it. No worries.. add this... android:background="#ffbc1010" . Good to go.
Some apks wont decompile with apk manager 5.01. You get an out of bounds error. Use apk manager 4.9 for those.. it will open them.
If you try to install an app and something doesnt work.. 1 minor thing, even though the rest does work.. do not try to install another re-edit until you have gone back to a fully functional version. Otherwise, none of your new edits will take hold even if they are correct. (Learned that one the hard way)
Remember, trial and error siis the Android Way!!!
Lastly, I leave you with this... each app has its own "fun-ness" to it. If you are ever stuck and need help, please feel free to ask. I can't do magic.. like looking at Sense... cause I dont have it.. but if you are running GB stock, Blur or its just an app for any phone.. please ask. I will answer, even if I dont know the answer and we have to work together to figure it out.
This is my contribution to XDA. Let's keep progression moving forward. I want to see more themers and more options!!!!
EDIT:
NEW INOFRMATION
I copied this over from my how to on DF... The links are probably still good (I just updated them) but just make sure you are getting the latest version... I wrote the how-to in January.
Since I see a lot of people trying to figure out how to get into theming and such, might as well share my knowledge...
I would also like to thank Devildog8791 and say that he went thru and added a lot to this via PM (which I then pasted here). He also made it a lot more detailed and easier to follow along for everyone.
Things you will need:
-APK Manager located here. It is the one from post #226. It uses apktool version 1.3.1 instead of the newest one, 1.3.2. The new version has some bugs that have not been worked out yet.
-Android SDK located here. There are two different files for Windows: a zip file and an .exe file. I downloaded the zip file, but you can try the .exe file.
-7zip located here. Make sure you pick the right installation for your setup (32-bit or 64-bit)
-Java JDK located here. Make sure you pick the right installation for your setup (32-bit or 64-bit)
Before I begin, please keep in mind that this is just how I did it. Maybe it's perfect, maybe its wrong, BUT... it worked for me.
NOTE: PLEASE READ THIS
Unless you are going to be pushing apks to your phone or pulling them directly from the phone, you do NOT need to bother with steps 3-6 and 9-11. You also only need to add the Java stuff to your Environment Variables.
OK here is how I set all this up and in the order that I did it.
1) Install the Java JDK. You probably don't need to, but I rebooted after the installation was complete.
2) Install 7zip.
3) Extract the android SDK file and move the extracted folder to the root of the C: drive. I renamed the folder "androidsdk", but you can rename it whatever you want. On my computer, the SDK is at C:/androidsdk (whatever you name this and anything in its filepath, make sure there are NO SPACES).
4) Go into your sdk folder and run "SDK Manager".
5) When the "Android SDK and AVD Manager" screen opens up, select "Available packages". Select the packages you want to install and click on "Install Selected". If the "Choose Packages to Install" screen comes up automatically, then select "Accept All" and click "Install". This will take a few minutes. Go ahead and get a drink and stretch your legs.
6) When your packages get done downloading and installing, close the "Installing Archives" and the "Android SDK and AVD Manager" screens.
7) Extract the APK Manager zip file and move the extracted folder to your user file. Mine is located at C:\Users\Tim\apk_manager_4.9.
8) Now you need to set your environment variables. To do this, click on "Start" and then right click on "Computer". Left Click "Properties" and in the left pane you will see "Advanced system settings". Click on that and it will open up a new window called "System Properties". Click on "Environment Variables" at the bottom of the screen.
9) Now that you are in the Environment Variables screen, you want to look at the top part of the screen first. Under "User variables for <your name here>", click on "New...".
10) In the "Variable name" section, type in ADB.
11) In the "Variable Value" section, type in C:\androidsdk\platform-tools\adb.
12) Now go to the bottom part of the screen and find "Path" on the left side under "Variable".
13) Double-click that "Path" section and it will bring up the edit screen.
14) Go to the end of the "Variable value" section and add the following: ;C:\Program Files\Java\jre6\bin;C:\Program Files\Java\jdk1.6.0_23\bin;C:\androidsdk;C:\androi dsdk\platform-tools;C:\androidsdk\tools. Verify that the bin file locations for java are in the same place as indicated here. They should be the same, but check it to be safe. Also, don't forget to change the name to whatever you named your sdk folder. One last thing is to make sure you have a semi-colon in between each path as indicated.
15) Click "OK" when done and close all the windows.
16) Reboot your computer.
Now that you have your environment variables set, you should be good to go to use APK Manager. One thing that you might have to do is set up your adb drivers for your phone. I have a Droid Incredible and I went to this site to get mine set up. If you have a Motorola Droid 1 (which most on this site do), then it should set up with the proper drivers when you plug it in the computer. My wife has a Droid 1 and that is what happened for me.
So, now you have 7zip, SDK, Java and APK Manager installed, setup and ready to use. Fantasmagorical!
Great, now, what the hell do you do with it...lol
1) You decide on an apk file (let's choose phone.apk) to use. You can grab it from the stock ROM your using, pull it off your phone, whatever...
2) Now that it is on your computer, move it into the APK Manager's "place-apk-here-for-modding" folder.
3) Run the script.bat and select option 22. Then choose the apk (project) you want to work with.
4) Now select option 9 to decompile the apk.
5) Once that's done select option 11 to recompile the apk. If it asks you if it's a system app (y/n) then you are in business. If it says there is an error, it is most likely that the apk has some .9.png images without guides. If this occurs, grab the stock images and stick them in by using 7zip and choose "open archive".
6) OK, so it works fine, now what? Just choose "N" and when it's done, go to the "place-apk-here-for-modding" folder and delete the "unsignedphone.apk" file.
7) Now go back to the script and choose option 9 to decompile again.
8) Once it's decompiled, navigate to the "projects" folder and go into the phone.apk folder.
9) Make all your xml edits.
10) Now, go back to the script and choose option 11. Choose "Y" and then choose "Y" again.
11) Now, go into the "KEEP" folder and delete the resources.arsc file and also delete every single xml you edited. Then go back to the script and "press any button to continue".
12) Once that is done, you are done. Go into the "place-apk-here-for-modding" folder and you will see an unsignedphone.apk file.
13) Put it in an update.zip that you can install to your phone and then rename it to phone.apk.
14) If you are wanting to now stick your own images in, use 7zip and select "open archive" and then drag your images into the proper folders.
15) Close 7zip and select "yes" to the box that pops up.
16) Now you are ready. Move the zip file to your phone, reboot into recovery and install it.
Going to add something blur related here. AK Manager 4.9 will give you errors recompiling phone, contacts and dialer. To fix it, go into the decompiled apk and open apktool.yml with notepad++ or similar. You will see 3 lines.. -1, -3 and -2. Put them in order.. -1, -2 and -3. Good to go.
Very nice thanks for this
Sent from my DROID X2 using Tapatalk
No problem. Get out there and make some good stuff!!
Hey thanks for the guide. I have a lot of programming experience but I am fairly new to android.
With that said, you state that: "This guide will assume the basics (image editing, apk manager setup, adb, etc..) are understood."
Is there a page were this things are explained, I have the image editing down, but have no idea about the apk manager,adb,etc...
I found this and I was wondering if this is the apk manager:
http://forum.xda-developers.com/showthread.php?t=1227179
Thanks, and sorry if this sounds too noobish.
Yes, that is apk manager. I would use 4.9 though because 5.01 will give you a lot of "out of bounds" errors when decompiling. 4.9 wont. And the apps work.
There is also another thread here on XDA .. So you want to make a theme.. or something like that.
I also wrote a How-To on installing java, apk, adb and setting all of your environment variables. That is in the "Team Inversion Conversion" area on droidforums.net.
Edit: Added the how to to the original post.
Question
So i wanted to theme and started reading guides on xda and came to the conclusion that it was a lengthy process requiring knowledge of may different programs, most of which was over my head. Just recently i started digging into roms wanting to change the lockscreen background and incall backgrounds. using 7z i located the lockscreen background file at system\framework\framework-res.apk\res\drawable-hdpi\zz_moto_gradient_bg2.png I then copied the file out and opened it and using paint, changed the image to a different one and then pushed the modified file back into the zip and then flashed the rom. I was very happy to end up with this
.
My question is, not using apk manager or apktool or a command prompt or any of the methods that ive read, am i doing something wrong? Will editing roms in this method run me into problems? Or is it just a noobish approach that actually works?
afm1118... There is absolutely nothing wrong with the way you are doing things. Just make sure you don't mess with any 9pngs. if you edit those with your method, it will break the signature. The image would still work but the guides would be gone. When I first started learning to theme, I didn't understand what a guide was. So, heres my explanation... look at your keyboard... in landscape mode, the buttons are bigger than they are in normal view. guided 9s will make the images stretch perfectly to fit the required dimensions. unguided 9pngs will just take the actual image and make it bigger. Kind of like if you went into an image editor and re scaled a 40x40 pixel image to 100x100 pixels. It would still be there but it would be a little distorted.
Yeah i just stay away from the 9pngs because i dont understand them and just know not to touch. You definitely helped me understand them better tho. What i dont understand is the need to use apk manager, or what recompiling/decompiling is. Like just using 7z i modified phone.apk in the same fashion i did the lockscreen, changing the incall background. Im guessing apk manager is necessary for editing xml. I really want to understand all this.
afm1118 said:
Yeah i just stay away from the 9pngs because i dont understand them and just know not to touch. You definitely helped me understand them better tho. What i dont understand is the need to use apk manager, or what recompiling/decompiling is. Like just using 7z i modified phone.apk in the same fashion i did the lockscreen, changing the incall background. Im guessing apk manager is necessary for editing xml. I really want to understand all this.
Click to expand...
Click to collapse
I dont do .9 pngs and I still create alot of themes, dont be scared to theme cuz u cant do .9.
TheMuffStuff said:
I dont do .9 pngs and I still create alot of themes, dont be scared to theme cuz u cant do .9.
Click to expand...
Click to collapse
Im not scared of um, i just thought i would figure them out when i wanted to change one. but so far,with nitros rom and with muffstuff xkape and funkencools themes along with uot kitchen ive been very happy. The themes are great, im looking forward to whats next.
afm1118 said:
Yeah i just stay away from the 9pngs because i dont understand them and just know not to touch. You definitely helped me understand them better tho. What i dont understand is the need to use apk manager, or what recompiling/decompiling is. Like just using 7z i modified phone.apk in the same fashion i did the lockscreen, changing the incall background. Im guessing apk manager is necessary for editing xml. I really want to understand all this.
Click to expand...
Click to collapse
TheMuffStuff said:
I dont do .9 pngs and I still create alot of themes, dont be scared to theme cuz u cant do .9.
Click to expand...
Click to collapse
.9s are integral to theming....cheating them and not doing them arent an execuse
Nitsuj. Instead of bringing negativity into the thread, try being useful. This is a help section not a your doing it wrong thread. If you would like to discuss it further pm me.
Sent from my Nexus S using XDA App
Nexus S.. Ha.. Editing the build.prop har further reaches than I thought.
Anyway, yes, editing an xml requires decompiling and recompiling... or does it? Not so fast. You can use a Hex editor to edit those colors but, I have no clue. I never went that route.
I guess the easiest way to think about apks that are compiled or decompiled is like this... lets say you have a game.. Football.exe on your computer. you click it, it opens. Now, to save space, you zip it up and its now in a zip file called Football.zip. You click it, it does NOT open. The OS cant read a zip file as an executable file.
You open a compiled xml, can't read it. you open a decompiled xml.. its all right there in plain English. Why would you want to edit an xml? Many reasons. I am going to give you an example right here...
This is the decompiled progress-horizontal.xml from the framework. It controls the color of the bar when you are dwnlading an ap, adjusting the ringer or media volume, etc..
<?xml version="1.0" encoding="UTF-8"?>
<layer-list
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:id="@id/background">
<shape>
<corners android:radius="0.0dip" />
<gradient android:startColor="#ffdfdfdf" android:endColor="#ffdfdfdf" android:angle="270.0" android:centerY="0.75" android:centerColor="#ff000000" />
</shape>
</item>
<item android:id="@id/secondaryProgress">
<clip>
<shape>
<corners android:radius="0.0dip" />
<gradient android:startColor="#ff000000" android:endColor="#ffbf0d0d" android:angle="270.0" android:centerY="0.75" android:centerColor="#ffbf0d0d" />
</shape>
</clip>
</item>
<item android:id="@id/progress">
<clip>
<shape>
<corners android:radius="0.0dip" />
<gradient android:startColor="#ffbf0d0d" android:endColor="#ffbf0d0d" android:angle="270.0" android:centerY="0.75" android:centerColor="#ff000000" />
</shape>
</clip>
</item>
</layer-list>
Im not going to go look at a hex chart but I think this is from when I was making an orange theme the other day. You can see there are 9 hex codes for color. You can edit those and make the progress bar have a different background and color. If I remember correctly, the first 3 control the background and the other 6 control the color of the bar. Play around and experiment til you see one you like. you can also add in transparencies and such to get fading and whatnot. like #80dfdfdf instead of #ffdfdfdf.
Some xmls wont be as clear cut.. it mught say something like android:background="@drawable/status_bar_bg"
This still can be changed. You can actually add something to a folder..image, color, etc.. but you also need to make an xml for it too. (I think, never done it).
You can make it point at a different item or, you can just give it a hex color.
ok so with the lockscreen i did, i could have done it two different ways. i could have changed the xml to target a different file or what i did, modify the image file itself. its just like html or any programing, its been a while.
correct man. Deciding which way to go is key. some of those images show up all over the place. In each instance just have to decide if its better to point it something else or just change what its pointing to looks like.
When I first themed ShapeWriter(back when I hadn't even heard of a .9) I got into a whole new mess with .smali, turns out that's where the tracer color was defined. You could never edit smali without decompiling first, although for theming its rare to have to.
Once you start theming you start learning little things here and there. And usually if your theming, it's cause your trying to do what no ones done yet; so most of what your going to learn is from a LOT of trial and error.
I'm not good at writing guides or anything but anyone can feel free to ask in my thread or pm me if you have some specific questions, etc..
Sent from my DROID X2 using XDA App
Also just thought I'd add: things may seem confusing sometimes but so would basic algebra if it hadn't been etched into your brain already.
Sent from my DROID X2 using XDA App
I was wondering is someone could explain to me a little better as to how to make a flashable zip.
I wanted to change the background image of the dialer, but when I have a finished apk I dont know hot to make it flashable.
Thanks
Electroniko said:
I was wondering is someone could explain to me a little better as to how to make a flashable zip.
I wanted to change the background image of the dialer, but when I have a finished apk I dont know hot to make it flashable.
Thanks
Click to expand...
Click to collapse
Well I could get pretty indepth but if you just want one that works you could borrow mine or probably anyone else's and change it for your needs(deleting my files adding yours).
without getting into the actually scripting the basics are:
A script that tells you what files/dir go where(among other things) and the files.
Usually it will just unpack everything in the zip to the "root" of your system partition. So if you were to use my zip i would keep my dir's and just delete the actual files.
basically if you want to put a file in "/system/framework/" on your phone you would put the file in "/system/framework/" in the zip.
also a note if you use mine; it will only copy to the system partition and not sd or sd-ext. even with that it should fit your needs.
Hope that all helps
I have searched this but can't find my particular issue. I just flashed CM7 (previously had bionix). I followed the instructions on the CM7 wiki and all works smoothly and fine except in call volume.
It is extremely loud when I make/receive a call. When I adjust the volume it adjusts to what it is set to. How do I set the in call volume or solve this issue?
This may work with CM7's stock kernel. But I do know that if you flash a custom kernel like Glitch for say, then you could download a Call Script... http://androtransfer.com/fascinate/90call_vol.zip... With this file you can tweak all the call volumes to your liking.
Instructions (if you have Glitch kernel running):
1. Download the Call Script.zip
2. Extract the .zip
3. Move the file to your phone's internal SD card
4. In Root Explorer hit the "Mount R/W" button
5. Still in Root Explorer move the 90call_vol from the /sdcard to /etc/init.d
6. After it has been pasted into the init.d folder long press on the 90call_vol file and hit "Open in text editor".
7. Once the file is opened, the file will take you through the rest of the steps.
8. Once you have tweaked the settings in the file do a reboot and test out your phone. It may take a bit to find the perfect balance but with a little patience you will .
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
sokey70 said:
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
Click to expand...
Click to collapse
I was having the same issue on Glitch. Even if you're not on Glitch, I suggest flashing another kernel.
Sent from my SGH-T959 using xda premium
sokey70 said:
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
Click to expand...
Click to collapse
No problem. But did you try these steps w/ the Glitch kernel (because I don't think the stock CM7 kernel supports Call Script)? I was having the exact same issue and the Call Script fixed the issue for me. I'll upload my Call Script (already tweaked) in a few. In the mean time I would suggest you look into Glitch, much better then the stock kernel in terms of battery, stability, and color. Plus it will allow you to fix the horrible loud distortion present in CM7.
Yes, I installed Glitch and edited the file as explained and still had the issue. even a screen of your file would be good, I tried all different settings from 0-3 and each started off way loud and then when I adjusted the volume it went to where it was supposed to be.
each time you edit the script, you want to reboot the phone for the settings to take effect. also, make sure all permissions are checked by longpressing on the script using root explorer, select permissions and check all selections.
with glitch kernel, set all incall boost to 0. the highest would be 1. settings 2 and 3 cause distortion. in any other kernel, i've found setting 3 is the same as setting 1 in glitch.
This worked perfectly for me! Glitch kernel on MIUI SGSII rom.
Thanks!
Se7eN43 said:
each time you edit the script, you want to reboot the phone for the settings to take effect. also, make sure all permissions are checked by longpressing on the script using root explorer, select permissions and check all selections.
with glitch kernel, set all incall boost to 0. the highest would be 1. settings 2 and 3 cause distortion. in any other kernel, i've found setting 3 is the same as setting 1 in glitch.
Click to expand...
Click to collapse
Question....I can't get this to work. I notice in the file it says, "just be sure you do the chmod and chown commands below in any case." I think that's the piece that people are missing, and I can't seem to figure that out. I tried to go into terminal emulator and say
Code:
chmod -R 750 /etc/init.d/
and
Code:
chown -R root:shell /etc/init.d/
...but for both commands, I get that the operation is not permitted. I think this is what is causing my changes to not apply correctly, and I can't seem to figure out how to do these two commands. Both the etc and init.d folders are set to r/w/x, as well as the file itself
Are these commands extremely necessary and if so, what can i do to more easily make them work?
Perhaps someone would be so awesome as to create a flashable script for linux dummies like myself?
jakemg said:
Question....I can't get this to work. I notice in the file it says, "just be sure you do the chmod and chown commands below in any case." I think that's the piece that people are missing, and I can't seem to figure that out. I tried to go into terminal emulator and say
Code:
chmod -R 750 /etc/init.d/
and
Code:
chown -R root:shell /etc/init.d/
...but for both commands, I get that the operation is not permitted. I think this is what is causing my changes to not apply correctly, and I can't seem to figure out how to do these two commands. Both the etc and init.d folders are set to r/w/x, as well as the file itself
Are these commands extremely necessary and if so, what can i do to more easily make them work?
Perhaps someone would be so awesome as to create a flashable script for linux dummies like myself?
Click to expand...
Click to collapse
You don't need to use Terminal Emulator. It's 100.1% easier to use Root Explorer. Here's what to do. These are similar to the steps I posted above, but I simplified it to make it easier for yah...
Instructions (While on Glitch):
1. Download the 90call_vol (To make it easier use mine which is already configured)
2. Move the file from your PC to your phone's internal SD card
3. In Root Explorer hit the "Mount R/W" button
4. Still in Root Explorer move the 90call_vol from the /sdcard and paste it into /etc/init.d
5. Now the most important step... REBOOT
6. Done! Now test your device
Yep, that's exactly what I was doing and still, when I make or receive a call, the in-call volume jumps up to max unless I turn it down. T. Then if I make or receive another call, the in-call volume jumps back up again. This cycle constantly repeats itself. No matter what, the actual in-call volume keeps jumping up to max.
Thanks for trying, though.
And you're on the Glitch kernel right?
Yep. Glitch V13...
Boo. First off thanks for the help and guide but unfortunately it does not work for me. I've tried this twice now on cm7 and miui fresh installs. Neither worked and I followed the steps exactly. Man this is lame. Is there a previous version of either miui or cm that doesn't have this issue?
N00B_IN_N33D said:
You don't need to use Terminal Emulator. It's 100.1% easier to use Root Explorer. Here's what to do. These are similar to the steps I posted above, but I simplified it to make it easier for yah...
Instructions (While on Glitch):
1. Download the 90call_vol (To make it easier use mine which is already configured)
2. Move the file from your PC to your phone's internal SD card
3. In Root Explorer hit the "Mount R/W" button
4. Still in Root Explorer move the 90call_vol from the /sdcard and paste it into /etc/init.d
5. Now the most important step... REBOOT
6. Done! Now test your device
Click to expand...
Click to collapse
This did not work for me.....
You all are selecting ALL permissions in the script with the script in the /system/etc/init.d folder correct? the permissions must be done while the script is in the init.d folder. If you make the permissions before moving the script over to the init.d folder, it will not work. It should look like rwxrwxrwx (Read Write eXecute) for the User, Group & Other fields.
How do get to the permissions? I didn't see that. Also, does anyone have a link to the original cm7 kernel to replace glitch if it doesn't work again?
Never mind. Got the permissions set and it still starts out loud, this is ridiculous.
wow... sounds like your phone just doesn't like you. haha.. kidding.
another thing you can do is use Script Manager from the Market.
run script manager
navigate to script (doesn't matter what folder the script is in)
select script (window pops up)
select "Su" (android skull & bone crosses icon)
select "Edit"
select "File Editor" (make sure the settings are what you want)
press the phones menu button to save (you may be asked to save again when pressing the back button to go one screen back, of course save it again.)
select "Run" (window changes)
select "Close"
you need not to reboot or set permissions using Script Manager, so go ahead and test.
if this works, you need to set the script to run at every boot using Script Manager by selecting the script again and select "Boot" (gear looking icon) and run again. (Su should still be selected as well)
if you end up tweaking the script again, just select "Run" after you are done editing, then "Close". no need to reboot.
IF this too does not work, then you might want to try a fresh install of CM7+Glitch without any other extras, besides the script just for testing. and if you are not on the latest CM nightly, i suggest you update to it.
Boo, my phone does hate me! It must know that I want a Galaxy 2 lol. Well I tried the script manager and it didn't improve. Right now I am on MIUI and like it but could try the CM7. Both ROMs with glitch 13 gave me the same issue. I wonder if my speaker is messed up or somethingm although previously on bionix it was okay...
Hi,
I have an xperia sola with build .54. I did everything according to the instructions (http://forum.xda-developers.com/showthread.php?t=1417375) to make init.d scripts work on closed bootloaders also. I wrote one for myself also:
#!/system/bin/sh
echo "0,0,6144,0,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
But unfortunately it does not work. If I run it in terminal the value changes, but it reverts after restarting.
Sorry, for my bad english.
Hey mate,
First, check if init.d support was added correctly. Paste this in init.d with 777 permission, then restart phone, Go to/data/local/tmp/ and see if init.d_log_test.txt exists
If it does, then its an issue with script,else init.d Issue Report back and we'll look into your problem
Cheers
There it is. So, the init.d is working.
Which editor did you use to make the file ? And you did set the right permissions, no ?
I'm use notepad++, and the permission: rwxrwxrwx
Ok.. hm.. next thing, Click the "Show All Characters" option in notepad++. It looks like a "P' button.. See if the end of each line says LF or CR-LF
I see LF
Then I cant see any issues Can you send me the file ? Might be a typo or something missed out when you copy-pasted
Here: http://d-h.st/3Sk
Edit: I tried to edit init.rc. I added this line:
write /sys/module/lowmemorykiller/parameters/minfree 0,0,6144,0,14336,18432
but it doesn't work
Sorry my english.
Still couldnt find an issue Just to be sure its not an init.d issue,can you delete that file in data/local/... and reboot to see if its made again ? Maybe init.d support got broken somewhere in between
I delete the file, but it's recreated. I tried to change the sys/module/mali/parametrs/mali_mem file, and it was succeeded. It's let to change either files, but the minefree not.
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)