yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] kobridge:
Definitely, I could work for Nexus one but I don't have enough knowledge about Nexus. I need to have some background on that phone like - the default governors provided by Nexus kernel and CPU freq ranges for each governors, etc. Do you know any good place showing all this information for Nexus?
[Samsung Epic 4G Touch] TeamERA:
Well I just started looking at the build.prop (havnt gone any further yet, now off work, just want to warn) and I noticed 2 things right away, its bloated beyond anything Ive ever seen lol. It is changing the lcd density to 200 in 2 (edit = 3 times)different locations, might want to take that out and change it to 240. There are several lines I think shouldnt be in there also. If you want me do do a full run down send me a pm.

edit, In your kobridgetweaks script you have ring delay at 1000, and in build.prop 0, it should be 0. Anyways Im done looking at it really, I never used calks scripts either, always made my own. No Im not trying to say your work is bad, jsut that it looks sorta sloppy atm, sorry man just want you to get better is all. Im a kobridge fan my friend.
[Samsung Epic 4G Touch] kobridge:
Whoops! Updating now and sent PM to you!

Saw your edit portion. Thanks for another one and your advice. I'm still trying to getting there within my limited and allowed time.
[Samsung Epic 4G Touch] sfhub:
Crap, had a brain fart. I meant to say busybox-initd (previously I wrote busybox-lite and now corrected it, so what is quote above is correct)
[Samsung Epic 4G Touch] Saear:
Trying to access the toggle for running wifi while in sleep mode.I'm running Calks 2.8.2 rom with the kernal provided in the rom. I don't have any menu or advanced options under wifi settings.

I have

Wi-fi check box

network notification check box

WPS button connection

than a wi-fi network list
[Samsung Epic 4G Touch] kobridge:
It it's not there then it would be the option that upgraded in ICS. For anyone using GB Rom, do you know how this can be done in any way?
[Samsung Epic 4G Touch] JohnCorleone:
I will see what info I can get when I get off of work. I would like to see some of these in our ICS kernels when we get source...

Sent from my Nexus S 4G using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] gershee:
aosp kernel wouldn't work on tw based roms (stock).

and I odined a kernel because I didn't want to flash anything from an ics recovery so went back to el26 first.

I was trying to just delete the init.d script from adb cause that seemed faster. but couldn't touch /system without su and I couldn't grant it cause it wouldn't boot..
[Samsung Epic 4G Touch] kobridge:
Understood. Maybe sometime I need to flash the AOKP rom and do some test. But right now I just want to stick with stock/Calk/Sfhub's rooted roms. I'm not ready yet to jump in.
[Samsung Epic 4G Touch] kobridge:
Wow, that's lots of modes over there! Are those from the stock?

D710 Stock only has 4 modes.
[Samsung Epic 4G Touch] sfhub:
You shouldn't need su with a custom recovery as the adb is usually already set to give you root permissions when you boot into recovery.
[Samsung Epic 4G Touch] JohnCorleone:
no but almost every kernel has those governors, USB fast charge, blinking light notification (BLN), backlight dimmer (BLD), for softkeys as well

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] odub303:
FYI, BLN for the SGS II is a big no-no for now, the BLN holds insane wakelocks and has not yet been fixed.
[Samsung Epic 4G Touch] kobridge:
The second version tweak coming soon...

Mainly on 41tweaks and build.prop file.

Edit: created issue log section in post #2. It seems like there's some wifi issue. I'm not sure it's Kernel related or this tweak related. Checking it now.

Update: Tested with Wifi Fixer but wifi still do not want to sleep. Now I'm heading to drug store to buy 'phenobarbital'(sleeping-aid). Still checking...
[Samsung Epic 4G Touch] tdunham:
Settings/wireless and network/wi-fi settings, press the menu key, select advanced, select wi-fi sleep policy, select never.
[Samsung Epic 4G Touch] adma84:
All three scripts seem to get me stuck on the SGS2 screen on AOKP m5. I have to odin el26 kernel and then use recovery to remove the scripts. Anyway to troubleshoot? /etc/init.d/ works because I made a test script to echo output to a file in /data/local/tmp

Any way for me to troubleshoot?
[Samsung Epic 4G Touch] kobridge:
SManager if it works on AOKP rom. But please don't use this tweak on AOKP. Some people reported it's causing stuck on boot screen.

I need to test the script and make it to work on AOKP.

Thanks.
[Samsung Epic 4G Touch] thizz415:
Dose this tweak work in Miui
[Samsung Epic 4G Touch] kobridge:
It's not ready for other roms except the Stock based roms.
[Samsung Epic 4G Touch] kobridge:
Update2: Finished testing wifi sleep mode. Actually there's nothing like that and wifi never sleep after it's turned on. Wifi could be disconnected by some app or any wifi configuration but it never go to sleep by check wifi 'never' option nor by setting the pm.sleep_mode. I added this info into the op and second post.

I'm not sure this would be the only stock rom/kernel issue but at least it's not working on ICS Stock/kernel.
[Samsung Epic 4G Touch] gershee:
how'd you removes the init.d files via adb? I kept getting permission denied.. :/

what was I doing wrong?
[Samsung Epic 4G Touch] gershee:
have a quick question..

if there is a build.prop setting in 2 different locations with 2 different values in the build.prop, which value would stick? first or last?
[Samsung Epic 4G Touch] kobridge:
which one? The second one will be active. Let me know which one has two. Actually, it had two versions and seems like you are using first version. If I found the same thing on the second one, let me edit & post it for you. Incorrect edit would be a reason of stuck on boot screen.

Are you testing it thru SManager? then you need to assign su permission to run the scripts. To remove, simply use root explorer or es file explorer.
[Samsung Epic 4G Touch] rmikulus:
I ran this on AOKP, although I already have a lot of init.d and build.prop tweaks set, so I'm not sure of the impact. Was able to run fine though.

---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------

My buddy with an Evo 4G was wondering if this would work on other phones, or if the script settings are specific to our device.
[Samsung Epic 4G Touch] gershee:
I meant in general. I have a list of build.prop tweaks and I just toss em any build.prop I'm using. wanted to make sure. I put them at the end not beginning right? I'm not checking for duplicate entries.
[Samsung Epic 4G Touch] gershee:
I meant if you can't boot up. in recovery. how do you remove the init.d scripts via adb? I was doing something wrong. I opened an adb shell. went to /system/etc/init.d/ and tried to remove the scripts but I didn't have permission? :what:

rephrased:

last time I tried these scripts on aokp one or more of them broke boot for me. stuck at sgsii.

I want to try again but how can I remove a script via recovery using adb?

and kobridge, a suggestion.. why not have the build.prop tweaks just as a standalone without the erroneous settings? that way people just drop the tweak settings in the end of their current build.prop.... less hassle..
[Samsung Epic 4G Touch] sfhub:
You need a recovery that has insecure adb (ie you get a # sign immediately when you open adb shell). All the rogue custom recoveries have insecure adb. You could flash rogue cwm, make your fixes, then flash back your existing kernel.
[Samsung Epic 4G Touch] kobridge:
If you are tyring to on AOKP, don't take the whole portion of tweaks or build.prop. Definitely, you will need to edit something. Because these tweaks and build.prop are created based on Stock rom/kernel, these are not going to work. Some people already reported that they experienced same stuck on boot screen, we need to find out what that is first.
[Samsung Epic 4G Touch] gershee:
exactly what I intend to do.
[Samsung Epic 4G Touch] bambam126:
Loving the battery thanks
[Samsung Epic 4G Touch] guirae:
I record my lectures via the stock TW app. After applying the scripts last night and recording and hour of a lecture, my battery drained about 20%. Is this expected in the context of applying this script and wakelock behavior? I'm just confused because prior to the scripts I would only lose ~10% in an hour of recording.
[Samsung Epic 4G Touch] kobridge:
Could be related. Did you replace the build.prop tweak in here?

In build.prop tweak, there's some options that maximizing your camera's capability. This function will maximize the performance but will cause more battery drain.

Try again with original build.prop and see how the battery drain looks like.
[Samsung Epic 4G Touch] guirae:
so I have the init.d in system/etc. I ran SManager and have all 4 files on su and boot. I ran it. Did I do anything wrong? I don't get that the whole 0test file. Although I have it inside init.d, it hasnt done anything..
[Samsung Epic 4G Touch] boi2gangsta:
How do I know if the scripts are running
[Samsung Epic 4G Touch] kobridge:
1. In here, I did not include the 0test file. I think you are referring to another thread that I created. Anyway, 0test file is to test the init.d functionality on boot.

2. There are 4 tweak files are included in all_in_here.zip file. Three files should be for init.d and build.prop for under /system folder.

21 & 31 tweaks are doing nothing for media processing. It's only touching the CPU governor (CPU speed control). 41 file has just few video (media) related tweaks on it - hardware video accelerate & jpeg (camera) quality. There is nothing that causing battery drain on this tweak. That's why I told you that replace the build.prop with original one and see what happens.

This one - http://xdaforums.com/showthread.php?t=1610741 Check out 'How to test'
[Samsung Epic 4G Touch] kobridge:
Actually you are giving me a hard time. :D

To run the init.d script, there're several things that you need to know. That's why I spent lots of time to explain every thing. If you don't understand what you need and how it works, then you need some more time until you understand what you're doing and what is required to do so. I'm sorry to say that but please research before you ask something.

I really want to help you and I'm really willing to. But there's some portion that you have to finish your homework at first.

Let me give you a homework (I'm not trying to offensive but trying to help you in here. I was just like you in 5 months ago).

1. what's the init.d script and how it works?

2. If you are using Script Manger, you need to understand how it works, and how this app make it possible to run the init.d script during the boot. Do you think, you can figure it out? What's the difference running the scripts during the boot or running the app after the boot?
[Samsung Epic 4G Touch] kobridge:
1. I thought I put the 0test file in somewhere but it's not. Let me add the 0test file in here (use it after unzip).

2. On the stock Kernel (if it's not repacked Kernel), init.rc does not call the init.d scripts directly. When we check the init.rc script, there's no routine calling init.d but there is a routine calling install-recovery.sh. So, that' the reason why sfhub added special function adding install-recovery.sh on his auto root package (I believe it's option 'E'). If you are using different Kernel except the stock or Rogue repacked, then I don't know the init.d script is going to run or not. Some other xxx.rc script would call install-recovery.sh or not. So, it depends on Kernel.

For the Rogue repacked kernel, you won't need install-recovery.sh (means you don't need to install auto root package) because init.xc calls init.d scripts directly.

3. Anyway, put the 0test file under /system/etc/init.d folder and assign the permission 755 (rwxr-xr-x), reboot and check the file is created and 'Hello Android' is there. If you see this, then it means init.d scripts are running.
[Samsung Epic 4G Touch] kobridge:
Want to add one snapshot -

battery usage with wifi turned on 24x7 (automatically on & off when I'm not in wifi range). So far so good.

JC, this is really not bad. It seems like more benefits by turning on wifi 24x7.
[Samsung Epic 4G Touch] guirae:
Wait..if i am using SManager to run these scripts through su and boot, these tests don't really matter do they..?
[Samsung Epic 4G Touch] kobridge:
You can also run 0test using SManager. It's not a big deal but once you confirmed that it's running, then uncheck 'boot' for 0test.

Edit: I forgot to mention one thing. I only use SManager just for test purpose because this process could be killed by any task killer or automatic memory management tool. What this means is, CPU governer still works on boot but mode changes (custom CPU under-clock) like sleep, awake, etc could not work afterward if process killed. So, better way would be find using init.d scripts through init.rc or install-recovery.sh.
[Samsung Epic 4G Touch] guirae:
So in SManager, i ran the 0test script (i have su and boot checked) and got:

exec sh ' /system/etc/init.d/0test/0test'

m/etc/init.d/0test/0test'

: not found/init.d/0test/0test[4] :

Just to be clear, it seems the scripts are running via SManager...when i check my frequency times, its not running at 1.2 anymore and spends a lot of time in 200mhz. That is why I am asking if running scripts via SManager is the only thing necessary, therefore not having to "Test" if it's running or not.
[Samsung Epic 4G Touch] kobridge:
Whoops! Previous 0test had wrong characters on it. Fixed. Use this one.

Be sure put unzipped file directly under /system/etc/init.d folder and not /system/etc/init.d/0test/. Any scripts in init.d should be placed directly under this directory and do not create any subfolder under init.d.
[Samsung Epic 4G Touch] guirae:
well thats funny because i got the 0test to work :)...

Edit: this was under /data/local/temp directory

Should i be worried..? should i fix it just in case?
[Samsung Epic 4G Touch] kobridge:
Yes, just in case. SManager runs it but if you use init.rc or install-recovery.sh, it wouldn't because Unix (Linux) does not recognize some hidden special characters.

That's why SManager shows the 'not found' error message.
[Samsung Epic 4G Touch] guirae:
Ah ic. Btw, I have init.rc and recovery.rc. I ran init.rc but it crashed and did nothing. haven't touched recovery.rc.

I just rebooted with the new directions (having the 0test in system/etc/init.d) and Hello Android appeared in that folder :)

Does the build.prop go inside /system/etc/init.d as well?

Also,

If i have init.d working, should i have SManager NOT su/boot the 4 scripts?
[Samsung Epic 4G Touch] kobridge:
init.rc is not the one that you can touch. It's kernel generated. So, don't touch it. Just try to find 'init.d' text from that file or 'install-recovery.sh'. If init.d is there, then you don't need SManager because kernel support init.d on boot. If init.d is not there but install-recovery.sh, then you need to put install-recovery.sh file in /system/etc folder.

build.prop must be placed into /system folder. Before placing build.prop, be sure that your kernel is Stock and not AOKP. You can find all these information from op.
[Samsung Epic 4G Touch] kobridge:
Adding two more snapshots #8 and #9 on second post.
[Samsung Epic 4G Touch] guirae:
Thanks for everything kobridge. You are the best.
[Samsung Epic 4G Touch] JohnCorleone:
Our findings are the same actually. I turned it off yesterday at work and I didn't have as much battery left at the end of the day as when I leave wifi on 24/7. I appreciate the very thorough testing you are doing here

Sent from my Nexus S 4G using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] kobridge:
email push interval

I added one more tip into the second post. Check it out from there - 11. email section.

If your phone does not go to deep sleep mode, then it wouldn't help much.
[Samsung Epic 4G Touch] gershee:
EDIT:

too late
[Samsung Epic 4G Touch] kobridge:
The quoted one above was not by me actually. I mis-edited so, it shows as mine.:p

I re-edited original! Thanks!

Edit: it seems like there's something wrong on XDA. Lots of quotes are 'reversed' between guirae and mine.

Update: lots of quotes between guirae and me were reversed. I don't know what happened. I corrected many conversation between him and I but not able to correct the post belongs to him. Strange... Strange...

It seems like the logic is simple. If we put the another QUOTE just after the first quote, then the original quote shows reversed and it appears quoted by someone else. For the reversed quotes, you can see the quote word on top of the post.

Brought up this issue to the forum's top general section - http://xdaforums.com/showthread.php?t=1635628

Figured out. Not be a XDA issue. I think it started from incorrect editing whenever we edited quoted php data (post). Two starting 'quote's always need two ending '/quote'. But if there's only one ending 'quote' then one remaining starting 'quote' is always carried over to the next post and it shows the quoted post is owned by the person who's quoting. Hope this make sense. I pm'd to guirae to make some modification on his post if he's able to do it...
[Samsung Epic 4G Touch] DutchDogg54:
Hey kobridge, what version of better battery stats do you have...mine looks way different, and I like yours better :)

Sent from CIA headquarters via Codenamed XDA App
[Samsung Epic 4G Touch] kobridge:
Download it from here - http://xdaforums.com/showthread.php?t=1179809

It's free for xda users - xda developer version and not from the market! Most recent version 1.8.1.
[Samsung Epic 4G Touch] DutchDogg54:
Thanks a bunch man, got it...I was on the xda version but 1.5.1 lol

Still doesn't look like yours though:

Sent from CIA headquarters via Codenamed XDA App
[Samsung Epic 4G Touch] JohnCorleone:
Lol...I think mine was 1.4 something. Thanks kobridge.. again

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] kobridge:
1.8.1.0 is in here http://xdaforums.com/attachment.php?attachmentid=1036954&d=1335983200

You can also find the same thing from previous link.
[Samsung Epic 4G Touch] DutchDogg54:
I got 1.8.1.0 from the original thread you posted but just to be sure I uninstalled and installed the apk from this link ...same

Sent from CIA headquarters via Codenamed XDA App
[Samsung Epic 4G Touch] kobridge:
Couple of ways.

1. After uninstall, check /system/app folder and be sure that it's not there.

2. Also check /system/data/com.asksven.betterbattery.... I think there could be two version over there. Remove the folders if it's there.

3. May need reboot

4. install new version.

Hope this work.
[Samsung Epic 4G Touch] DutchDogg54:
Well, followed those steps and its still the red lined one ...not that it matters, it seems to be exactly the same functionality wise, appreciate your insight though man...really good thread.

I noticed in the screenshots you're on a tw ics leak - might that be the difference? I'm on AOKP 4.0.4...either way, thanks

Sent from CIA headquarters via Codenamed XDA App
[Samsung Epic 4G Touch] kobridge:
That make sense. Check the version - menu > help > about and it will show you the version.
[Samsung Epic 4G Touch] DutchDogg54:
Man, that's some stellar time there dude ...super jealous! Checked there before when finding version info.

Not a good representation of what's possible for me on AOKP, but here's my last couple hours, for ****s & giggles.

Sent from CIA headquarters via Codenamed XDA App
[Samsung Epic 4G Touch] TeamERA:
Here are the finished build.prop files. You may need to set permissions once you paste it in /system/

These are files from a team member working on this phone, he wanted to help.

AOKP

http://d-h.st/g5S

CM9a3 (tested)

http://d-h.st/ZOk

CNA

http://d-h.st/JpD

FD26

http://d-h.st/jGo

MIUI

http://d-h.st/Ete
[Samsung Epic 4G Touch] JohnCorleone:
Kobridge, I was telling you about those other governors on the NS4G kernels and that phone is known for not having good battery life. Check these out...
[Samsung Epic 4G Touch] kobridge:
Thanks so much TeamERA. Let me test FD26 portion out. Now I'm trying to test the init.d tweaks on GB rom/kernel because it has only been tested on ICS Stock.

Wow! So, these screenshots are from GNex and these are from applying tweaks or what? If any tweaks made this difference what that tweak is?
[Samsung Epic 4G Touch] JohnCorleone:
No, those are NS4G using the lazy and wheatley governors I mentioned. Wheatley uses almost no battery when screen is off or phone idle. I am going to push for that one to get included in our source kernel. Lazy is like on demand except it shows no lag when underclocking a step. It would be great for your 1000 max freq. I swear..I am still considering a GNex with my upgrade. I bet I can get a good battery setup going on it
[Samsung Epic 4G Touch] JohnCorleone:
This is all I have in init.d on my Nexus at the moment and I just wrote the voodoo script this morning so my color settings set on boot. What exactly does userinit script do?
[Samsung Epic 4G Touch] kobridge:
Right, this is something needs to be done in Kernel level. Before my current tweak, I tried to underclock the CPU under 800Mhz on Ondemand governor, but some apps fc'd and not able to make those apps working.

Just like you, I think in some point of time, I also need to jump into Kernel side...:(

I don't use userinit script anymore and it's not included in op because it's causing some app not working (like lucky patcher....)

Edit: Got a time. Actually there were two lines of code.

Removing /dev/log/main. So, make the system run lightly. But I found that some of the apps are actually using this. So, removed this line.

The second line is sysctl -p.

I also found that stock kernel does not have /etc/sysctl.conf.

That's the reason why I did not include this tweak in my current op.
[Samsung Epic 4G Touch] kobridge:
Thanks again TeamERA. I've checked FD26 build.prop with mine in OP. Basically same and some reorganized the sequence. There are two values are different - not major items for tweak.

In yours -

windowsmgr.max_events_per_sec=250

wifi.supplicant_scan_interval=300

Mine -

windowsmgr.max_events_per_sec=150

wifi.supplicant_scan_interval=180

There could be many different opinions on these items. But my opinion is,

1. windowsmgr.max_events_per_sec value affect the smoothness of scrolling. Many FD26 users reported that scrolling is much smoother than previous build. But I tested it out with both values and I did not notice much difference between those values. So, I kept 150. The thing I considered in here is the CPU usage. If we think about on that, CPU will use a lot(?) more power to make the event available (max 250 times). I think it's the same thing like fps (frames per second in TV). If we increase the fps, then tv will show much smoother and clear screen, but if it goes above in certain level, we may not recognize the difference and may only use more power. So, I think 150 would be the acceptable value and we may not notice the difference.

2. wifi.supplicant_scan_interval. This is totally on phone user's preference. This value means that how long we have to wait unitl wifi tries to reconnect. 180 is 3 minutes and 300 is 5 minutes. With 300, we could save a little more power but have to wait longer until get it connected. If phone users do not understand this logic, they will start to complaining about the phone.... As you know, the stock value of this interval is 15 seconds.
[Samsung Epic 4G Touch] TeamERA:
I may agree with you about max events, but the wifi scan interval works like this, that number stands for " interval between scan/ notification of new wifi network discovered". So that means it scans for new networks every 5 minutes, I dont know anyone that wants to know there is a new network every 15sec. I look at it like if your going to be some place for more than a couple minutes and want wifi, your going to check.

lol, and I fixed many of the problems that were in there man, I see you trying to down play it by saying it was almost the same lol j/k no harm