yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] tdunham:
Hey Daniel. I think he's just re-doing the build.prop to match the latest kernels as they come out and the init.d scripts were fine the way they were but are still necessary if you want to use all the tweaks available (I think that's what you meant right? :))
[Samsung Epic 4G Touch] kobridge:
Thanks and that's exactly what I meant
[Samsung Epic 4G Touch] tdunham:
Hey KO. I think this is an easy couple of general questions.

I know you are writing and testing these scripts on Stock ROM and I don't expect you to support all of the custom ROMs

The init.d scripts should run just fine without any adjustments on custom ROM as long as the kernel we are using has init.d support?

Also, you write that build.prop is specific for stock kernel (and rom). Just curious why. It should still work (in theory) for modified kernel (and rom) too correct?

Once again, appreciate the work. Do not expect support beyond what you are testing. I will probably dissect the scripts and adapt them to my needs when I have time. This is all for learning anyway! :D
[Samsung Epic 4G Touch] kobridge:
I think that's a really great question!

1. Yes, init.d script should run on all stocked based kernels (no rom, kenel modified) because basically it's using same busybox, kernel shell, etc.

2. For the build.prop, there are some customized informations there something like build #, modification #, etc. So, many Devs they put their own #s over there. So, if you replace the build.prop with different one, those info will be replaced with the info in new build.prop. Besides of these, there are lots of tweaks that can be commonly used on most of the roms. But if the build.prop is used on different Kernel based Rom like AOKP, then couple of build.prop items should stay same from previous one, otherwise it would not work. But stocked based roms, if you don't care about the version info or Dev's specific build info, then you can even use the previous build.prop for current rom.

I hope I answered all of your questons, but if not let me know again.
[Samsung Epic 4G Touch] tdunham:
Thank you, I asked those questions for everyone just not myself so we can know how it all works together.

The ro.build & ro.product in build.prop are just information fields I think and if someone does not know what ROM they are running (and have to look to remember), they shouldn't be making changes to it! :p LOL

Edit: Does the build.prop get replaced if you flash a different kernel? If so, it would have to be replaced (or modified) every time a kernel is changed also correct?
[Samsung Epic 4G Touch] kobridge:
You got it but it's not always true because some devs are using those fields to perform specific task and I've seen that in aokp. In stock those are informational and you can change it manually.
[Samsung Epic 4G Touch] tdunham:
Sorry, you posted your reply after I edited mine.

Does the build.prop get rebuilt/replaced every time you flash a new kernel? Mine is in a happy place right now so I don't want to experiment just to answer my own question. :)
[Samsung Epic 4G Touch] nibrwr:
Build.prop only gets replaced with ROM flashes. /system
[Samsung Epic 4G Touch] kobridge:
If you want to keep your own build.prop then you must back it up because flashing new rom always format the system partition. This means that everythibg under /system will be cleaned up. But flasing kernel is different story.
[Samsung Epic 4G Touch] kobridge:
save more battery by using zipalign

you can even save more battery by aligning the APKs thru zipalign tool.

Section 4.4 and zipalign.zip tweak file added at op.
[Samsung Epic 4G Touch] tdunham:
Hi KO. Once the zipalign tool is installed will it be necessary to run it again once in a while or is the tool there permanently once it has been installed?
[Samsung Epic 4G Touch] kobridge:
It's ok running this tweak every time and this tweak will check the any updated apk or new.

But if it runs every time on boot, the boot time would take longer.

So, if you want to run this in a while, change the permission to 644 then it won't run on boot. But if you want to run it again, then change permission back to 755.

Changing permission would be much easier and safer than changing the code.

Edit: Another great way to run zipalign tweak is by using SManager. If you do not want to run this tweak on boot, then whenever you want, just run this script using SManager. Just same as running this script on boot but you can manually run this script any time without changing the permission.
[Samsung Epic 4G Touch] kobridge:
Updated 11zipalign tweak file posted.

What's changed: conformation of temporary APK file removal. If it's not deleted, add the error message to log file. Temporary APK files will be removed during the next boot.
[Samsung Epic 4G Touch] edlee:
I am running calks 2 v1.5 rom, with sfhubs fe10 kernel-plus.

Can you direct me to which build.prop I should be using?
[Samsung Epic 4G Touch] kobridge:
Just replace with FE10 build.prop at op section after unzip it.
[Samsung Epic 4G Touch] edlee:
even though calk's 2 v1.5 rom is based on fd26, and kernel is fe10, I can use the fe10 build.prop in the op section?
[Samsung Epic 4G Touch] kobridge:
Great question! +1

OK, let me explain a little more.

Basically FD10 build.prop is based on FE10 Rom.

So, if you place this fe10 build.prop file, then your phone will display that FE10 related information at settings > about phone. So, this may give you some confusion because the displayed information is not actual configuration of your phone. If you don't care about the info, then you can use fe10 build.prop.

But if you care about that info, use the build.prop included in all_in_here.zip file. On that zip file, build.prop is based on FD26.

Actually, build.prop is based on the Rom and that's the reason why it's stay same (not removed) even when we reflash the different kernels.

Edit: just want to show you the example. The snapshot in here shows what happens when I copied FD26 build.prop over FE10 Rom/Kernel. About phone shows that it's FD26 Rom build. Baseband/Kernel versions are not changed (stay same).
[Samsung Epic 4G Touch] edlee:
Thank you, I really do not mind what it displays in the status, I just want to get the best battery possible while using calk's rom/fe10-kernel-plus combo.
[Samsung Epic 4G Touch] edlee:
after applying these tweaks, I noticed that if i get a phone call, it takes till the beginning of the third ring on the phone for the screen to turn on so i can swipe to answer the call.

Is this because the phone is in deep sleep state and takes longer to turn on, or there is an issue with the way I applied the tweaks?
[Samsung Epic 4G Touch] kobridge:
Both are correct!

If phone goes to deep sleep mode, it would take longer to wakeup, means that there are several steps to move back to awake mode. Also, build.prop tweak includes the code that make the phone to deep sleep.

If you also applied init.d tweaks, there's also some portion that affect the wake up time.
[Samsung Epic 4G Touch] tdunham:
I had this happen today. Just curious if you were also using the v2b2 init.d tweaks? I went straight to that one and performance seems to be fine except for an occasional lag that I can live with. I may let it go a while longer to see if the phone answering thing becomes an issue then drop back to v2b scripts to evaluate it further.

---------- Post added at 11:46 PM ---------- Previous post was at 10:59 PM ----------

Hey KO. Is it ok to just overwrite the zipalign that is already present in system/xbin (on Calk's v1.5 FD26 rom)?
[Samsung Epic 4G Touch] kobridge:
If the lag time is too long for you, you can go back to v2b anytime. Like I said, v2b2 is an experimental tweak. For me, I'm using more aggressive tweak to see any more battery savings but it's not a time yet to report. Of course, I also saw many lags during my testing but I'm still checking couple of things from my side.

If your rom already has zipalign, you don't need to over- write it. It should work same for zipalign tweak.
[Samsung Epic 4G Touch] MrTimz:
Just wanted to let everyone know that ecooce said updated build.props for AOKP, AOSP, CNA with kobridges guidelines coming soon ;) He said he has been busy.
[Samsung Epic 4G Touch] kobridge:
Added init.d.v2.4.zip - Complete set of init.d scripts. 41tweaks_other tweak changed a lot (new tweaks and modification) based on sysctl and fixed one error. 21&31cpufreq tweaks were also changed more aggressively. 11 & 70 are same. In the zip file, included sqlite3, busybox, zipalign executables in case you don't have it.

I recommend to use 41tweaks_other tweak in this attachment. This tweak would be more smooth and faster than previous ones.

21 & 31 - you can use any previous ones if you see the lags on these tweaks.
[Samsung Epic 4G Touch] akarol:
Any way you can make a CWM flashable zip with ALL your tweaks?
[Samsung Epic 4G Touch] tdunham:
It's pretty easy to do. Let me know what build.prop and init.d you want and as long as it's ok with KO to post it here... otherwise I can PM it to you.

---------- Post added at 08:37 PM ---------- Previous post was at 08:32 PM ----------

Hey KO. An init.d question for you. Does it matter what order your init.d scripts run in? I've been renumbering them a little for my own setup and was curious if it made a difference. (I'm still on Calk's 1.5 and he has his own init.d scripts that I have to work with too.)

Edit: When I say renumbering, I just mean renaming the init.d filenames.
[Samsung Epic 4G Touch] kobridge:
It's ok renaming the tweak files for your own purpose. But if you create flashable zip file, please keep the original. If you can create the flashable zip file, then I'll give you a little guide (if you want). Also, if you want to use Calk's original tweaks, just let me know which one you want to keep then, I'll check it out if there's any conflicts or something needs to be changed.

The ordering really doesn't matter in my tweaks. But 21 & 31 need to stay same order like s21 & s31 or like this.

Actullay making flashable zip file would be my next plan but if you could do that, it would be really great for me and many people who likes these tweaks.

Edit: I'm not supposed to say this - my next plan is adding odexme tweak into my tweak package.
[Samsung Epic 4G Touch] tdunham:
Here is Calk's original init.d folder:

0dalvik2cache

2cpufreq_governor

3cpufreq_screenstate_scaling

5tweaks

6firstboot

I delete #2 and #3 because I am pretty sure that your #21 and #31 replace these. The rest remain the same.

I will discuss the flashable zip once I finish writing the script. I will have to learn the proper syntax to program file permissions, the rest is easy.

Unless you want to show me permission line(s) for the script ;)

These may not be correct but I want to set permissions like these examples.

Example: set_perm_recursive(0, 0, 0755, "/system/init.d");

set_perm(0, 0, 0644, "/system/build.prop");
[Samsung Epic 4G Touch] kobridge:
I don't think you need Calk's 0, 5 and 6 tweaks. The same thing in 5tweaks is already in my tweak. For 0 & 6, you may don't need it. For 6, there are couple of database update tweaks and maybe I can try on my tweaks but not a big deal -

window animationscale change, display_battery_percentage, wifi_sleep_policy.

For the second thing, let me pm you late tonight.
[Samsung Epic 4G Touch] tdunham:
Ok thank you.

Also, if we do a flashable zip, I always like to make another flashable zip of the original settings. This way, users can undo the changes if they want.

---------- Post added at 10:15 PM ---------- Previous post was at 10:04 PM ----------

I think I have the correct permission lines:

set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");

set_perm(0, 0, 0755, 0644, "/system/build.prop");

Edit: Corrected the permission for build.prop and it appears to be working properly:

set_perm(0, 0, 0644, "/system/build.prop");
[Samsung Epic 4G Touch] tdunham:
KO, I just sent you a PM.
[Samsung Epic 4G Touch] tdunham:
It looks like sqlite3, zipalign and (of course) busybox are already implemented on Calk's ICS rom. This actually helps me out because now I know what their permissions are supposed to be. :)

Overwriting these probably won't be any issue do you think?
[Samsung Epic 4G Touch] kobridge:
Replied back to you :D
[Samsung Epic 4G Touch] ReubenRene:
Where do we put these permissions at?
[Samsung Epic 4G Touch] daniel4653:
Through root explorer or something similar . You long press the file and scroll down to permissions
[Samsung Epic 4G Touch] ReubenRene:
This is what I get when I longpress the file and go to permissions. Not sure where I change the permissions
[Samsung Epic 4G Touch] kobridge:
There are some related posts in this thread -

http://xdaforums.com/showpost.php?p=25443610&postcount=2

(check quick install guide)

http://xdaforums.com/showpost.php?p=25468500&postcount=8

http://xdaforums.com/showpost.php?p=25849559&postcount=126

(127, 128)

Let me know again, if you still don't understand, then I'll post the screenshots.
[Samsung Epic 4G Touch] daniel4653:
Lol make it easy for him :)
[Samsung Epic 4G Touch] ReubenRene:
Thank you guys so much I truly appreciate your help and feedback.. Am somewhat new to this but you tutalidge has helped a lot.
[Samsung Epic 4G Touch] kobridge:
The screenshot you posted is same as permission - 775

The screenshot daniel4653 posted is same as permission - 644

And here mine is same as 755 (for most files in my tweak use 644 or 755)
[Samsung Epic 4G Touch] kobridge:
70wifiSleepWait_kobridge.v2.zip just released

Check out section 4.5 from op and zip file.

Now you don't need to manually handle the database table to create the wifi idle timer. By using this tweak directly, you can create or update the wifi idle timer.

For more information about this tweak, visit http://xdaforums.com/showthread.php?t=1630792
[Samsung Epic 4G Touch] tdunham:
Ok, I have a question about this from the OP:

4.5 Wifi Sleep Wait timer

In my original version of this tweak, it was required to manually insert the table row to use this tweak. But it's fixed and now you can use this tweak without manually handling the database.

I have always gone to wifi settings/advanced and set my 'Keep Wi-Fi on during sleep' to 'Never'. Do you think that is still ok or should I change something? I haven't been running the 70 wifi tweak very long so I couldn't report any noticeable difference anyway.

Edit: Oops, missed the link above. I guess the tweak has it's own thread... I've got some reading to do. :)

Question still stands however, is there a proper/correct setting for the advanced wifi or will the tweak do what it needs to do regardless of the settings?
[Samsung Epic 4G Touch] edlee:
New scripts are awesome thank you.

I live in an area where i only get 2-3 bars of 3g signal. And for the last eight hours in deep sleep mode phone only used 0.75% dph which is amazing to me.
[Samsung Epic 4G Touch] akarol:
KO, can you, or anyone else, create a CWM flashable zip with ALL your tweaks? I trust you would know which would work best with Calk 2 1.5. I wouldn't know where to begin flashing tweaking one script at a time and with my luck, my phone would explode.
[Samsung Epic 4G Touch] kobridge:
We are working on that. Within few days, you may see these tweaks available thru flashable zip files (sheeee!)

Sorry tdunham, just saw your post.

Answer: In your case, this tweak will work like a charm - wifi sleeps in 10 seconds after you turn off the screen. How to check? Turn off the screen more than 10 seconds, and turn screen back on then you will see 3g or 4g turned of instead of wifi. But with the screen turned on, system will try to connect wifi again (only if you already turned on wifi from settings).

One more, this tweak works great with 'Never' option because you do not want to keep wifi turn on during the sleep mode!

But, if wifi is set to 'alway', this tweak won't work because 'always' option override this tweak. This tweak only works when you enabled the wifi sleep.
[Samsung Epic 4G Touch] r80ies:
I've been using the 70 wifi tweak all morning and noticed and issue with wifi waking properly. At times wifi would resume normally, but there were more frequent times when wifi wouldn't resume. I would manually have to turn wifi off then back on. Also I made aa change to the script from 10 seconds t or 10000 ms to 5 minutes or 300000 ms. So I disabled the script for noW. Any thoughts?

Thank you for all your hard work kobridge.
[Samsung Epic 4G Touch] kobridge:
I think I mentioned the same thing in somewhere in my thread. It's not because of this tweak. It also happens on stock rom without this tweak! I tested out and confirm that it's not the tweak issue. There are some people reported the same thing and they said that it's happeing without the tweak. I'm safe in here;)
[Samsung Epic 4G Touch] r80ies:
Haha yeah totally safe. I was just curious that's all. I have one other question. How would one go about tweaking the gpu settings to give a bit to some games? If you answered this before I do apologize, but a link would suffice to my question.

Thank you.
[Samsung Epic 4G Touch] kobridge:
Currently ICS ROM does not support the GPU(as long as I know). That's one of the difference between GB and ICS. To get the GPU control, I believe we have to wait until we have the ICS source code released. You can try chainfire but I'm not sure about that because it's been a long time for me used chainfire.

Market link (free version) - https://play.google.com/store/apps/...251bGwsMSwyLDEwOSwiZXUuY2hhaW5maXJlLmNmM2QiXQ..
[Samsung Epic 4G Touch] edlee:
kobridge is there a particular modem you recommend, or the kernels /tweaks are the most important when it comes to battery?
[Samsung Epic 4G Touch] tdunham:
Are you on ICS, I have been having this exact same issue (and it is annoying) even before applying any tweaks. Sometimes wifi wakes up and takes over, sometimes it doesn't.

Just confirming Kobridge's comment, it's not the tweak. At least not for me.
[Samsung Epic 4G Touch] kobridge:
There are lots of opinions on the modems. But I do not prefer any modems because every modem gave me the same very low signal. Nothing better or nothing worst - just stay same in my area (one of the worst area as long as I stay with Sprint). So, I just stick with most recent one with the hope.

Because modem does not give me the better signal, I mostly stay with kernel side tweak and other tweaks. So far, there is no proved tweaks that increase the signal strength. Actually this is the most important part when it comes to battery because if the signal strength is excellent, then battery consumption is minimal - win and win situation. But the signal strength is weak, it also consumes lots of battery.

There are two kinds of tweaks - one is even making phone better and another one is limiting or decreasing the full functionality of phone.

My tweaks works in both ways. If something is not critical for battery life, then I tried to maximize its function. But it affects the battery life, then I tried to reduce the capacity to extend the battery life....

I hope I answered your question.
[Samsung Epic 4G Touch] edlee:
Yes you always do. Can you make application execptions for the tweaks. Like when browser or voice command is accessed to go 1ghz. Cause im noticing on lastest tweaks are super aggressive to stick to 200ghz when screen is on but then phone is less responsive on certain tasks.

Update: i went back to init.d v2 because v2.4 was a little too agressive for my tastes.
[Samsung Epic 4G Touch] r80ies:
Thank you I really appreciate your time to respond.
[Samsung Epic 4G Touch] kobridge:
Now flashable zip files are available - http://xdaforums.com/showthread.php?t=1658471
[Samsung Epic 4G Touch] r80ies:
I agree. Almost every task I so was taking a bit longer. Personally I am willing to sacrifice a little battery life for a standard performance.
[Samsung Epic 4G Touch] kobridge:
Test out the flashable tweaks. There were some changes made on 2.4M and 2.4A comparing with previous tweaks.

Personally I like 2.4A but you can try 2.4M first because it's much faster than 2.4A.
[Samsung Epic 4G Touch] beast4romtheeast:
Thanks for providing the community with your work on battery tweaks, I just implemented the Init.d, going to skip Build.prop until a FE16 is released, I look forward to post my experience with the tweaks in a few days.... I was curious, if you wanted to manually make your own Build.Prop is there any documents I can read to make one that works with FE16?
[Samsung Epic 4G Touch] guirae:
so i just flashed CM9 and tried to apply your init.d.v2b scripts (the kernel for CM9A3 had a kernel with init.d). rebooted and boot looped. am a missing something..?
[Samsung Epic 4G Touch] kobridge:
Again, I do not support CM9. To use the script, you need to test it out first something like using SManager.
[Samsung Epic 4G Touch] kobridge:
No secret in here. Just copy from old build.prop starting at,

#

# ADDITIONAL_BUILD_PROPERTIES

#

to end of lines and replace the stock build.prop at the same line and below.

Or just check out thread for flashable zip file - http://xdaforums.com/showthread.php?t=1658471
[Samsung Epic 4G Touch] beast4romtheeast:
I will try this later today, everything smooth using scripts on FE16 no lag with init.d2.4 files
[Samsung Epic 4G Touch] guirae:
"Supported Kernel: AOKP CM9a3 (tested) CNA FD26 MIUI. For FD26, I've checked the items and values on it. There's some items sequence change made comparing build.prop in here and minor values changes - post #94."

you should take that out
[Samsung Epic 4G Touch] tdunham:
That's a pretty old post. I'm pretty sure Ko apologized for not being able to support everyone. He can only do so much with one phone after all.

Edit: I once promised to cherish and obey but that ship sailed a long time ago too. ;)
[Samsung Epic 4G Touch] jamice4u:
Thanks. I believe there's a lot of work involved in creating these tweaks so I can understand why it will take sometime to get it done.

If I helped you out in any way please thank me. Thanks.
[Samsung Epic 4G Touch] kobridge:
This thread was being quiet for past few days :D.

Update:

I just want to update the battery life after applying my Kobridge tweaks using flashable zip files at http://xdaforums.com/showthread.php?t=1658471

Battery life screenshot is at OP.

I'm still on 1st battery cycle after I unplugged cable 2 days ago.

56 hours and 41% left. 1 hour on screen time. Lots of stuffs turned on (3G, wifi, synch, sns, sms, etc....)
[Samsung Epic 4G Touch] b1g.p0ppa:
I'm on CM9a4 runnning your 11zipalign and 41tweaks_other unmodified with no problems. I think I have an innovative way for you to tweak the build.prop files without having to keep track of the different ROM's files. As a thanks for those scripts I'll PM you the code.
[Samsung Epic 4G Touch] kobridge:
I didn't experience that for many days and ever with this tweaks. Yes, just like you saw, sleep governor with 200-500 cpu freq, it's totally ok with me. Only the chance for sleep of death would be the time when the phone wakes up. An that time, phone goes back to with 200-1000 range to avoid the some known issues.
[Samsung Epic 4G Touch] kobridge:
I'm not using any under-volting tweak in my tweak. Actually, uv is not supported in stock ICS kernel.

I believe under-clocking does not affect the 3g functionality. In general terms, under-clocking makes the system a little slower but system still works. But uv is little different because some apps or components need certain range of voltage to work properly. So, uc is much safter than uv.
[Samsung Epic 4G Touch] JohnCorleone:
Oh I agree completely. I haven't had a chance to try your tweak yet but I definitely will tonight. I have never undervolted this phone but I can see underclocking helping quite a bit. It sure does on my Nexus (800/200) in combination with the lazy governor and a 400/200 wheatley governor screen off profile. Hopefully when we get source we can get a few other governor options in the kernel because the 2 I mentioned increased my battery life by 1/3

Sent from my Nexus S 4G using Xparent Blue Tapatalk 2