yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] brandoncarlson33:
I'm on aosp liquid ROM 5/10 kt5/9 they went so fast not sure what they were

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!

---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------

Will try again in a few and let ya know if I can catch them

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] luis86dr:
What selections did you make in aroma

Also check md5 on download to make sure it isn't a bad download..

Md5: fc882c277f426f029c65821010e01a90
[Verizon Samsung Galaxy S III] brandoncarlson33:
Did it again and there was a few again but finished this time so idk wth lol

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] brandoncarlson33:
Here's a pic of the errors

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] TheDriller:
^ This.... Omfg Lmfao...

Is your ROM still there?:eek::eek::eek:

I hope it didn't mess something up...

That would be ţęŗŗįblę!!!! :D
[Verizon Samsung Galaxy S III] Gordo1603:
That's great!
[Verizon Samsung Galaxy S III] tprophit:
When you say restore build prop, do you mean the stock one prior to flashing tkmod?

The one I just loaded that you all helped with, someone, I thought, said I'd be good to go with future tkmod updates?

Clarification appreciated.

Thank you.
[Verizon Samsung Galaxy S III] brandoncarlson33:
So all is good I take it??

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] luis86dr:
Thats normal. Just a joke REick placed in updater script since SED was being a pain.

Lol. That script is going to get us in trouble.:p

Yes, but with the new verification system I would restore original build prop and then flash new version. In your case keep a backup of your current build prop and just edit the modified build prop after you flash 1.0.4. That way all necessary files for verification system is installed.
[Verizon Samsung Galaxy S III] MorphiousGX:
I'd say don't upgrade yet. If you do want to try, you have to make a back up of the one you currently have (the new one rerick gave you) just in case.

---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------

The errors you saw were a joke Rerick added initially. LOL I can see where it might mess people up.

You're fine, unless you saw other issues?
[Verizon Samsung Galaxy S III] brandoncarlson33:
Haha jokes on me then last time I seen a fatal error my laptop **** the bed lol thanks again you guys are the ****!!!!

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] luis86dr:
Okay, going to try and explain again to sum up everything into one post about the new "Verification System" I implemented.

When flashing the new 1.0.4, a new directory will be created. Within this directory you will find a file called "TKBP". What "TKBP" does is specify wether or not your build.prop has been modified by our Aroma Installer or not. The values will show as follows within the "TKBP" file:

0 = Unmodified build prop by Aroma

1 = Modfied build prop by Aroma

This is where the verification kicks in. In my coding I have it check "TKBP" for either "1/modified" or "0/unmodified".

So for sake of example, If 1.0.5 was released with a ton of new build prop tweaks, this will save you the hassle of having to restore your original build prop, then loading up Aroma again to flash newly modified build.prop.

If Aroma detects that "TKBP" = 1. It will restore your original build prop for you, and install newly modified version for you all in one session of Aroma.

Else, if its unmodified (0), it will apply it normally.

The reason I'm asking you all to restore your original build.prop is so the files required are implemented into your systems. Once this is done, it will not be needed ever again. Once a new version of TK Mod is released with build prop changes, just flash them in Aroma and it will do the proper install for you.

Restore setting in Aroma will be left for the people who want that option available, but remember! IT IS NOT NEEDED WHEN UPGRADING BUILD PROP AFTER 1.0.4.

If your still confused on this, then feel free to ask questions. But this should be pretty simple to understand. :)

Also, with the SYSCTL mod.

MW and myself have worked on this today trying to fix a issue he was having where the system would collide with our settings on boot. Basically, these settings reset on every reboot.

So what we did was make use of init.d (aint it great? ;)) and have it set at boot automatically. Problem is on some ROM's it will try to load the "default" values at the same time as our init.d script kicks in, which will basically override our settings. So I set a 45 second delay which should give more than enough time for the system settings to kick in, and then our init.d settings to load up normally.

You can reference all file attributes changed by navigating to "/system/etc/TK/TK-SYSCTL". Open that file with a text editor, or you can do the following from terminal emulator:

su

cat /system/etc/TK/TK-SYSCTL

This will display a list of "Before" and "After" settings so you can see what exactly was changed.

So once again, feel free to ask questions guys. Im open for discussion.
[Verizon Samsung Galaxy S III] TheDriller:
Lmao. Yeah getting sed to work right messed with me for about 2 weeks. So I wanted to mess with everyone who made my life hell. Glad you liked it:) it is just a joke though lol
[Verizon Samsung Galaxy S III] mw86:
New sys ctrl designed to not interfere with other mods so it is fully compatible with crossbreeder as all of our stuff has been.
[Verizon Samsung Galaxy S III] tprophit:
Ok...so what would I take from the one RErick gave me and add to the new one? What would I take out of the new one?

Sorry if this is a dumb question, still trying to understand all this.

Thank you.
[Verizon Samsung Galaxy S III] luis86dr:
The build prop hasn't changed so basically in your case do as follows:

1. Make a copy of your modified build.prop that rerick gave you and save it in a different directory.

2. Load up prior TK mod and restore Build Prop.

3. Flash TK Mod 1.0.4 and install new Build.prop

4. Once booted up, locate the build prop you copied into a different directory over in step 1. Open that with a text editor and copy all of the contents inside.

5. Now that you copied all of the contents, navigate to /system/build.prop and open it up. Delete everything within it and paste over your copied props. Save and you should be now good to go.
[Verizon Samsung Galaxy S III] TheDriller:
Actually, here are the lines that you are going to want to remove from your Build.prop. These lines are GSM specific and I am not exactly sure how they ended up on an AOSP ROM that was built for a CDMA carrier. Anyway, if you are on Carbon or any other ROM for that matter and are experiencing radio issues AND are on either VERIZON or SPRINT Then make sure that these build.prop lines are NOT present in your build.prop, these are GSM specific

#MOAR Props
ro.config.multimode_cdma=1
ro.config.combined_signal=true
ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000

#Additional Build.Props
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.cdma.subscribe_on_ruim_ready=true
[Verizon Samsung Galaxy S III] Stranger_84:
# Moar ril props

persist.radio.snapshot_enabled=1

persist.radio.snapshot_timer=22

ro.config.multimode_cdma=1

ro.config.combined_signal=true

ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000

DEVICE_PROVISIONED=1

persist.eons.enabled=false

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.ril.hsxpa=1

ro.ril.gprsclass=10

persist.sys.usb.config=mtp

ro.hwui.text_cache_width=2048

persist.radio.add_power_save=1

persist.radio.snapshot_disabled=1

ro.vendor.extension_library=/system/lib/libqc-opt.so

com.qc.hardware=true

persist.radio.apm_sim_not_pwdn=1

ro.telephony.call_ring.multiple=0

ro.sf.lcd_density=320

Found this in my ROM should I delete certain lines or just ignore all this moar talk lol
[Verizon Samsung Galaxy S III] TheDriller:
Just delete these lines and anything following them:

ro.config.multimode_cdma=

ro.config.combined_signal=

ro.gsm.data_retry_config=max_retries=

ro.ril.hsxpa=

ro.ril.gprsclass=

ro.cdma.subscribe_on_ruim_ready=

Reboot your device

And all your radio issues will magically dissappear:D
[Verizon Samsung Galaxy S III] tprophit:
So, delete those lines from original BP. Run 1.0.4, and all should be good?

I was advised to do this, then add back the BP you gave me yesterday, which, if I do that, it seems I would miss any of the new changes in 1.0.4.
[Verizon Samsung Galaxy S III] luis86dr:
Build prop wasn't changed in 1.0.4, just the coding that installs it.
[Verizon Samsung Galaxy S III] tprophit:
Ok, made these changes to orignal build prop. Went reboot phone...get the Ktoonz splash, then nothing...

Suggestions?

****...won't even boot into recovery....

several battery pulls later...booted into recovery. wiped dalvik and cache. attempt to reboot failed.

Doing advanced restore, system only, of a 44 hour old nandroid.
[Verizon Samsung Galaxy S III] TheDriller:
Fix permissions in recovery
[Verizon Samsung Galaxy S III] tprophit:
I am back to the original build.prop.

What do you think of flashing 1.0.4, then, if modem issue presists, replace whatever buildprop is there with the one you gave me yesterday (or late Fri)?

Thanks.

---------- Post added at 08:11 PM ---------- Previous post was at 08:06 PM ----------

Or, should I replace original BP with the edited on again, wipe cache, dalvik, and fix permissions, then do the above?

Thank you.
[Verizon Samsung Galaxy S III] TheDriller:
That would be okay. But the lines I posted to delete above are the same ones I removed from your build.prop the other day. You may have inadvertently deleted something else by mistake
[Verizon Samsung Galaxy S III] Stranger_84:
I deleted em, rebooted and everything is working great .... Thanks
[Verizon Samsung Galaxy S III] tprophit:
Trying this now: What do you think of flashing 1.0.4, then, if modem issue presists, replace whatever buildprop is there with the one you gave me yesterday (or late Fri)?

Easier for me to keep track:)

Thanks.
[Verizon Samsung Galaxy S III] TheDriller:
That would be fine
[Verizon Samsung Galaxy S III] tprophit:
Ok, with original, unmodified BP, flashed 1.0.4.

Had the Wifi issue, as expected.

Replaced with the BP you gave me.

Rebooted.....and nothing......

rebooting into recover, wiped cache, recovery, and fixing permissions.

And...that didn't work.....

I'm stumped....

---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------

Only difference is, I moved copy of file you gave me, as opposed to copying into original BP...

...And ticked the SYSCTL mod.option
[Verizon Samsung Galaxy S III] luis86dr:
Make sure build prop permissions are set to 644 after you've edited it.
[Verizon Samsung Galaxy S III] TheDriller:
Yeah if you didn't copy it directly INTO the original build.prop you would have had to set permissions. So with the original build.prop delete everything inside of it and copy new build.prop lines into the original file so you don't have to set permissions again
[Verizon Samsung Galaxy S III] tprophit:
Got it.

Here goes....standby...
[Verizon Samsung Galaxy S III] TheDriller:
Permissions should be rw- r-- r--
[Verizon Samsung Galaxy S III] tprophit:
Thanks guys, for all the help.

Sorry I'm so slow at some of this stuff. In retrospect, it was the lack of correct permissions to the various BP files that were moved around.

So, here's what I've done:

F'd up the edits to original BP.

Restored to original BP

Flashed 1.0.4.

Replaced the BP that had the baseband 'unknown' with the BP from RErick.

All now appears to be good, AND I have 1.0.4 installed.

One last question; until 1.0.5 comes out, if I flash another rom revision, I have to go thru this process again, correct?

Thank you all again for the help.
[Verizon Samsung Galaxy S III] TheDriller:
Data working correctly?
[Verizon Samsung Galaxy S III] tprophit:
Yes, as is GPS and 4g.

Speaking of,GPS, used it today, it was definitely lagging my actual position (driving at 25 MPH). First time that's happened, will keep an eye on it this week....
[Verizon Samsung Galaxy S III] MorphiousGX:
tighten up the screws on the back of the phone below the battery cover. It does wonders
[Verizon Samsung Galaxy S III] tprophit:
No kidding....got about 1/8 to 1/4 turn on all but 3 of them ....
[Verizon Samsung Galaxy S III] brandoncarlson33:
Just got the no data /WiFi issue after reboot booted into recovery and reflashed 1.0.4 but choose restore on everything now all is well will try next update and see what happens (sorry Team)

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] TheDriller:
Delete those lines I specified earlier and all should be well
[Verizon Samsung Galaxy S III] mw86:
Luis and I removed the last and only offending line from the mod tonight and when he has time he will have it made and posted. So im sure if you check in tommorow we will have the version up by then.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Wow couple mins after I posted, You guys are fast!!!!!!! Will keep checkin thanks for the reply Team keep up the good work!!!

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] luis86dr:
Update:

TK-Mod-Beta-1.0.4-Rev1

Download: http://db.tt/nCGqNPJ5

Changes:

Removed GSM specific props within build.prop. Hopefully this solves this god forsaken wifi issue.

For those of you who flashed prior 1.0.4 version, no need to restore it will do it for you. But to be on the safe side, let's make sure your build.prop has been modified by us.

Here is a tool I've been working on, which is still being worked on but for the sake of people not getting confused I'll release a small version of what I plan to implement.

Download this: http://db.tt/SnGch92j

As you will see it will be a file named "TK".

Now what you want to do is open terminal, and change directory to where that file is placed. So for example, you would type something like this if the file is saved in your downloads folder in SdCard:

su

cd /sdcard/download

Once you see that the directory has changed, type the following:

sh TK

You will now get a selection menu where you can choose to verify your build.prop. Please do so before flashing. Thanks.
[Verizon Samsung Galaxy S III] Mystique:
Hey all,

Just wanted to say thanks for this thread..

Just got the wife a GS3 because she was so unhappy with her rezound..

But before this thread she was hating the GS3 as well..

Thanks for all the mods and directions in the box.net links..
[Verizon Samsung Galaxy S III] savagebunny:
So I don't know why I waited till now, or I just realized what my build.prop consisted of... but I had those same GSM lines and my phone was working fine, all DATA modes, WiFi, GPS, AGPS etc
[Verizon Samsung Galaxy S III] TheDriller:
Its hard to say why some peoples phones work with it and some don't. I don't have that answer. Best thing I can say is that no 2 phones are alike and no 2 ROM installations are the same either
[Verizon Samsung Galaxy S III] savagebunny:
This is why I've been saying certain phones get better battery life with the same setup. I've seen guys with VERY similar builds. Guys have gotten 12-13hrs battery life with the ZeroLemon and I max out at about 9hr 30min or less most of the times.

So as back with the first Inc, Thunderbolt everybody had the same rom as me, kernel, tweaks, and speed settings and we get give or take 15-30min screen on time and 1-2hr battery life time. These phones are quite different. Must be the manufacturing process Samsung has going, maybe found a cheaper way putting these together thus maybe affecting revision batches.

Kinda like overclocking with CPU's from Intel, certain batches can run high GHZ with low voltage, and some require more voltage as the same GHZ of the top clock.
[Verizon Samsung Galaxy S III] TheDriller:
That's gotta be screen time because I usually average about 11 hours screen time and 3 days off charger
[Verizon Samsung Galaxy S III] murayoshi:
Hi guys, sorry for the bother...I flash synergy r484 and kt dated 5/3 what is the your recommended file for ktweaker to save battery...thaks in advance
[Verizon Samsung Galaxy S III] keynith:
REricks usually on point with his mods. Test different ones and see what works for you. There is no "one size fits all". Every phone is different, even when your running the same ROM/Kernal as someone else.
[Verizon Samsung Galaxy S III] mindflayyer:
You need to type sh TK.txt

(Or at least I did to get it working)

Newest TKmod confirmed working on carbon nightly 5/12 on d2vzw. All hail the KERNELIZERS! :D

Swyped from my kernelized carbon
[Verizon Samsung Galaxy S III] TheDriller:
I'm still "testing" my extreme setting. Pretty happy with it so far and have been working on porting The Peoples ROM to ATT, so I've been away from tweaking for a couple of weeks. Got some new ideas I wanna try out and see what you guys think. But for now its the extreme setup
[Verizon Samsung Galaxy S III] brandoncarlson33:
All done all seems to be well so far will let ya know if anything comes up thanks again Team your the best!!!!

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] mw86:
Your welcome, glad to be here and help. I appreciate your post in the Ktoonsez kernel as well. Thank you.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Your very welcome!!!!

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] tprophit:
Did this, first doing the TK test, and confirmed that my build.prop had been modified by you. (it is the one RErick gave me Friday.

Next, flashed 1.0.4 rev 1.

Still have baseband = 'unknown'.

copying the RErick buildprop...

Thank you
[Verizon Samsung Galaxy S III] mw86:
Well rerick may have some advice. I have all the lines out. Now I am thinking the install is putting a harmless line in but the location of the prop may be effecting it, i am not certain. I am in meaning the section at top of prop maybe modifying up there is bad? Rerick any advice. This new build works on brand new phone so its hard to say why this is coming back again. Please use 104 rev1 again and post the build prop as is that again causes the unknown. The information has to be in front of us and this would be only way we can help. I hope you don't mind providing that in your free time?
[Verizon Samsung Galaxy S III] TheDriller:
No problem at all. Just attach it to the thread or post it in a spoiler
[Verizon Samsung Galaxy S III] tprophit:
Re: [Team Kernelizers][H To][VZW][TK Mod 1.0.2]KT747 Kernel Tweaks - Updated 4-15-13

Will do. I assume you mean the BP file that is there immediately after 1.0.4 ver 1?

What's that command for converting to text? Will try now.

Never mind, can use wordpad on desktop. Stand by...
[Verizon Samsung Galaxy S III] TheDriller:
Just copy and paste
[Verizon Samsung Galaxy S III] tprophit:
Here you go. Thanks
[Verizon Samsung Galaxy S III] TheDriller:
I can't stress enough how bad it is to have gsm build.prop lines in a CDMA handset. This is not good. Verizon will see this as it spams our network with handsets trying to subscribe with a gsm signal. Please don't do this. Also I don't know where devs are getting the idea that its good to have CDMA ready on RUIM. WE DO NOT HAVE A RUIM ON THESE PHONES!!! I posted information regarding RUIM several times in multiple threads over the last several months but no one cares.
[Verizon Samsung Galaxy S III] TheDriller:
Here is is again in case you all missed it

Removable User Identity Module (R-UIM) is a card developed for cdmaOne/CDMA2000 ("CDMA") handsets that extends the GSM SIM card to CDMA phones and networks. To work in CDMA networks, the R-UIM contains an early version of the CSIM application. The card also contains SIM (GSM) application, so it can work on both networks. It is physically compatible with GSM SIMs and can fit into existing GSM phones as it is an extension of the GSM 11.11 standard.

This interface brings one of the main advantages of GSM to CDMA network phones. By having a removable identity card, CDMA users can change phones while keeping their phone numbers by simply swapping the cards. This simplifies many situations such as phone upgrades, phone replacements due to damage, or using the same phone on a different provider's CDMA network.

The R-UIM card has been superseded by CSIM on UICC. This technique allows all three applications (SIM, CSIM, and USIM) to coexist on a single smartcard, allowing the card to be used in virtually any phone worldwide that supports smart cards.
[Verizon Samsung Galaxy S III] tprophit:
If this is the same as what you gave me Friday, it's what's in there now. It was what was in there when I flashed 1.0.4 rev 1.

To reiterate, I downloaded 1.0.4 rev 1, and, the verification tool.

Verified that the BP had been modified. (It was the exact BP you sent).

Flashed 1.0.4 rev 1. Rebooted. Had baseband unknown. Copied what you gave me Friday and rebooted. There was great rejoicing, as all was good.

Sent (posted) the BP that was on phone immediately after flashing 1.0.4 rev 1.
[Verizon Samsung Galaxy S III] TheDriller:
Its essentially what I gave you on Friday but slightly different. I just removed the same lines that I did before
[Verizon Samsung Galaxy S III] tprophit:
So paste this, reboot, and should be good.

I shall call this RErick rev. 1...

Thank you.
[Verizon Samsung Galaxy S III] TheDriller:
Yes. Actually Delete, Paste, Reboot, Profit :D
[Verizon Samsung Galaxy S III] tprophit:
Done.

Baseband correct. Wifi working. 4g, and GPS working.

Since I have already flashed 1.0.4 rev 1, and now replaced that build prop with this one, am I ok to go for future releases?

Thanks again for all your help.
[Verizon Samsung Galaxy S III] TheDriller:
Yes if you keep that build.prop that I gave you there
[Verizon Samsung Galaxy S III] tprophit:
RErick rev 1? Have it saved ....
[Verizon Samsung Galaxy S III] TheDriller:
Op updated
[Verizon Samsung Galaxy S III] tprophit:
Regarding the file renaming, I always rename mprecision, and # it in post boot file. The only other file on my phone of the group is smd. What does that file do?

Thanks.
[Verizon Samsung Galaxy S III] brandoncarlson33:
My battery stats since the new mod!!! Thanks team, awesome stats

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] Addiso:
What setup you running?
[Verizon Samsung Galaxy S III] brandoncarlson33:
Ktoonservative/noop mod aosp with the new tk1.0.4 rev1 on ktoonz 5/9 kernel on liquid smooth nightly 5/10 with the new vrbmb1.aio.zip

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] Wi1son:
Are there any foreseeable issues with re - flashing TK Mod after dirty flashing a ROM update? Carbon in particular. Thanks.

Sent by i535 with CarbonROM & KT747
[Verizon Samsung Galaxy S III] prboy1969:
RErick just caught sight of the New OP. Looks great man. Nice job :good::good::good: