yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plaut:
> su
> cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
1512000
> echo 1080000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
> cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
1512000

It's possible it's some interaction with ktweaker. Interestingly, I had no problem setting scaling_governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
OH!! it's probably cause it's hotplugged and turned off when you try to write to the file, turn on a benchmark app, or other intensive application to be sure it's running cpu1.

you can't read the file when it's hot plugged, i am not sure about writing the file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plaut:
Perhaps, but when cpu1 is off the entire cpufreq directory vanishes, so I shouldn't have been able to write to scaling_governor nor to cpuinfo_max_freq. Also, I used the boot script (when both cpus are busy) to set both scaling_max_freq and scaling_governor but only the latter stuck, whereas if I use cpuinfo_max_freq they both stick.

Not that it matters....too early to tell for sure but battery life seems better......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
u0_a45@android:/ $ su

u0_a45@android:/ # sh /sdcard/1080mhz-asswax.txt

/sdcard/1080mhz-asswax.txt[5]: can't create /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq: No such file or directory

/sdcard/1080mhz-asswax.txt[8]: can't create /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor: No such file or directory

1|u0_a45@android:/ #

This is what I'm getting. Am I running the script wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Might need to disable mpdecision or auto hotplug or w/e for those files to exist
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I tried renaming mpdecision to mpdecision.bak, rebooted, tried again and I still got the same message.

Would auto hotplugging mess anything up when I'm using a hotplugging governor like ktoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jacqstrap:
I have applied your settings last night and have fully charged. Discharged from USB cable this morning at 7:00AM and am at 100% still. Will tell you how it goes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
That could be it, try setting the parameter disable_hotplugging to 1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Thats what ive done when kt told us all about it. Not really a way to be sure ypu can set those unless that option is set then turn it off again

You cant set those files unless core two stays on the whole time... Thats what baconatorXVI has been getting at in his directions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
You named it .txt

delete .txt off the end. That may do it.

Did your root explorer name it this? Or did you?

I only got this error when terminal didn't have super user perm's. Perhaps I wasn't hot plugging Amgen my script ran

Try running a benchmark app in the background maybe.

Also verify terminal emulator is actually getting root. Use the cd command to see what directory. Should say /sdcard at first. Hit / to try and go up a directory to root. That's if I remember my commands correctly that is...

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Well I'm leaving the country and XDA for awhile, so you guys have fun playing with your settings, I can't wait to hear how it's worked for you guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jacqstrap:
I applied your settings and followed your method to increasing battery life. I was not able to install PerfMon onto my phone for reasons unknown. Install was unable to be tapped on for some unknown reason. With that being said, I do not know if I correctly ran the terminal emulator/scriptmanager correct, but according to the terminal emulator it was able to locate the 1080mhz text file you gave us to download.

I did a few things differently today. For one, I downloaded Greenify and hibernated a large amount of apps (including Facebook, Twitter, Instagram, Snapchat). I think by hibernating Facebook I removed a very large wakelock from my phone. From doing that, that might have increased battery life on top of your settings, so distinguishing if using the method you gave me now made any difference from what I did with your old settings last time.

I also turned off mobile data and wifi for about an hour today because I was in an area with little to no reception/a very weak wifi signal.

I would rate my usage light-moderate to moderate. If I stayed out more today it would have been moderate-heavy usage and I probably would have died around 8 or 9 pm.

LONG STORY SHORT, I was able to reach almost the same time of the phone on battery than my last post (about 15 minutes short) but was able to squeeze about 1 more hour of screen life than my last post (which only had 2 hrs and 30/40 minutes) and finished the day off at 11pm with 10% left. Better than last time for sure!

Without further ado, here are my results for today:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey guys I just had a thought, I bet screen off settings will mess with whatever you do to cpu1... like maximum/governor.

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
It could bud because they won't be restored to what was custom set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Can't you use tasker to run the scrypt every time the screen turns on?.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I finally had time to test this out!

The CPU1 settings from the script are not affected by the screen off settings of ktweaker.

CPU0: ktoonservative(modified tunable) 81-1890mhz

CPU1: conservative( stock tunable) 81-1890mhz

Everything run smooth, cpu1 is less inclined to ramp up rapidly, is more frequently on lower freq and go offline faster than interactive. I didn't notice more lag than with interactive.

I can't say much about the difference in battery life yet but I'll keep you informed.

Thank you for your time and effort baconator :beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
When copying the settings do I need to have it formatted the exact same way? I keep putting it in editor but it brings it together
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Download the txt, move it into the folder /sdcard/ktweaker. Once that has been done, open ktweaker and select restore prefs from sdcard. The file option should be there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Sorry, every time I click on it, it opens up with text in my browser (stock,chrome,fireforx) on my sg3 I can copy the text, but of course when I put it into a file all the spacing is off (I didn't know if that would effect) ktweaker pulling in the settings. thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Try this..

https://www.box.com/s/6jsfkpiywux9bgvuapac
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
thanks a lot. that worked for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Anyone know good settings that's good for battery without heat issues? Also decent for performance. I'm running MIUI V5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
The settings I'm testing look promising. I'll keep you informed :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Looking forward to hearing them!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Same here ive been looking for good settings for awhile. Heat is an issue for me cus I'm using an otter box armor case and its hard to get off all the time for battery pulls
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Can't wait to hear if you've found improvments! it's been better for me from what I've seen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I need some testers for my cpu1 settings. I tweaked cpu1 to use conservative and did some changes in the conservative's tunable. I mostly aiming for battery life and to keep most of the charge on cpu0( using ktoonservative for me but you can use your own preferred governor) while CPU1 stays on lower frequenciesand ramp down quickly.

This is a very conservative setting so you will notice some lags. What I want to know is if your battery life seem to increase with light usage of the phone (ex:work or going out). I'm currently testing something else without conservative that may be a good in between.

Here is the script: http://db.tt/Lz32rTsf

Here is my ktweaker backup with my ktoonservative settings if you want to try it. You can also not use it(voltages are stock, 378-1512): http://db.tt/KSiOQoPK

Use Baconator's method to run the script: http://xdaforums.com/showthread.php?p=41663912

Apps I use to test and benchmark:

https://play.google.com/store/apps/details?id=com.quicinc.vellamo

https://play.google.com/store/apps/details?id=eu.chainfire.perfmon

https://play.google.com/store/apps/details?id=net.bsayiner.benchmark.SuperPi

I hope I'll get some feedbacks from you guys :beer::D

Conservative script:

echo conservative > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 50 > /sys/devices/system/cpu/cpufreq/conservative/down_threshold

echo 3 > /sys/devices/system/cpu/cpufreq/conservative/freq_step

echo 60000 > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate

echo 90 > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
After some tweaking, asswax seems to be a very good in between for conservative and interactive on cpu1. If you could test both my conservative script and asswax script and give some feedbacks, that would be great.

Cpu1asswaxscript: http://db.tt/qoNfLT6C

Refer to the post above for more explanations.

Script

(adjust awake_ideal_freq, sleep_ideal_freq and sleep_wakeup_freq to fit with your min freq):

asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 189000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 2000 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 486000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 90 > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 60 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 540000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 189000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 30000 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
My settings

Locked Frequencies

CPU (MIN): 189mhz

CPU (MAX): 1458mhz

Scheduler: ROW

Scheduler Adjustments:

> hp_swrite_quatum = 5

> rp_swrite_quantum = 4

> rp_write_quantum = 4

Governor: Ktoonservative

Governor Adjustments:

> boost_cpu = 1080

> freq_step = 2

> sampling_rate = 50000

> sampling_rate_min = 10000

> sampling_rate_screen_off = 1000000

Auto Hotplug: Checked

Voltage Table: -50mV across the board

Screen Off Mhz: 189

Screen Off Gov: Same governor

Screen Off Sched: Same scheduler

Battery Level Low: 15

CPU Mhz for low level battery: 1080 mhz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chillwill11:
Best CPU times I've ever had thanks to liltitiz.. I'm running his script and his KT backup. Also this is running Pandora for exactly 8 hours at work. Thank you very much..:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You tried conservative or asswax? And how was responsiveness vs interactive on cpu1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chillwill11:
Conservative and I have zero lag. I'm not big on benchmarks so I haven't run any. I used my phone often and I've had zero problems with the your conservative setup. Zero lag..multi tasking was very fluid. Thanks again.. I look forward to more of your tweaks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Sorry never mind....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Hey I'm using the latest pa 5.7 with the latest kt kernel on my sgs i747 (att Samsung galaxy s 3) and I was wondering if anyone who was using this combo had some configs that gave some better battery life. I'm open to any suggestions i just am hesitant to try old configs i found on this thread with such a new build of paranoid android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Just check the last two pages... Also, if you use old settings just input the settings manually don't restore backups from older versions of ktweaker. Other than that it doesn't matter which ROM your on, if it is recent or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Just did the script and it works great! Im not noticing any lag on conservative and is not freaking anything out for those of you using my configuration. Thanks for the script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bomba_king:
do you have any prefs that I can restore? kinda new to this so im not familiar with running script and such.

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Lilitz and Baconator wonderful job I think this a great method of getting core two in check. Great job. I will test the new setup asap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
hi there, i hope this question isn't too dumb

I have the following kernel for stock TW JB 4.1.1

3.0.31-538866

se.infra@SEP-106#1

I want to try out kt747 but i've read about once you've flashed this new kernel and if you want to change kernels or switch back to the one you had, you have to reflash the drivers, or something.

Is there a guide or a step by step guide in changing kernels back and forth?

All I know right now is

1) Boot in recovery

2) flash kernel

AFTER installing the kernel:

3. Clear cache

4. Clear dalvik

5. Fix Permissions

6) If you are using my ktoonservative governor with the Touchwiz JELLYBEAN version, you should rename /system/bin/qosmgr to /system/bin/qosmgr.bak to prevent battery drain

Now if I wanted to revert back to the old kernel or another one that uses different drivers than KT747, what would i do?

I heard that even nandroid recovery cannot bring back the previous driver.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
The thing about the driver is old and doesn't apply anymore. Just follow the step you paste above and you'll be fine. If you wish to flash another kernel or restore your nandroid, don't mind about the drivers thing everything will be fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
In the post that I shared the script to run conservative as governor on cpu1(link: http://xdaforums.com/showthread.php?p=42445903), I also included my ktweaker backup that you can only download' move to your ktweaker folder and restore. If you want tho run one on my script, download this app

https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer

Swipe right to scripter, add a new script, copy the text of the script you wish to use, save, press on the script, set it on boot and then run it.

It is very easy and will not mess anything on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
You're question isn't dumb, this is the general thread, people are nice here.

I'm sorry I haven't used touch wiz in months, but I'm thinking I remembered ktoonsez saying that the Wi-Fi drivers thing wasn't necessary anymore. I remember the drivers came from Samsung so it's probably in the newer Samsung Rom. Sorry I can't say for sure. Just make your nandroid backup and flash away! Oh and I don't want to tell you what to do, but if I were you I'd just flash am aosp Rom like CM or slim or AOKP. In the opinion of many people android open source(asop) Rom's are miles ahead of touchwiz. Just restore that backup if you don't like it(also titanium backup pro is fantastic)

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Hmm having a random problem. When i try to run the script I get this error message

u0_a85@android:/ $ su

u0_a85@android:/ # sh /sdcard/Download/cpu1script.txt

/sdcard/Download/cpu1script.txt[1]: syntax error: '<' unexpected

Any idea of why this is happening?

1|u0_a85@android:/ #
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Syntax error. Your lines should look like this

echo 50 > /sys/devices/system/cpu/cpufreq/conservative/down_threshold

Not like this

echo 50 < /sys/devices/system/cpu/cpufreq/conservative/down_threshold
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
Thanks for your replies.

I guess I'll post my question on the main to toonz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
I m sorry I don't understand what you are saying. Do you mean the syntax In the script itself or the syntax of my command? I can't find anything In the script that has what you pasted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Ok I have a hard time explaining this so i'm gonna guide you from scratch with the easiest way to run a script.

1- go in the playstore and install this app: https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=fr

2- Open the app and swipe right to Scripter. Then press on the + sign to add a new script and gave it the name you want.

3- If you want to use conservative, copy and paste the content of this file(https://www.dropbox.com/s/4i5uzctopx50w87/cpu1conservativescript.txt) into the comand section.

If you want to use asswax then copy and paste the content of this file(https://www.dropbox.com/s/q4wy2t8ss75225y/cpu1asswaxscript.txt).

4- when you have paste the script you want, save it. It will get you back to the list of scripts. Press on the script you want, and select Run on Boot and then run the script. If you run into an error and the script don't want to apply then just reboot and it will work.

5-Enjoy :)

Note: you can save the to scripts and alternate between the two if you want to test them both.

What I meant with the Synthax error is this:

This is the error:

u0_a85@android:/ # sh /sdcard/Download/cpu1script.txt

/sdcard/Download/cpu1script.txt[1]: syntax error: '<' unexpected

When you type a command, You type Echo then the value you want to echo. Let's say it is asswax, want to echo asswax as the scaling governor of cpu1. So I'll type: echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor. This symbol( >) means that I want to take The value(asswax) and echo it to this system location. As you can notice, The error reports this: syntax error: '<' unexpected. Which leads me tothink that you may have enterd the wrong symbol. and this kind of command can't use this type of synthax since it is the opposite of >.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Ohhhhhh! Ok I got it the script I downloaded was a bunch of drop box jargon I but I went another screen into it and analysis downloaded the script and did what you said. Works like a charm! Your description was way easy to follow and ill remember that coding tidbit. Thanks again for your time :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I did some tuning in my ktoonservative(cpu0)/asswax(cpu1) setting. I was aiming to keep most of the load on cpu0 using cpu1 mostly to keep cpu0 from rampibg up to its max free too quickly. Cpu1 is set to ramp down real quick and stay on its lower freqs.

Ktoonservative setup to input in ktweaker:

Boost 2nd core on button:0

Boost cpu:594

Boost gpu: doesn't matter

Boost hold cycle :0

Boost turn on 2nd core:0

Cpu down block cycle:0

Down threshold:75

Down threshold hotplug:60

Freq step:3

Ignore nice load:0

No 2nd cpu screen off:1

Sampling down factor:1

Sampling rate: 30000

Sampling rate screen off: 60000

Up threshold:87

Up threshold hotplug:90

Link for my ktweaker backup(81-1512, stock voltages): http://db.tt/zM6JVuLa

---------------------------------------------------

Command lines to apply my asswax settings on cpu1 :

echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 1000 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 189000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 80 > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 60 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 250000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 100000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 5000 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us

LINK FOR THE .TXT FILE: http://db.tt/XEOyV7ej

---------------------------------------------------

How to apply the command lines on cpu1:

1- go in the playstore and install this app: https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=fr

2- Open the app and swipe right to Scripter. Then press on the + sign to add a new script and gave it the name you want.

3- copy/paste the command lines above.

4- when you have paste the script, save it. It will get you back to the list of scripts. Press on the script and select Run on Boot and then run the script. If you run into an error and the script don't want to apply then just reboot and it will work.

5- remember to adjust awake_ideal_freq, interactive_ideal_freq, sleep_ideal_freq, sleep_wakeup_freq to match with your minimum frequency if it is not 81 mhz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Can someone tell me if that bit about renaming QOS Manager applies to Non-Touchwiz roms too ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
For aosp Roms you can rename mpdecision under /system/bin. I still do it, but I know some developers don't.

Hey liltitiz, I've applied your asswax settings and dropped them into my script, so far so good :) I noticed something with the ktoonservative governor, if I disable the touch booster value(currently 378) and swipe my home screen it tends to make cpu1 spike way up, but the touch boost value helps it stabilize more or less and not spike up. Just thought I'd share my findings.

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
So I have applied these settings and I really like how it keeps cpu 1 at lower frequencies, however, anytime I use ktoonservative governor the sampling_rate gets changed to 10000 on its own somehow and causes my phone to get extremely hot and the battery starts draining quick. any fix for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I'd like to hear more about your setup, is it cpu0 or 1 that you've being setting ktoonservative to?

does your script set your sampling rate? I'd use ktweaker for your cpu0 settings. Get perfmon or cooltool and figure out which core is running at max frequency to make it hot.

But like I said I need more info

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
cpu0 is set to ktoonservative using the ktweaker app. i'm using liltitiz exact setup. somehow the ktoonservative sampling_rate file gets changed. I haven't been able to put a finger on a common task my phone is doing when the sampling rate changes so at the moment it seems random...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Make a backup of your current ktweaker setup if you wish to not lose anything, then into settings/apps, delete app data a d cache, reboot in recovery and reflash ktweaker by the usual way. Once you're done, don't restore any backup and try ktoonservative then input my setup manually and report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Might I suggest also clearing Superuser logs prior to reflashing the kernel simply for safety measures.