yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] akarol:
MW, thank you so much for your time and concern. I have gone through the build.prop and I have changed the values for those commands to 0. I hope that's the same as deleting them. I wanted to leave them there to return them to their default settings if need be.

One thing I noticed is that there were two identical lines for the 1st and 3rd commands. The 1st one we're both set to 1 while the 3rd one had one line set to 1 while the other was 0.

I just rebooted it and so far, no WiFi drops. It's only been 10 minutes though. I'll update this post after an hour.

By the way, I must tell you that only the WiFi was being affected by these drops earlier. I thought the data network was also affected but turns out it was just crappy reception (thanks Sprint!)

Thanks again for all your help.

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] luis86dr:
Test zip up for those experiencing lag after applying build prop. Let us know your results.

http://db.tt/CJrY1pGI
[Sprint Samsung Galaxy S III] mw86:
Thats not the correct way i am sorry means when set to 0 the whole build.prop is still used then. I have made those changes for you and more in the zip luis just posted above. Please restore stock build prop and reflash this one and retest thoroughly on this one. Please do it just like that and don't bother manually editing anymore of em as the zip has them all done now. Please let me know if this a fixes lag for users reporting it and b fixes whichever data issue ypu had be it mobile or wifi. If it makes no difference, there is nothing else really in this buddy thats like that. Id say then try modem (baseband update as it runs mobile data and wifi the baseband that is) i use MD4 baseband.
[Sprint Samsung Galaxy S III] akarol:
Gotcha. Flashing stock and newer build.prop now.

Btw, changing those to 0 seems to have fixed it nonetheless. No more WiFi drops! =D

I'll report new build.prop after an hour of using it.

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] mw86:
:( since the dawn of this thread we had the recommendation to check both gpu options in developer options and I wish more users would see that :( I am glad you got that checked now. Is anyone having lag uaing the option anyway and is anyone not having lag after this. I need to know of the build prop changes are even necessary.
[Sprint Samsung Galaxy S III] Romcrazguy:
Can someone tell me what's the reasoning behind the wifi supplicant being 1000 instead of 180 in the build prop
[Sprint Samsung Galaxy S III] akarol:
Btw, I've been on MD4 modem and MOAR 4.0 since it's release.

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] mw86:
Thanks did you try the new fix zip? Its last post or two back.

---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------

If users would prefer that time we can set that no prob. I had it so high so wifi doesn't scan so much to save battery. We can set it to 180 i would guess its not too short at that.
[Sprint Samsung Galaxy S III] prboy1969:
Yes, definitely. I gave also learned considerable amount on Kernel tuning from this thread, and the TK members :) .

I believe gs3 man posted a response to this. It has to do with an app constantly checking for the time. I'll see if I can find the post.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] stas333:
Thank you! it keeps my phone up for over an hour in about an 8 hour period.
[Sprint Samsung Galaxy S III] ryandubbz:
No before moar I always had it checked but since rompnit says to keep it unchecked with his rom I did
[Sprint Samsung Galaxy S III] akarol:
MW, just flashed stock and then newer build.prop. Phone is charging now. Let it get to 10% and I'll do a quick test.

By the way, I had Aroma crashes twice in a row when trying to reflash the newest build.prop directly after flashing stock. I had to do a normal reboot, then go back to recovery and do the newer flash again.

Just thought you all should know. =P

Sent from my amazing Nexus 7.
[Sprint Samsung Galaxy S III] ryandubbz:
After installing the newest mod just posted the install booted rightt to recovery it didn't say complete it just booted right to recovery
[Sprint Samsung Galaxy S III] mw86:
Luis86dr is our Aroma man :) but if your on cwm recovery like me i run into occasionally and unless aroma itself updates it will be touchy on occasion. Check options slowly.

Okay fingers crossed :) let us know thank you

---------- Post added at 10:49 PM ---------- Previous post was at 10:47 PM ----------

I see buddy I should of realized :silly:
[Sprint Samsung Galaxy S III] iamikon:
Ah fellas I don't think it's good to disable hw overlays. It has always produced significant lag issues for me on many devices even on the n10. Just my two cents.

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] akarol:
Bad news. WiFi is totally borked now after latest flash. It won't connect at all. Well it actually shows as connected, but no apps with work. Data still seems fine via mobile network though.

I noticed that those 3 build.prop lines were reverted back to default values of 1 with this newest flash, is that how it's supposed to be? Also is it normal for there to be multiple identical lines in th build.prop file?

As far as lag goes, before this latest flash having Force 2D unchecked yielded better results. After this update, I checked that option back on for better results. Could be placebo though as difference is very slight.
[Sprint Samsung Galaxy S III] mw86:
Hmm thats weird those lines were deleted buddy and some changed can you show me pic what you mean I dont know which lines you refer to.
[Sprint Samsung Galaxy S III] galaxys3man30:
Reflash the rom buddy and see if thag fixs it n then do the build props mod I want to see what exactly what it could be

President of {Team Kernelizers}

Im Gman and I approve this message
[Sprint Samsung Galaxy S III] Maxamillion:
Good news guys I flashed back to the original build.prop and lag is still here meaning that it is not the build.prop, its just my ktweaker settings. I have gmans ktoons/noop 189/1350, uv 25 across the board and freq step at 8%. I guess my phone just doesn't like this setup too much. Its not as smooth as it should be..but then again this is a battery-saving oriented setup so this is expected.. But anyhow, thank you guys for your work. And to the rest of you, that "lag" you are experiencing most likely will be your setup.
[Sprint Samsung Galaxy S III] akarol:
Weird. Turns out that my Tapatalk app had crapped put and after trying to open it, it would crash and then now other apps would connect to their services when on WiFi.

I'll take some screening of the lines that you had me manually remove in the first version of 1.0.3 TKMod to show you that it is still there for me. Hold up.

---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------

These photos were taken using the build.prop Editor app from the PS.
[Sprint Samsung Galaxy S III] stas333:
I found the posts that deal with wake issues, but didnt see any solutions besides doing a full wipe. i have done that today and i am still having same issues.
[Sprint Samsung Galaxy S III] galaxys3man30:
What wake issue u having?

President of {Team Kernelizers}

Im Gman and I approve this message
[Sprint Samsung Galaxy S III] daniel4653:
I believe the alarm one
[Sprint Samsung Galaxy S III] iamikon:
After a full wipe you need to install apps one at a time to see which one is causing it ;)

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] galaxys3man30:
Like a alarm clock wakelock if so this is what needs to be done erase all alarms for the alarm clock n freeze it woth toolbox or tb n also freeze calender sync n anything to do with the calender amd then reboot if I'm thinking correctly that's all i did if see anything esle i did i will post

President of {Team Kernelizers}

Im Gman and I approve this message
[Sprint Samsung Galaxy S III] slickdaddy96:
You got to dump the alarm log into a text file and see what apps are causing the AlarmManager to run. Many apps use it to alarm the system to wake up and do whatever it needs to do.

From ADB on computer:

adb shell dumpsys alarm > AlarmDump.txt

From Terminal Emulator:

su
cd /sdcard
dumpsys alarm > AlarmDump.txt

Not really sure if the su is necessary or not. I had to dump it yesterday to see what apps were calling for it. It helped me out to Greenify the apps I didn't want running all the time calling Alarm Manager.

---------- Post added at 12:49 AM ---------- Previous post was at 12:47 AM ----------

The AlarmManager "Partial Wakelock" in BBS, isn't necessarily just the Alarm or an app calling for a reminder. It can be any app. I think the function is to wake-up the system or "Alarm" the system to wake-up. At least that is what I got from doing some research.
[Sprint Samsung Galaxy S III] galaxys3man30:
U are very correct buddy i just never got that in-depth with it lol but thanks for a more better explanation buddy

President of {Team Kernelizers}

Im Gman and I approve this message
[Sprint Samsung Galaxy S III] mw86:
Whatever your rom came with you should set it back to or restore your build prop before flashing the test build luis built for you :) use the function in the zip.

---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------

Thanks buddy good to hear so which has been better the latest build or the test one for lag.
[Sprint Samsung Galaxy S III] Maxamillion:
Just flashed the test one will report back

EDIT: the test one is definitely faster than the latest build in my particular case and setup. Good work you guys! Lag is practically gone! And on a battery oriented setup too! What did you guys change?? Seriously, the speed of the ui is just so fast.
[Sprint Samsung Galaxy S III] bso44:
I'm also seeing a definite improvement with the test build.prop tweaks.
[Sprint Samsung Galaxy S III] mw86:
THANK YOU :high five:

THANK YOU :high five:

Need a few more reports of one versus the other and will make changes more permanent and leave it like that next update coming soon. Fingers crossed :) im psyched guys very cool :)

---------- Post added at 04:05 AM ---------- Previous post was at 03:55 AM ----------

Here is what i posted in Verizon TK thread answering a question and talking ib general of our endeavours so Clankfu and Maxamillion its awesome to hear both your reports. This all has been to me the best thing I've been a part of in my life. It brings me joy and a sense of purpose to be apart of all this honestly the best part is knowing all you cool fellow Android enthusiasts.

Here is what I had posted there.

There is a latest zip for fix on aroma theme and a separate new test build to fix a few reported radio issue and lag. Its not many so trying to debug the issues. Here is build prop change log for it. Removed is from installer. Users should restore build prop with our option always before installing our newest zips with build prop changes. I elected to remove those props since it's strange any users had issues on radios on the props from before. Hopefully these fixes work or pan out to be there were other causes of the issues reported.

Change log build prop

Fix 5/1

dalvik.vm.heapgrowthlimit=64m

Changed from

dalvik.vm.heapgrowthlimit=224m

dalvik.vm.heapsize=256m

Changed from

dalvik.vm.heapsize=512m

dalvik.vm.heaputilization=0.25

Changed from

dalvik.vm.heaputilization=0.85

debug.mdpcomp.maxlayer=3

Changed from

debug.mdpcomp.maxlayer=2

ro.adb.qemud=1

removed

ro.config.hw_fast_dormancy=1

Removed

pm.sleep_mode=1

Removed

ro.ril.disable.power.collapse=1

removed

In any case im trying to get this resolved as quickly as possible as my goal as part of the team has been to provide one stop shopping for the smoothest experience possible through generic preferably universal build props and tweaks or any advice to gain a better user experience. The main thread started by my friend Gman whom compiled most of the advice discussed in three seperate threads about kt kernel between me and a few founding members of Team Kernelizers. Many participated there on the starts of it all and as this team and its combined knowledge grows we continue to document the findings and making a quick way to install the mods to get many of the tweaks we promote or use to gain a better experience. I am glad we have such an awesome team and followers. We should have the build props sorted very quickly and there's so much more to come with our mod.
[Sprint Samsung Galaxy S III] stas333:
The 2nd alarm (calendar) is usually at the top of the list, but for some reason Facebook is now also chewing up my battery.

---------- Post added at 07:06 AM ---------- Previous post was at 06:09 AM ----------

i have done that. freezing the calendar storage removes the wakelock, BUT this also prevents calendar from working, even if i download other calendars from the market. I actually use the calendar quiet a bit, so i definitely need it.
[Sprint Samsung Galaxy S III] prboy1969:
So here are my finals for gman / mw86 setup first tun. Now a few things to note. I did not use noop, as my device was not liking it. I only used it for screen off. The main governor was SIO. Also my Min / Max was different. Details below.

Min: 81mHz

Max: 1728mHz

Governor: SIO

Screen off: noop

UV: 50 across the board

DS Battery Saver - set on strong

No data toggling

Syncing set to everyday settings

EDIT: All results are on 7000mAh ZL

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] stas333:
nice results! are you on the extended battery? if so, which one?
[Sprint Samsung Galaxy S III] akarol:
Where can we find this newer test build you speak of?

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] iamikon:
The 1.03-test? I think its the same one you already used but it's always good practice to read the last few pages of the thread cuz that's where its pasted ;)

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] galaxys3man30:
Lol maybe

[Team Kernelizers]

jellybombed sgs3/Ktoonzs kernel/Tweaked Ktoonsnative and I/O BFQ http://xdaforums.com/showthread.php?p=35101228
[Sprint Samsung Galaxy S III] GTOJim:
You and me both..
[Sprint Samsung Galaxy S III] galaxys3man30:
Wow its quite today

[Team Kernelizers]

jellybombed sgs3/Ktoonzs kernel/Tweaked Ktoonsnative and I/O BFQ http://xdaforums.com/showthread.php?p=35101228
[Sprint Samsung Galaxy S III] castle_bravo:
Yea I thought the same thing. I'm testing no 3g usage and Wi-Fi when I need it, like now, and I'm getting stellar results with light usage. When I drain out I'll post stats and then do a run with 3g enabled the whole time and do the same

sent from rooted stock freeza's deodexed lj7
[Sprint Samsung Galaxy S III] galaxys3man30:
Sweet lets us know

[Team Kernelizers]

jellybombed sgs3/Ktoonzs kernel/Tweaked Ktoonsnative and I/O BFQ http://xdaforums.com/showthread.php?p=35101228
[Sprint Samsung Galaxy S III] galaxys3man30:
Ok guys here is my rom yall take a look if yall want too im still not done yet thou still got to theme it

http://db.tt/ic8zatDG

[Team Kernelizers]

jellybombed sgs3/Ktoonzs kernel/Tweaked Ktoonsnative and I/O BFQ http://xdaforums.com/showthread.php?p=35101228
[Sprint Samsung Galaxy S III] clothednblack:
That won't work for us cellular, right?

Ridin the Mystic jellybean unicorn on my Ktweaked SG3
[Sprint Samsung Galaxy S III] galaxys3man30:
Naw buddy it wont if rompnit can get TPR working for you maybe I can see if he can do mine as well

[Team Kernelizers]

jellybombed sgs3/Ktoonzs kernel/Tweaked Ktoonsnative and I/O BFQ http://xdaforums.com/showthread.php?p=35101228
[Sprint Samsung Galaxy S III] clothednblack:
I sent him everything he needed, its going to be a while, he has been really busy and I totally understand, so I'm patient and just enjoy everything else that is compatible lol

Ridin the Mystic jellybean unicorn on my Ktweaked SG3
[Sprint Samsung Galaxy S III] 02bugeye:
So not sure why it seems to be working now but mw I/o tweaks are sticking and no ktweaker pop up. I've rebooted a couple times made sure everything loaded up after boot went into ktweaker and no pop up and settings are all there. In Rom toolbox I have governor to apply at boot and also cpu to apply at boot. Also made a back up of my settings in ktweaker. I'll keep and eye on it and see if the pop up stays away.
[Sprint Samsung Galaxy S III] Chinkybean:
+1 after I just went ahead and said yes all is good.
[Sprint Samsung Galaxy S III] GTOJim:
Reinstall did not help, JD isn't turning data on and off. I"ll have to re-flash a rom, I thought it might have been due to disabling Sprint Optimizer but JD still didn't work after enabling the Sprint Optimizer.
[Sprint Samsung Galaxy S III] clothednblack:
Did you clear cache and data in app manager then uninstalling and make sure the folder was also deleted in file manager?

Ridin the Mystic jellybean unicorn on my Ktweaked SG3
[Sprint Samsung Galaxy S III] GTOJim:
No I did not, good tip, If there is a next time I will, to late now.
[Sprint Samsung Galaxy S III] sparkie172:
Well here is my best run so far only first charge after reinstalling ROM and last update of kt747.

Still not happy with how fast battery is dying. Only a little use and can lose a percent just with the screen on. I dimmed it to lowest setting. Gonna get lux app when I get some extra $ so I can set up screen in sub zero brightness
[Sprint Samsung Galaxy S III] mw86:
That seems pretty good with out lux and stock battery looks like your were you should be especially if you were using phone normally.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] fluk321:
Details?

What does this do? What is this ROM about?, I flashed and it bricked my Sprint Gs3. And yes I do know how to flash, I dont need to be asked if I wiped this or that.
[Sprint Samsung Galaxy S III] steelers_exe:
I was just about to say, seems pretty good for normal use. The best I've gotten recently is about 14 hours with like 3 1/2 hour screen on time.
[Sprint Samsung Galaxy S III] mw86:
Sadly Eugene doesn't respond to emails. I tested on my AOSP rom, app description says it doesnt work on CM9,CM10 or aosp/aokp. It if isntalled runs its service and appears to run at right times but is non functional. Maybe someone can test on Touchwiz but this app on the above does not work and is a waste of money just appears to do something. App description says custom kernels can be an issue. The user on Touchwiz with cpu sleeper i implore you to test it so know one buys it if its actually a waste of money. If i go to touchwiz soon ill test myself. Also mpdecision has no noticable impact either.

Cpu sleeper on for all pics and stability test

Mpdecision off screen on

Mp decision off screen off awhile

Mp decision on screen off awhile

Mp decision on screen on

Again if i use a touchwiz rom soon i will attempt the exact same tests. This was the only way at all i found to determine true core two behavior on screen off using Trepn profiler.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 05:50 PM ---------- Previous post was at 05:48 PM ----------

All i know right now is this is Jelly Bean Touchwiz rom. Galaxyman needs to post it in a thread to be able to describe whats in the rom and start support for the rom. Please give us link to such new thread/post when you have time galaxys3man30.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] bso44:
Would you mind sharing your settings for SIO?
[Sprint Samsung Galaxy S III] akarol:
I assumed he was talking about an even newer build. Apparently the last 3 lines he mentioned on his last post are still present on my device.

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] iamikon:
Ahh I see. Did you restore your original build prop? If so then your ROM uses those lines so you have to do that manually. Or reflash your rom without wiping data just to make sure. so maybe in the next test we can have the script remove them?

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] chui84:
Thanks

Thanks alot man,really helped just flashed Hyperdrive myself with ktoonz doinf much better with mw86 tweaks the second ones,the fast ones worked just lagged a little bit on my SG3
[Sprint Samsung Galaxy S III] bso44:
For future reference, please don't quote the entire OP or a similarly long post. It makes scrolling a *****, especially on a mobile device.
[Sprint Samsung Galaxy S III] ryandubbz:
Lol scrolling is a lot easier now with your latest build prop tweaks smooth as butter
[Sprint Samsung Galaxy S III] thegame2388:
Is disabling mpdecision still a requirement? Do we still need to flash the zip?
[Sprint Samsung Galaxy S III] mw86:
If using kt747 kernel yes because autohotplug is an option or using a hotplugging governor, of which both will do better than mpdecision ever did.

---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------

Prboy is talking about me and gmans ktweaker backup in box account and in latest tkmod zip.
[Sprint Samsung Galaxy S III] prboy1969:
Inhave the good fortune of owning a ZERO Lemon 7000mAh Battery. Thanks to an awesome member who donated it to me :D . THANK YOU :). You know who you are.

The settings are below. As well as the gman / mw86 modified KTweaker file.

async_read_expire async_write_expire fifo_batch sync_read_expire sync_write_expire writes_starved

50 1250 1 50 1250 2

http://db.tt/X7T8bTpb

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] bso44:
Thanks. Looks like TouchWiz doesn't allow you to have noop for screen off if you're running SIO. Mine wouldn't stick after turning my screen on and off.
[Sprint Samsung Galaxy S III] akarol:
I'm getting confused! :silly:

These lines are to be implemented manually on the newest 1.03-test build.prop or are they already implemented? In any case, I reverted back to stock build.prop via the TKMod-test, rebooted, then I reverted to the TK-test build.prop again via the TKMod-test and rebooted again.

Using build.prop editor from PS, I searched for the lines you mentioned and this is what I found:

dalvik.vm.heapgrowthlimit=64m

Changed from

dalvik.vm.heapgrowthlimit=224m

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=256m

Changed from

dalvik.vm.heapsize=512m

dalvik.vm.heapsize=256m (2 lines of this code)

dalvik.vm.heaputilization=0.25

Changed from

dalvik.vm.heaputilization=0.85

dalvik.vm.heaputilization=0.25

debug.mdpcomp.maxlayer=3

Changed from

debug.mdpcomp.maxlayer=2

debug.mdpcomp.maxlayer=3

ro.adb.qemud=1

removed

ro.adb.qemud=1

ro.config.hw_fast_dormancy=1

Removed

ro.config.hw_fast_dormancy=1 (2 lines of this code)

pm.sleep_mode=1

Removed

pm.sleep_mode=1

ro.ril.disable.power.collapse=1

removed

ro.ril.disable.power.collapse=0

Basically, the top portion of code seems to be on par with what needs to be there (TKmod modified those lines appropriately). The bottom 4 lines of code are still present (TKmod did not remove those lines). It's inline with what you said.

Now, this bring up some questions:

1. Is it normal to have multiple identical lines of code like it's shown in my build.prop? Should I leave the 2 lines of heapsize alone?

2. Which app do you recommend to remove these lines (ES File Explorer) doesn't seem to be able to save the modified build.prop.

3. Should I remove both lines of the fast_dormancy line?

Thanks in advance guys! You all rock! :cowboy:

---------- Post added at 04:46 PM ---------- Previous post was at 04:06 PM ----------

Crap! I just realized there is a TKMod1.03v2 and a TKMod-Test. Any difference between the 2?
[Sprint Samsung Galaxy S III] luis86dr:
Test has changed build props to see if it helped with lag, which some users reported it did. So it will more then likely be final. I'm currently running the test build prop and seems great.

As far as your questions,

Never normal to have double build props, but make sure the doubles aren't commented out. You can open terminal emulator and type:

cat /system/build.prop

And review the list. Maybe you can also try mounting system as rw to see if that let's you edit your Build prop to save changes.

Run :

mount -o rw,remount /system