yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] kobridge:
Could you please be more specific? I'm not trying to down play it. I just want to find what was wrong and how you fixed it.

What I'm seeing is, adding some missing items based on stock build.prop sequence. For me, I rearranged the sequence based on the item name to make it easy to find and modify. That's why I said, almost same. I do not see any missing items or added items yet.
[Samsung Epic 4G Touch] DutchDogg54:
Not to sound like a dummy but would I replace my whole build prop with this file or add it to existing? I'm running AOKP milestone 5 with the FD26 modem and kernel (stock AOSP tweaked kernel, of course.) Which one would i want: aokp or fd26? Much appreciate the work to all those involved!

Sent from CIA headquarters via Codenamed XDA App
[Samsung Epic 4G Touch] JohnCorleone:
So wifi scan interval is referring to scanning for networks other than the one you are connected to? Did I understand that right?
[Samsung Epic 4G Touch] TeamERA:
Yeah thats right :) But only when yiur not connected to a wifi hotspot already, but you have wifi turned on.
[Samsung Epic 4G Touch] TeamERA:
You want the AOKP version, just replace the one yiu have now and set permissions.
[Samsung Epic 4G Touch] kobridge:
This is what I'm saying. Once we connected to one network, wifi will not try to search the new network until it lose the current connection. So, do we need to set up 5 minutes for this? My point was, how long we have to wait until wifi automatically find the new network and some people could complain why it's not immediately detect the new network. If wifi is turned on but no wifi network connected, then phone will search the network based on this time. That's why I said, it's based on user's preference.
[Samsung Epic 4G Touch] TeamERA:
Oh I wasnt trying to sound that way, sorry. But there were about 10 duplicate lines, some 3 times, others 2 times. You had conflicting values also, so Im just trying to help not take credit. I did want to thank you for thanking me in the OP, but I see you removed that ;). Anyways Ill keep trying to help if and when you call upon it, as I will for any member of xda.

And these build.props wont cause any boot loops :)
[Samsung Epic 4G Touch] TeamERA:
What your saying is right, but 5 min is clearly a small number compared to 3 min , as 15sec is compared to 3 minutes. So if they complain about 5 min, dont you think they may complain about 3 minutes, remember stock is 15 seconds.
[Samsung Epic 4G Touch] kobridge:
This is why I published the second version and now planning to publish another version soon. I'm still keeping my big thanks to you in my second post. :D

Thanks for your explanation!
[Samsung Epic 4G Touch] countryteazer:
Alls I know is I'm using the build.prop from the link TeamERA provided along with the init.d scripts that kobridge posted with the Blu Kuban ROM and I'm seeing the best battery life I've ever seen on any ICS related ROM. A very big thanks to both of you!
[Samsung Epic 4G Touch] kobridge:
Thanks for your feedback. Much appreciated!
[Samsung Epic 4G Touch] kobridge:
GB Blazer ROM 4.1 EL29 test

GB Kernel Test - Blazer 4.1 EL29 - Not able to change the CPU frequencies and frequency change causes phone freezing during the sleep & wakeup. No way to change this by init.d script so far. Only the way would be using Tegrak or System Tuner Pro tools. I tried System Tuner Pro and set the conservative governor as on boot instead of init.d option. Working like a charm and no freezing yet. Will report back the battery life. I turned on the default tweaks included in Blazer rom (init.d scripts) except the S70darky_zipalign script because it seems like this script is causing some widget not displayed - most of widgets not displayed but app shortcuts.

By default, all init.d scripts on blazer rom 4.1 are disabled. To run those scripts, you need to change the permission to 755 from 644. The tweaks look great!

Update: Blazer CPU governor changed to conservative from default ondemand and CPU underclocked to 1GHz. Besides of that, everything runs with Blazer defaults. Battery status : running 8 hours and 89% battery left. Getting almost same battery performance like running CPU tweaks on ICS.
[Samsung Epic 4G Touch] daniel4653:
I'm confused on how to possibly get this working on code name. All I have done so far is push the build.prop file for aokp that was posted yesterday.
[Samsung Epic 4G Touch] RustedRoot:
All's well save for the 70wifi script. Keep getting 127 Exit Code in Script Manager when booting. 3 other scripts returning 0 Codes. Running Team ERA's FD26 build.prop and Agat's FD26 with Sfhubs FD26 modded kernel plus. Removed Agat's 7Tweaks from init.d (I assume that was necessary?). Pray tell, what am I missing?

SOLVED: Copied sqlite3 to System/bin and System/xbin folders. (How do I give thanks to myself? Lol. Gave thanks to Kobridge however.)
[Samsung Epic 4G Touch] JohnCorleone:
Kobridge, here's a idle battery drain shot with wifi set to never sleep on Venum Ice. I do have a few init.d scripts running. I am going to try yours on next battery cycle...

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] kobridge:
init.d script should run fine on AOKP if you have the proper build.prop. Try it and let me know.

Check out this thread http://xdaforums.com/showthread.php?t=1630792. WiFi sleeps well now and there's some tweak also.

The above portion is from my op. Check out the link to properly use the 7Tweaks.

Update: wrong URL. corrected URL now.

ya, comparing both would be great.
[Samsung Epic 4G Touch] daniel4653:
Well i pushed the files into the folder and fixed permissions and rebooted so far so good ? Lol no immediate difference in battery
[Samsung Epic 4G Touch] kobridge:
CPU related scripts tries to under clock the CPU to max 1GHz and mostly works during the sleep & standby. During the on-screen mode, the battery savings would be minimal. If you have any tools like System Tuner (Pro), Better Battery Stat, or Battery monitor widger (Pro), check the CPU utilization after the some sleep. If you still see lots of 1.2GHz CPU utilization, then it means that scripts are not working.

If the scripts works then you will see lots of CPU offline and low MHz times.
[Samsung Epic 4G Touch] RustedRoot:
I had seen your thread on wifi never sleeping when you first posted it and thought, hmmm, I'm fairly certain mine does. I've mentioned 3g Battery Saver Pro in other threads and have had good success with it, but I wonder if it's redundant with your scripts installed (?) Seems to be working fine in tandem.

I used the sqlite3 file from a Titantium backup folder in data/data (I have no idea how it got there but a BusyBox file is in same folder) and it works, but let me ask you should I install a clean copy of it from the SuperOneClick app?

No biggie, but I couldn't find the link re: 7Tweaks script from the referenced thread. Interested to see (i.e. learn) what it says.
[Samsung Epic 4G Touch] kobridge:
I don't think you don't need a clean copy. The linked url explains how to add wifi delay option in the database. Once it's created based the linked url, you can use the 7tweaks file in this thread from op section.

Edit: what I mean is 70wifiSleepWait_kobridge.zip file at OP. unzip it and put into init.d directory. You will need this script only when you want to change the wifi delay time (need to change the value inside of the script). To check whether wifi sleeps after the screen off, you can jsut use the small values as less as.
[Samsung Epic 4G Touch] guirae:
Calk's v1.5 FD26. running these scripts. 8 hours and 30min. in, 72% left. kobridge is a bauuus.
[Samsung Epic 4G Touch] kilogramz718:
Always wondered about this

This Transmission was sent from my Epic Touch 4G Note Inside The BatCave
[Samsung Epic 4G Touch] kobridge:
About this?
[Samsung Epic 4G Touch] Admiral2145:
Omg... Best tweak ever. Can't wait to try this on Fe07 leak!
[Samsung Epic 4G Touch] kobridge:
I'm flashing it now. Will try on FE07. Thanks!
[Samsung Epic 4G Touch] Admiral2145:
Fe07 I hope... I thought kernels had to be modified to support these tweaks
[Samsung Epic 4G Touch] kobridge:
It wouldn't happen ever :). I've checked the FE07 and it looks like it's much better than previous version at least concerned about the tweaks. There's no visible tweaks applied on this new kernel but it seems like the performance and battery life is better (it's too early to say that but if someone want to hear about the battery life on this new rom).

To run the init.d scripts, you need to follow the steps again (placing the init.d scripts and if you do not run repacked kernel, then place the install-recovery.sh, etc...)
[Samsung Epic 4G Touch] RustedRoot:
Its been one of those days where my addled brain is functioning worse than its usual dim self, but I had to tell you here that I saw your post on sfhub's FE07 thread -- the one with "unplugged at 96%" -- and I looked at the attached pics and I thought, "WTF, is he, kobridge, published dude on XDA, talking about battery life after only 17 minutes on the ROM?" Yup its been that kind of day. Hope you enjoy the humor. I loved JC's comment, BTW.

Back to being on topic, I reduced the wifi-off delay setting to 2 minutes. Did you know that feature is also on 3G Battery Saver Pro?

And oh, my battery drained a whopping 4% over 10 hours last night. Sucks, huh Mr. Tweaker? Good work, laddie.
[Samsung Epic 4G Touch] kobridge:
I was testing D710 battery for the past several months on every builds. That's why I could tell you in 17 minutes on the new ROM.

No, I didn't know anything about the feature on 3G Battery Saver Pro. I never used that battery saver and now I don't use any battery saver because there's not many things we could get by using battery saver. I like my way more than saver.

Posted build.prop based on FE07 stock rom at op. Download it and unzip, then replace your build.prop under /system/. Permission should be 644.

This build.prop is only for stock FE07 Kernel/rom.
[Samsung Epic 4G Touch] daniel4653:
i saw you put that permission should be 644 how exactly do you do that on root explorer. obviously i know how to access permissions on root explorer but it doesn't show any numbers just check boxes.
[Samsung Epic 4G Touch] kobridge:
http://xdaforums.com/showpost.php?p=25468500&postcount=8

(I hope this would help you to understand the numbers)

644 = rw_r__r__ = 110100100
[Samsung Epic 4G Touch] daniel4653:
Don't completely understand lol hope this is correct
[Samsung Epic 4G Touch] sfhub:
BTW the FE07-Plus kernel repack in the 2nd post of the FE07 OneClick thread works really nicely to debug these scripts. If you get stuck in a bootloop, just boot into recovery, and connect with adb.

You'll be presented with a root prompt and /system will be mounted so you can "fix" your errant script.
[Samsung Epic 4G Touch] kobridge:
That's it!
[Samsung Epic 4G Touch] daniel4653:
Sweet thanks kobridge. Do that's all that had to be done and move the other files to init.d folder?
[Samsung Epic 4G Touch] locoboi187:
I'm stuck on the Samsung logo at boot after applying the build.prop on FE07. chmod 644 /system/build.prop as well.

EDIT: nvm forgot to type "adb shell" lol
[Samsung Epic 4G Touch] countryteazer:
So this won't work on the repacked version?
[Samsung Epic 4G Touch] kobridge:
Now I'm uploading new init.d scripts - modified from previous version. This tweak will only support the D710 Stock roms. Simplied CPU Governor tweaks and fixed few errors from 41Tweaks.

If you are using Stock kernel, then you need to install sfhub's auto root tool - option 'e' or place the install-recovery.sh file from my other thread.

The easiest way would be installing sfhub's modified kernel on this FE07 thread. It will support the init.d scripts.

Edit: not uploaded yet. Doing final test before posting...

This will work on stocked based repacked version. What repacked version are you specially talking about in here?
[Samsung Epic 4G Touch] BigJPNut:
On the FE07 build are you having trouble disabling auto startups of apps with rom toolbox pro?
[Samsung Epic 4G Touch] boi2gangsta:
Is ok if I use these scripts with calks scripts from his rom on fe07 stock rom + kernel (with init.d support) and is it safe to put the build.prop into fe07 also
[Samsung Epic 4G Touch] kobridge:
No. I don't have any problem. Just tested it out.

But I experienced almost same thing before when I tried disabling startups using Rom Toolbox. Sometimes, it's not getting superuser permission to disable or enable the startups. In that case, I selected first like 'CPU Control' and got the superuser permission, then tried disabling startups (it seems like some issue on rom toolbox and not the rom itself)

To make Calk tweaks working, you will need to manually change his tweaks. That's why I started working on these tweaks. By default, his tweak is based on conservative governor but it's not supported on stock ICS. It's only supported in GB Rom. Based on my test, it would not work well on the GB Rom either.

My recommendation is using my tweaks only and you may get the better result. For the build.prop, you can use mine on any stock based FE07 Kernel. Calk, Agat, sfhub Roms.
[Samsung Epic 4G Touch] kobridge:
Updated init.d scripts v.2 beta

Now I'm uploading updated init.d scripts.

It's still using ondemand governor for the CPU tweaks and I made it simple because there were many unnecessary governors that can't be used in e4gt on previous tweaks.

For the 41tweaks file, I fixed few errors from previous version and cleaned up the duplicated items with build.prop. So, by using these tweaks and build.prop, you may get the better result.

I tested out all these tweaks for several hours after the FE07 release and did not find any big issue yet except one thing:

If you set the wifi option to 'never' (keep wifi on during sleep), rarely wifi is not automatically reconnected after the sleep. Because it was not happened from previous tweaks, I'm trying to figure out why it's happens now. That's why I'm calling this tweak as beta.
[Samsung Epic 4G Touch] jerrypp:
after sleep /system/bin/wpa_supplicant(or other app) is killed and cannot restart sometime.
[Samsung Epic 4G Touch] RustedRoot:
Having problems following your syntax here. You meant to say 'Never' setting means wifi is OFF during sleep? Are you also saying it is mostly reconnecting on waking but not always with new script, or...? Sorry, can't follow the logic.
[Samsung Epic 4G Touch] kobridge:
That's right! Sorry for the confusion.

I'll check it out today.
[Samsung Epic 4G Touch] RustedRoot:
I've been getting the wifi-not-turning-on sometimes with your FD26 scripts and ERA's build.prop. For me it's not big deal since this has been an ongoing issue with all ICS leaks. (I'm going to freeze that battery saver app to see if the issue clears.)
[Samsung Epic 4G Touch] kobridge:
Freezing battery saver app would not help because I do not use any battery saver app but seeing wifi is not coming back now, frequently.

My question is, is this a current ICS build issue or not? To decide that I need to disable all tweaks and try again. That's what I'm doing now.

Update: it's still happening after disabled every tweaks. build.prop works fine and should be no issue on there. I'll move back to stock rom with wipe all and test it again.

Update2: confirmed that it's not the tweak issue. On the stock rom/kernel without any tweaks, wifi is not turned on sometimes after the sleep. Wheeew....

Update3: Added one more tweak file. This is to save the battery more aggressively. May experience the slowness (if you don't care about that, you can try it).

These tweaks are no longer beta version. You can use init.d.v2b (moderate savings) or init.dv2b2 (more aggressive savings).
[Samsung Epic 4G Touch] RustedRoot:
I gotta believe it's in the ICS build since like I said, my experience is it would happen with almost every version. Interesting though you don't seem to recollect that before? I know its happened (for me) with sfhub's one-clicks which only have root mods, so ya, it's in stock. Its certainly gotten much better of late however that I don't notice it much anymore.

Just flashed agat's odexed FE07 with sf's repacked kernel (I don't know if it's the Plus.) Will load scripts a bit later and let you know.

Any preference on the savings script you want me to load first? Does your change log for today need to be changed to reflect that these are out of beta? Also, at first glance it doesn't look like all-in-here zip is changed, but according to your notes it is, thus let me ask you a favor to name or number the versions differrently -- if I have it right. Much obliged.
[Samsung Epic 4G Touch] kobridge:
You may try init.dv2b2.zip first with FE07 build.prop (both are at top thread). If you feel it's kind of slow, then you can replace the init.d scripts with init.dv2b.zip one.
[Samsung Epic 4G Touch] RustedRoot:
I just saw you put the wifi sleep wait and the new all-in-here with the FE07 zip. Sneaky! Lol. Will not use those. Extracted 2b2 (there were two folders in there -- used the newest) and will load to init.d.
[Samsung Epic 4G Touch] kobridge:
You can put any scripts in init.d but if you don't want to run, then just change the permission to 644(rw_r__r__). The script has execute permission will run on boot. Typically we set 755(rwxr_xr_x) for the scripts running on boot. For the next time, I won't include the wifi idle tweak on the same zip file.

Strange... I did not include the all-in-here zip file in any other zip file. It's the only one and first version of tweaks.
[Samsung Epic 4G Touch] RustedRoot:
Can't get the scripts to run on boot according to SManager. On-Boot-scripts log is blank. Extracted build.prop from FE07 zip, moved it to /systems (renamed old build.prop and moved it to root), set 644 permissions. Extracted 21 cpu, 31cpu, 41tweaks, and 70wifi, moved to /systems/etc/init.d (deleted 7Tweaks -- now I know only to change permissions), changed permissions on all to 755. Opened each file in SManager and clicked su and boot, then save and exit. I get exit codes of 0 for both cpu scripts and 70wifi when they are run manually through Smanager but 41tweaks shows a 1 exit code. Again, however, nothing loads on reboot. No prompt for sqlite3 this time.

I'm doing this as I did with FD26, but something is gnawing at me that I forgot.
[Samsung Epic 4G Touch] boi2gangsta:
Which scripts and build.prop would be the best to use with caulks 1.5
[Samsung Epic 4G Touch] countryteazer:
Kobridge, would you or Team ERA be kind enough to provide an updated build.prop for the latest AOKP? Or is the one that Team ERA sufficient for the latest AOKP rom? Big thanks for all your effort
[Samsung Epic 4G Touch] kobridge:
First, putting something in root is not a good idea. For anything backed up, sdcard (internal or external) would be the best place. build.prop should work because it's the same thing that currently I'm on.

init.d directory and files inisde of it should have the permission set to 755 (rwxr_xr_x). Showing exit code 1 is fine on SManager. It will run on boot without any problem. For wifi idle time tweak using sqlite3, be sure that you already manually created raw on the table and you have the sqlite3 executable. Actually I explained all of these over multiple threads.

In here, my recommendation is, if you are on sfhub's FE07 and stock FE07 kernel, then try to run the init.d scripts automatically without SManager's help.

Definitely you can try mine if you don't have anything in your mind. Basically some portion of tweaks in here actually came from Calkulin's. Because his tweak didn't word well for me, I modified it and added some other things.

Which Kernel are you using now? build.prop is just like the Kernel. We can port it to any Rom based on the same kernel (if you are not moving around between the ICS and GB, or between the Stock and customized roms. So, you are on the same kernel where you used AOKP version of build.prop, then you can use it again.
[Samsung Epic 4G Touch] boi2gangsta:
I mean like what combination of scripts like for example fe07 build.prop with aggressive or moderate on calks 1.5
[Samsung Epic 4G Touch] countryteazer:
I'm using the latest AOKP rom which has FE07 kernel. Thanks!
[Samsung Epic 4G Touch] guirae:
with the new init.d scripts, do i need to get rid of any other scripts or just add it with the other scripts that were from the all_in_here.zip
[Samsung Epic 4G Touch] kobridge:
Sorry for delaying the answer. I was preparing the quick guide on my second post.

I'm currently using fe07 build.prop + aggressive one to see any more battery savings comparing with when I used the moderate one. You can use any combination but aggressive one is not being tested long time and I don't have any result of that tweak. So, if you want to use kind of proven, then fe07 build.prop + moderate one. Be sure that you read my quick guide at second post and back up Calk's original tweaks and build.prop for just in case.

You don't need the previous one. Remove old one and place the new one.
[Samsung Epic 4G Touch] kobridge:
If you send me the build.prop that you currently have, I'll try to change it and return back to you. But, again, you can still use the old one because build.prop does not change your actual kernel. It's place where the current phone information is collected and having some tweaks based on it. One cons using build.prop which is based on previous kernel is, system will show some old information (go to about your phone) because it's not updated. No actual impact to your phone.
[Samsung Epic 4G Touch] kobridge:
Here we go.

Attached is baded on AOKP build 35 and Kernel FE07.
[Samsung Epic 4G Touch] tdunham:
Are the file links in post 88 still valid (for the FD26 kernel in particular) or do they need any additional updates/modifications? Also, if you plan on keeping the support for both FE07 and FD26 kernel, would you mind adding those to the OP please so those of us that wish to remain on the FD26 kernel will have a more efficient method to check for updated files? I believe it would be easier to keep the files separate and distinct to prevent confusion between the 2 different kernels as I see you have already started to do with the FE07 file downloads.

Also, thank you for your input in Calk's 1.5 thread.

Edit: Just a suggestion as well about the prior post (and perhaps future ones as well)... as the thread is growing larger, wouldn't it serve a better purpose to add an important updated file like the AOKP FE07 build.prop to the OP? It would help to keep important updates in one place. :)
[Samsung Epic 4G Touch] kobridge:
I'm not trying to provide the tweaks for all users. Mainly for the Stock kernel rom users. Because some people asked me to modify these tweaks to support AOKP, I just created the aokp version build.prop (in previous post). For the post #88, it was done by TeamERA based on previous kernel. Because I'm only with stock kernel, it's gonna be really hard for me to track all different kind of roms/kernels. If I move the kernel related support into the op, then I would have to support it for the next kernels. That's what I'm afraid of and that's not the reason why I'm in here.

Actually my primary intention was just giving some useful information to anyone who want to know about the init.d and tweaks. But it's getting bigger and somehow people started expecting me to have the product that is 'ready to be delivered' type of things.... Having lots of fun in here. :)
[Samsung Epic 4G Touch] tdunham:
Ahh, well it looks like it's going to grow out of control anyway. :rolleyes:

Making changes to build.prop is fairly easy (and tedious) but having the finished product for your particular build does make it far easier to implement. I believe that many of the users here are just plain spoiled & lazy to expect all of the work to be done for them without any foreknowledge as to how it all works. I also realize that the development of this thread is in the relatively early stages. Maybe TeamERA or someone else can continue providing us with the additional support necessary for the different 'flavors' out there.