Database Develop

Boost Milestone Speed *(reguardless of ROM)*

https://market.android.com/details?id=com.sdincrease.it&feature=search_result
* * * MUST HAVE ROOT * * *
This app boosts your SD read/write speeds immensely! By default it is a mere 128k and it will push it as high as 6144k (6mb) but it suggests 2048k for "best" results.
I pushed mine up to 4096k (4mb) since i have EVERYTHING on my card. After the change everything glides like butter! Games respond quicker, everything in general just flows like butter on a hot-plate!
I know there was a post on this a while ago from another XDA member (brainmaster) but im reposting this to help out the 'stone!
Just install, open, set to desired speed & press the little flame button, then resume operations as normal.
NOTE: on reboot or turning on/off, it loses the values, so you will have to reapply the change again. Semi-annoying, but well worth it!

Looks good.
I'll try it.
Thank you .

NOTE: on reboot or turning on/off, it loses the values, so you will have to reapply the change again. Semi-annoying, but well worth it!
Click to expand...
Click to collapse
There is a small square button beneath ...on the left hand side to make it run on boot!
Haven't you see it?
SENT FROM MY MILESTONE POWERED BY GINGERBREAD

http://forum.xda-developers.com/showpost.php?p=12437265&postcount=1
The script that you run from there will be able to set the Read-Ahead cache size to whatever you want on every boot.

sdtaddey said:
There is a small square button beneath ...on the left hand side to make it run on boot!
Haven't you see it?
SENT FROM MY MILESTONE POWERED BY GINGERBREAD
Click to expand...
Click to collapse
yeah ive seen it... maybe its just my rom.. (ice&fire 1.9)
but alot of people in the comments say it happens to them as well.
but if you run your launcher/theme from the SD, it makes it run AALLOOTT smoother!

Use with caution. This is recommended only if you really opens huge files from the sdcard. For someone that do not use apps from the sdcard the best is keep the cache low.

lfventura said:
Use with caution. This is recommended only if you really opens huge files from the sdcard. For someone that do not use apps from the sdcard the best is keep the cache low.
Click to expand...
Click to collapse
EVERYTHING i have is on there... including my launcher/theme, along with 900+ pictures and 250+ songs.
so for me... its a big helper.

Iam using it to. But now it included in The FroyoMOD at 2048. Thats what ive been using before too...

[ROM] BakaMod V1 (2.2.1 KD1) - Froyo's Last Stand

BakaMod V1 - Froyo's Last Stand (2.2.1 KD1)
Built on the theory that LESS is MORE. This is a MINIMALIST Rom. It uses the most up to date Froyo base I could find. Why not Ginger? Well... battery.. GPS.. there are reasons to stick with Froyo IF you want reliability, speed and long life.
The battery on this rom is PHENOMENAL!
There will not be any updates to this ROM. I built it as a learning excercise, and while I think it is pretty stable, there are a couple few issues (all documented in this post) that I'm not prepared to deal with. Take it for what you will, if anybody wants to use this to do their own work and fix the issues, feel free, no credit required!
BASE: T959VUVKD1 from the SGS 4G by drhonk
FEATURES:
Removed tons of bloat. Didn't ADD my own bloat.
Accurate Battery Mod
Cianbreadish Status Bar
Simplified Boot Animation
GPS/Speed/Zipalign/Build Prop tweaks
Loopy Smoothness Tweak
No Full Battery Alert
No T-Mobile boot or shutdown sounds/animation.
6 Lockscreen/Power Menu Mod
KB1 Modem - Cuz I got great battery life.
Yes I know what Baka means. I use the term affectionately.
KERNEL: Bali-X 1.2
LAUNCHER: NemusLauncher
GPS
Should work perfectly as do all Froyo ROMs. I got a very quick lock (under 10 seconds) on first boot with this setup, with 10 satellites.
LAUNCHER
I went out on a limb including a relatively unheard of launcher. However, I find it to be a very lightweight and responsive launcher. A little different than you may be used to, it defaults to manual sorting of apps. To change this behaviour, from the app drawer, select Menu->MainMenu Style->Alphabetical, and it will go to vertical scrolling alphabetically.
KNOWN ISSUES
1. Apps2SD - KD1 assumes you want apps on the SDCard, even if the app doesn't prefer that location. Can cause issues. Only apps that explicitely block being installed to SD get installed to Phone Memory.
2. Wifi Calling - Not ported and probably won't be.
3. 4G Icon - I didn't notice it was still in the theme. Rest assured, your phone hasn't been granted magical 4G capability.
4. Locales: I won't be porting these. Looks like a nightmare, and unless this ROM becomes popular (which it won't), there's not much benefit.
5. Camera - It has the FFC button, but I'm not sure if the FFC works without additional hacking. Haven't tried it, I don't have an FFC.
INSTALL
The usual - flash from CWM. If you have issues, WIPE FIRST. Does not require any special boot loaders. Nothing to see here.
GET BLOATED
View the BLOAT on my website here: http://tsukaima.net/KD1Bloat/ and download whatever is missing that you want. Drop the missing junk into /system/app via ADB or Root Explorer, and feel re-bloated! Do note that these Bloats are for KD1 only!
Any other Google Bloat can be gotten from the market.
DOWNLOAD
http://www.multiupload.com/IW8EV3BT9X
NOTE:
I pulled the default Undervolt version. The only difference is it included the config file that you can generate using the Voltage Control app. It also crapped out some phones. I did this rather than a 1.1 release. After what appeared to be stable testing of the 1.1 release with only minor changes, it suddenly went crashy and bootloopy. Probably due to changes in the startup scripts, those things are touchy.
So... consider this the first and last release of BakaMod. Why? Well, there are some issues with KD1 that were never resolved, such as its installing apps to SD Card regardless of app preferences, as well as a few other minor issues that I'm just not prepared to address. As is, it is a usable ROM, but I plan to spend my energy elsewhere and let this release stand for what it is, which is actually a pretty usable 2.2.1.

Baka? Maybe you should change the name...Baka is Japanese for idiot/ stupid...

Can you tell me if wificalling works?

duboi97 said:
Baka? Maybe you should change the name...Baka is Japanese for idiot/ stupid...
Click to expand...
Click to collapse
I know exactly what it means.
Dattack said:
Can you tell me if wificalling works?
Click to expand...
Click to collapse
Not at this time. I'm not sure what all is involved in porting over the wifi calling app. If there's much interest in the ROM itself, I may take a look at that as well.

Sir you just got 2 thanks I'm 106 MB into downloading this...

duboi97 said:
Sir you just got 2 thanks I'm 106 MB into downloading this...
Click to expand...
Click to collapse
If you have any issues, let me know. I may be a ばか, but I'm learning rapidly!

Lol I'm not Japanese, but I've seen enough anime to know what Baka means...144 MB in!
Edit: Oh god I lost connection when I was at 151 MB, but it was okay I dodged a bullet there...Its done now...

duboi97 said:
Lol I'm not Japanese, but I've seen enough anime to know what Baka means...144 MB in!
Edit: Oh god I lost connection when I was at 151 MB, but it was okay I dodged a bullet there...Its done now...
Click to expand...
Click to collapse
Well I used my personal hosting for it rather than one of those silly click-through-everything and wait hosts... so resuming shouldn't have been an issue. Hopefully they didn't lie when they said unlimited bandwidth LOL...

Would it be okay to edit the build.prop and add the tweaks from Master&Slave's thread through 7zip or something like that?

duboi97 said:
Would it be okay to edit the build.prop and add the tweaks from Master&Slave's thread through 7zip or something like that?
Click to expand...
Click to collapse
I think you'd have to re-sign the zip if you did that. It might be better just to pull the existing one with adb and then push it back, or use root explorer.
The reason I didn't include the 3G tweaks from his thread, are that they are typically more or less helpful for each user depending on the local network conditions.

Oh screw it then...I'm throttled regardless I was talking about the sleep policies though..

duboi97 said:
Oh screw it then...I'm throttled regardless I was talking about the sleep policies though..
Click to expand...
Click to collapse
That part should already be in there. Will double check before I do any updates.

Oh alright then...I'm putting the ROM on my SD right now so I'll report back soon. I Odin'd to JFD for a clean flash as well..

duboi97 said:
Oh alright then...I'm putting the ROM on my SD right now so I'll report back soon. I Odin'd to JFD for a clean flash as well..
Click to expand...
Click to collapse
Been meaning to odin to JFD myself... have wanted to pull the framework from it to make an Eclair theme for nostalgia purposes LOL...

Phone is about to boot! Voodoo just got done activating...nice boot animation reminds me of the stock Mytouch 3g one lol I always adored that for some reason. Now I got to wait until 3:30 (midwest) to reboot ugh
I was just on JFD two days ago because I just got off of CM7 to flash DMZ and I JFD'd to flash this ROM as well time consuming, but I think its worth it...

When I boot up my phone it boots up first it boots then it has to boot over again 0.o hard to explain, but at first my phone wouldn't get signal then I had to reboot again (after the initial one) now everything is fine and I'm gonna dive into this ROM.

duboi97 said:
When I boot up my phone it boots up first it boots then it has to boot over again 0.o hard to explain, but at first my phone wouldn't get signal then I had to reboot again (after the initial one) now everything is fine and I'm gonna dive into this ROM.
Click to expand...
Click to collapse
Odd, not sure why it would double boot... Mine hasn't done that and I've flashed this several times tweaking everything. Maybe it is due to the recent ODIN? Or are you still on GB boot loaders maybe? If it continues to act up, it could be due to undervolting... I took a risk including that by default, but I think most phones can handle the settings I included. If not, I'll update it and let people undervolt via the market app, but in my experience it's a little daunting to be setting that up yourself for most people.

This is 2.2.1 so is call routing through headphones without mic working?
Sent from my GT-I9000 using Tapatalk

mohitmoudgil said:
This is 2.2.1 so is call routing through headphones without mic working?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Oooh, good catch. I'm not sure - and I do randomly use that feature in my car (have audio go through the car speakers)... I will let you know once I try it. If not, I'll have to investigate the issue.

Say, the Russian language there is? how much RAM?

build.prop

Here's a modified build.prop Ive tested on my Thrill. It includes a lot of the tweaks posted in various links but already packed into a build.prop.
I have tested to make sure that this build.prop will NOT break your phone. Im running this build.prop on my Thrill with no issues what so ever. Actual improvements from these tweaks are up to you to test. I make no claims to their actual effectiveness.
To use this just put it on your sdcard and rename it to build.prop (its currently just a .txt file for upload purposes). Then paste it into your /system partition using a root file explorer such as root explorer or estrongs.
Here's a list of the actual changes and what they are supposed to do:
ro.HOME_APP_ADJ=1 Keep home launcher (any) persistant in memory
ro.telephony.call_ring.delay=0 make phone ring faster when dialing out
ro.lge.proximity.delay=25 disable blackscreen issue after call
mot.proximity.delay=25 same as above
windowsmgr.max_events_per_sec=150 Better scrolling speed
wifi.supplicant_scan_interval=250 increase time between wifi scanning to save battery
pm.sleep_mode=1 save battery?
ro.ril.disable.power.collapse=0 save battery?
debug.performance.tuning=1 increase touch responsiveness
video.accelerate.hw=1 goes with above mod
debug.sf.hw=1 render ui with gpu (potentially taking some load off cpu?
ro.media.enc.jpeg.quality=100 increase jpeg quality to max
persist.adb.notify=0 removes the debugging mode notification from status bar
The following are all meant to improve 3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
Net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
Those are just the ones I know will NOT brick/bootloop your phone. Feel free to remove whatever you dont want to use. All additions are at the end of the file. So all you rom devs feel free to include them in your roms. If anybody has any more they've tested let me know so I can add them. And ill update the build.prop as I test more tweaks.
EDIT: Included the original build.prop file (original_build.txt). Just rename it to build.prop and stick it on the /system parition.

The LG Thrill only support 4G not 3G whatsoever

linuxboxsolution said:
The LG Thrill only support 4G not 3G whatsoever
Click to expand...
Click to collapse
Seriously? LG Thrill has no LTE antenna.
Sent from my LG Optimus 3D using xda premium

linuxboxsolution said:
The LG Thrill only support 4G not 3G whatsoever
Click to expand...
Click to collapse
The thrill supports 3g, att markets its 4g, which is really just improved 3g with a new name.
Sent from my LG-P925 using xda premium

kleeman7 said:
The thrill supports 3g, att markets its 4g, which is really just improved 3g with a new name.
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Well the thrill can do 4g it is just on att's crappy network which means we get 3G+ not true 4G. Att is too expensive, has horrible cust service and an even crappier network. However i live in att corporate heaven so where I live coverage and speed is top notch, when I travel though I see why everyone complains so much about them.

CallMeAria said:
Here's a modified build.prop Ive tested on my Thrill. It includes a lot of the tweaks posted in various links but already packed into a build.prop.
I have tested to make sure that this build.prop will NOT break your phone. Im running this build.prop on my Thrill with no issues what so ever. Actual improvements from these tweaks are up to you to test. I make no claims to their actual effectiveness.
To use this just put it on your sdcard and rename it to build.prop (its currently just a .txt file for upload purposes). Then paste it into your /system partition using a root file explorer such as root explorer or estrongs.
Click to expand...
Click to collapse
Okay, so I'm at the point I'm looking at it on root file explorer. As per your instructions, do I just copy and paste it the entire file onto my system partition? Or do I open it in a text editor and erase what I don't want? I ask because you mentioned using what you want out of it. And have you noticed improvements by using it?

kiltedthrower said:
Okay, so I'm at the point I'm looking at it on root file explorer. As per your instructions, do I just copy and paste it the entire file onto my system partition? Or do I open it in a text editor and erase what I don't want? I ask because you mentioned using what you want out of it. And have you noticed improvements by using it?
Click to expand...
Click to collapse
Just open the file and delete the lines you dont want. Then Rename the file to build.prop and then copy/paste to to your /system partition.
The network tweaks made no difference in speed for me. The persistant home was an improvement. The rest its hard to tell of it's placebo or not without some way to test. The problem is I didn't have the phone long enough before making the tweaks to get a good enough feel for it to tell the difference definitely no negatives to those tweaks though.
Sent from my LG-P925 using XDA App

Okay so I've edited out and kept what I want and changed it to a build.prop. I'm using root explorer. I don't see a /system. I see a system. But when I go to paste it in there, it says I already have a build.prop and it will replace. Obviously I don't want to screw anything up.
Looking through my build.prop that's in the root, it doesn't have anything listed like what's on the build.prop (txt) that I downloaded. Can I paste it into there or is that a terrible idea?
This makes me wish I had a couple of phones like this just to mess and tinker with.
edit-
Okay, so I'm looking in the build.prop folder and I don't see any listings for the ro.ril files. I downloaded prop editor and can't find them there either.

kiltedthrower said:
Okay so I've edited out and kept what I want and changed it to a build.prop. I'm using root explorer. I don't see a /system. I see a system. But when I go to paste it in there, it says I already have a build.prop and it will replace. Obviously I don't want to screw anything up.
Looking through my build.prop that's in the root, it doesn't have anything listed like what's on the build.prop (txt) that I downloaded. Can I paste it into there or is that a terrible idea?
This makes me wish I had a couple of phones like this just to mess and tinker with.
edit-
Okay, so I'm looking in the build.prop folder and I don't see any listings for the ro.ril files. I downloaded prop editor and can't find them there either.
Click to expand...
Click to collapse
The build.txt file I posted is meant to replace your original build.prop file completely. Everything from your original build.prop should be in the new file, but not vice versa. So once you renamed it you can just delete the old build.prop and paste in the new one and reboot the phone. If it gets stuck at the boot screen (the att screen after the LG screen) then you will probably need to pull the battery and boot into CWM recovery and restore a backup. No harm no foul. But like I said earlier, ive actually tested this build.prop on my phone and it boots fine for me every time. So you should have any issues.
Of course all of this should be done after doing a back up, just in case. Better safe than sorry. As long as you have CWM installed and have made a backup you wont do any damage with the build.prop that you cant reverse with a nandroid restore.

Done and rebooted back just fine. Thanks given!
I'm liking this phone but should I choose to return it, when they send the phone back to AT&T and clean it up to sell it as a refurb, will they be able to tell the prop.build has been altered?

kiltedthrower said:
Done and rebooted back just fine. Thanks given!
I'm liking this phone but should I choose to return it, when they send the phone back to AT&T and clean it up to sell it as a refurb, will they be able to tell the prop.build has been altered?
Click to expand...
Click to collapse
Did you save a copy of your original build.prop? Ill post up a stock build.prop in the original post in a bit. I doubt its something they would notice but its a quick process to replace it.
EDIT: added the original file to my first post.
Sent from my LG-P925 using XDA App

CallMeAria said:
Did you save a copy of your original build.prop? Ill post up a stock build.prop in the original post in a bit. I doubt its something they would notice but its a quick process to replace it.
EDIT: added the original file to my first post.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
No. And thanks for the heads up and the stock build.prop. I'll go make a back up after coaching this middle school soccer game. This thing is super fast now. It downloaded the thrill zip faster than my laptop on the wifi. So either it's stupidly fast now or my wifi sucks.
Now if we can get reboot recovery and flashing roms via rom manager.

4G = Giant SCAM. Even LTE 1.0 is not "4g" because it does not offer 1gbit to stationary devices.
No different than "Windows 7", which is actually Windows 6.1.
F'cking marketing people and their fraudulent numbers.
Anyways, In terms of the the HSDPA category setting, 14 is probably the best bet. My understanding is AT&T's HSPA+ network is running at 21mbit at the moment.
List of categories:
http://en.wikipedia.org/wiki/High-Speed_Downlink_Packet_Access
http://en.wikipedia.org/wiki/High-Speed_Uplink_Packet_Access
... Probably want to try category 6 uplink, as well.
Anyone have any information on the Thrill's radio, like how to see what speeds it's actually training at? Haven't had the time to hack at the RIL yet.

There is supposed to be a setting in the build.prop to keep the capacitive buttons lit up when the screen is, do you know which setting it is?
Sent from my LG Thrill faux G

quarlow said:
There is supposed to be a setting in the build.prop to keep the capacitive buttons lit up when the screen is, do you know which setting it is?
Sent from my LG Thrill faux G
Click to expand...
Click to collapse
Yes I tried it when I was adding tweaks and it didn't work at all so I omitted it. If you want to give it a try though:
ro.mot.buttonlight.timeout=1
Sent from my Thrill 4G using Tapatalk

CallMeAria said:
Yes I tried it when I was adding tweaks and it didn't work at all so I omitted it. If you want to give it a try though:
ro.mot.buttonlight.timeout=1
Sent from my Thrill 4G using Tapatalk
Click to expand...
Click to collapse
Didn't work for me. After some Googling it should be =0 to keep the lights on, but the "mot" stands for Motorola, LG and lge don't work either.
What is weird is that the Netflix app somehow keeps those lights on, also Brightest Flashlight. There must be a way to do this. The app in the O3D forums doesn't work on the Thrill. It worked to turn them on with the screen off for notifications, but after the last update it just FCs.
Sent from my LG Thrill faux G

quarlow said:
Didn't work for me. After some Googling it should be =0 to keep the lights on, but the "mot" stands for Motorola, LG and lge don't work either.
What is weird is that the Netflix app somehow keeps those lights on, also Brightest Flashlight. There must be a way to do this. The app in the O3D forums doesn't work on the Thrill. It worked to turn them on with the screen off for notifications, but after the last update it just FCs.
Sent from my LG Thrill faux G
Click to expand...
Click to collapse
Thanks for that info. Ill see if I can figure something out after the game.
Sent from my LG-P925 using Tapatalk

Disable boot animation:
debug.sf.nobootanimation=1

The update to the app in the O3D forum seems to do the trick. Now my buttons stay on with the screen. Reboot required after installation, and it doesn't seem to work until you lock and unlock your phone once after each reboot.
Sent from my LG Thrill Faux G

I can debunk a few of these tweaks. I am definitely not endorsing the ones not debunked here... I just don't know a way to test if most of the tweaks in the first post are doing anything or not. Never been a fan of build prop tweaks to be honest unless I actually understand what they do and can verify that they work.
CallMeAria said:
ro.HOME_APP_ADJ=1 Keep home launcher (any) persistant in memory
Click to expand...
Click to collapse
The stock Thrill kernel won't kill the launcher unless there is less than 16 MB of RAM available and an app is requesting more. If you set the launcher to stay persistent in memory and a game you're playing needs a few more megabytes of memory, it might just crash instead of kicking the launcher out of memory and continuing on. The decision is up to you on that one.
CallMeAria said:
mot.proximity.delay=25
Click to expand...
Click to collapse
This tweak only applies to Motorola phones. It has no affect on the Thrill.
CallMeAria said:
ro.media.enc.jpeg.quality=100 increase jpeg quality to max
Click to expand...
Click to collapse
This tweak has no affect on the Thrill. I have done some testing to confirm.
CallMeAria said:
ro.ril.hsxpa=2
Click to expand...
Click to collapse
This is already set on the stock Thrill firmware.
CallMeAria said:
ro.ril.hsdpa.category=10
Click to expand...
Click to collapse
This is already set in my Thriller ROM.
CallMeAria said:
ro.ril.hsupa.category=5
Click to expand...
Click to collapse
This is an incorrect setting and may actually make your upload speeds slower. The Thrill supports hsupa category 6.
CallMeAria said:
Net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
Click to expand...
Click to collapse
These values are actually less aggressive than the stock values on the Thrill so they will probably decrease your network speed.

[APP] Myrt Undervolt GUI

EDIT: This app has been suspended, it serves no purpose anymore.
By popular demand, here's an app to set undervolt-values. It works on any ROM which runs on a suitable kernel, but needs init.d-support to be able to keep settings between reboots. (If your device supports it you'll get a button you can use, if not a little message in its place.)
WARNING: By using this app, you're playing with fire. It's in fact very likely you'll lose data if trying to see "how low you can go". Do not experiment without backing up everything first.
It's easy to use, and easy to freeze your phone with, make sure you know what you're doing. (Yes, changes become effective as soon as you apply them.)
It's clever when it comes to the volt_scheduler script as well, it only edits the line which sets the values at startup, meaning you can change the script as much as you like, the app won't touch anything else in it. (It also fixes the script-permissions on Topogigi 1.9, which aren't set correctly on a default install.)
The app will NOT let you change the startup-script until you have applied the settings. This is an attempt to avoid applying bad undervolts at startup. (The theory is that your phone will freeze if you're undervolting too much, and hence you won't be able to save those values to the startup script. If you try hard enough however, you will be able to save unstable settings, with the possible consequence of boot-loops and data-loss. I'm not kidding, be careful!)
NOTE: If you're using a system-monitor (System Tuner for example) and it doesn't show the voltages you applied, you need to force-stop and restart it before it'll show the current values (pun intended.)
NOTE2: Tegra 2 never supplies less than 770mV to the CPUs. The app will let you set undervolt below 770 though, and will in brackets show you what the real undervolt (on Tegra2) actually is. (Until recently I thought this was a hardware limit, but learned it is a kernel-limit. There may be kernels out there which can go lower. If the minimum frequency's default voltage is not the same as the kernel's minimum, the numbers in brackets will be off by the difference between the two.)
HEEELP: "I was very stupid and saved the undervolt-values to the startup script without testing properly first. Now it keeps rebooting. Is there anything I can do?" See Post #2.
Happy undervolting!
Click to expand...
Click to collapse

HEEELP: "I saved the undervolt-values to the startup script without testing properly first. Now it keeps rebooting. Is there anything I can do?"
Yes. The phone cannot be damaged by undervolting, but your data might. First thing you should do is to stop the reboots by pressing and holding "Power" and "Volume Down" to enter CWM.
You will need to have ADB installed on your computer. (The following instructions are for Windows-users.)
Select "Mounts and Storage" in CWM and select "Mount /system"
o In a shell, type:
If you're using a Topogigi ROM:
Code:
adb pull /system/xbin/volt_scheduler c:\
If you're using anything else:
Code:
adb pull /system/etc/init.d/S_volt_scheduler c:\
Now edit the file c:\volt_scheduler or c:\S_volt_scheduler in a PROPER editor like Notepad2 or Notepad++. DO NOT use the regular Notepad. You'll see a line with some numbers enclosed in quotation marks. Replace those numbers with zeroes. Save it.
Then type (Topogigi)
Code:
adb push c:\volt_scheduler /system/xbin/volt_scheduler
del c:\volt_scheduler
adb shell chmod 755 /system/xbin/volt_scheduler
adb reboot
or for other roms:
Code:
adb push c:\S_volt_scheduler /system/etc/init.d/S_volt_scheduler
del c:\S_volt_scheduler
adb shell chmod 755 /system/etc/init.d/S_volt_scheduler
adb reboot
If you're lucky, your phone will boot properly. If it still boot-loops, you've had some sort of corruption and need to wipe. If it still loops you've had corruption on the system partition, a full re-install (or backup-restore) is the last option.

Good job! Since I don't need OC but UV is useful for me.

greaatt... sadly this afternoon i already edit the script manually
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying.. )
Thanks! I use your clock adjustment tools too

gideonrs said:
greaatt... sadly this afternoon i already edit the script manually
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying.. )
Thanks! I use your clock adjustment tools too
Click to expand...
Click to collapse
You're very welcome.

thanks for ure great effort.
can you specify the UV settings that will not damage the phone?
p.s. i really like unlock silly values option
Thanks.
edit: can i use -50Mv

shpapy said:
thanks for ure great effort.
can you specify the UV settings that will not damage the phone?
p.s. i really like unlock silly values option
Thanks.
edit: can i use -50Mv
Click to expand...
Click to collapse
I wish it were that easy. Every phone is different. Mine seems to be completely stable at -75 across the board, and at 800Mhz I can run it at the lowest voltage possible, 770mV. Which is why I run everything at -50 ;-) (I learned a long time ago that balancing on the edge sooner or later makes you fall off.)
Other people have reported that their max stable undervolt is -25mV. There's no single recipe for everybody.
The correct way to test it is to set both min and max-frequencies to the same (for both awake and sleep-modes), then decrease voltage by one step, then run the toughest apps you can think of for at least 15 minutes each. If nothing weird happens, write down the numbers, decrease one step again, etc. etc. until you have found the breaking point for that particular frequency.
Then, and this is important, you need to make sure the phone is able to wake from sleep with those same values. For this you need to set sleep-mode to the normal frequencies again.
If everything works out with that, rinse and repeat with the next frequency. After you're done, you should have a nice set of numbers - increase them all by 25mV. That's your lowest stable voltage for each frequency.

thanks allot for the detailed and super fast reply.
as i mentioned in the edit i edited the Mv to 50 all across the board and its fine
also when gaming (thanks for the tip, i was just running quadrant each time)
i am running neoblaze with FR19 (2.2)

I UV by 50mv and then saved the profile with pimp my CPU and applied at boot since I use init.d
I wonder how much more battery I can squeeze more now
Sent from my LG-P990 using XDA App

Awesome apps Trym! I downloaded this and the OC one. Left some stars on the market too.

salisbury_steak said:
Awesome apps Trym! I downloaded this and the OC one. Left some stars on the market too.
Click to expand...
Click to collapse
Thanks!
10chars.

shpapy said:
I UV by 50mv and then saved the profile with pimp my CPU and applied at boot since I use init.d
I wonder how much more battery I can squeeze more now
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
I guess I can easily do that from the app. Currently looking into how to best determine if a system has working init.d support.
EDIT: Done.

TrymHansen said:
I guess I can easily do that from the app. Currently looking into how to best determine if a system has working init.d support.
EDIT: Done.
Click to expand...
Click to collapse
so what is the next step with the app?

shpapy said:
so what is the next step with the app?
Click to expand...
Click to collapse
I don't have any more plans for it at the moment, it does what it was designed to do. Open for suggestions though. I did add support for startup-scripts on ROMs with init.d. (I modify PimpMyCpus script, if it's there, to avoid conflicting scripts. If not I create it.)

TrymHansen said:
I don't have any more plans for it at the moment, it does what it was designed to do. Open for suggestions though. I did add support for startup-scripts on ROMs with init.d. (I modify PimpMyCpus script, if it's there, to avoid conflicting scripts. If not I create it.)
Click to expand...
Click to collapse
Please bring back set on boot
Thanks!!!!
Sent from my LG-P990 using XDA App

shpapy said:
Please bring back set on boot
Thanks!!!!
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Long story short: Some ROMs didn't apply the settings at boot due to non-functioning init.d. So I made some changes to better discover which ROMs support it. So, in theory, if the button isn't there, you're running a ROM which it doesn't work on anyway.
This is all very new to me, If I mistakenly remove the button on ROMs where you have working init.d, please report back here with the details of the ROM. (Update to the latest version of the app first.)
I tested it on GR4 cooked with stock kernel (no working init.d support, even when you replace the kernel), GR4 cooked with custom kernel (working init.d), Fr19 (Working init.d), Topogigi (which it was originally designed for - always working) etc.
CM7 has init.d support, but refuses to set the undervolt-values both live and and boot (VorkKernel), I'm looking into that.

I have fr 19 with the latest neoblaze which supports for sure since i checked the logcat. also now with topo 2.0 its missing
Sent from my LG-P990 using XDA App

I jumped the gun i had to clear data working fine now
Sent from my LG-P990 using XDA App

shpapy said:
I jumped the gun i had to clear data working fine now
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Ok, good to hear.

Just a heads up that it now works on VorkKernel (CM7) as well, from appversion 0.6.5.

[Q] Build.prop and the nexus 5 and 6

okay i have found many threads for the build.prop tweaks for the nexus 5. Do these same tweaks work for a nexus 6? If not where can i find such a guide to help with tweaks. And also if i just changed my phone model to nexus 5 would that make a difference. Yes I have made a nandroid backup. Any help would me much appreciated or if your looking for the same thing maybe we could help each other.

Ruthlez Ryn0 said:
okay i have found many threads for the build.prop tweaks for the nexus 5. Do these same tweaks work for a nexus 6? If not where can i find such a guide to help with tweaks. And also if i just changed my phone model to nexus 5 would that make a difference. Yes I have made a nandroid backup. Any help would me much appreciated or if your looking for the same thing maybe we could help each other.
Click to expand...
Click to collapse
most build.prop edits, and I mean most, like 95% of them, are old and do nothing for modern phones. a few still work though. the build.prop edits would be the same as most nexus 5, some would need specific changes for the n6 though.

simms22 said:
most build.prop edits, and I mean most, like 95% of them, are old and do nothing for modern phones. a few still work though. the build.prop edits would be the same as most nexus 5, some would need specific changes for the n6 though.
Click to expand...
Click to collapse
thanks alot for the quick response, well that's a bummer. is there anything out to optimize the nexus. Wonder if I should have kept S6.

Ruthlez Ryn0 said:
thanks alot for the quick response, well that's a bummer. is there anything out to optimize the nexus. Wonder if I should have kept S6.
Click to expand...
Click to collapse
if you go through all the build.prop edits tou know, youll find a few that work on the n6. for instance, you need a build.prop edit to gwt tethering to work, so that your carriers dont see. or, my favorite, i use this when benchmarking, to make fun of people making fun of people.. ill set a build. prop edit to remove the fps limit that is set for our devices :angel:

simms22 said:
if you go through all the build.prop edits tou know, youll find a few that work on the n6. for instance, you need a build.prop edit to gwt tethering to work, so that your carriers dont see. or, my favorite, i use this when benchmarking, to make fun of people making fun of people.. ill set a build. prop edit to remove the fps limit that is set for our devices :angel:
Click to expand...
Click to collapse
Thank you so much for the response. I used a couple and could notice a change, the list I am going from is so long, and the only way for me to input them in the build.prop and sticks. Is to edit it with es note editor. Tried copy and past didn't work. Tried doing with ADB by pulling build.prop and editing it. Didn't work. Only works if I manually put it in. Well guess I will go thru and see which ones work and don't. Or which ones I can tell anyways. Took a couple benchmarks, before I am going to apply tweaks.

Ruthlez Ryn0 said:
Thank you so much for the response. I used a couple and could notice a change, the list I am going from is so long, and the only way for me to input them in the build.prop and sticks. Is to edit it with es note editor. Tried copy and past didn't work. Tried doing with ADB by pulling build.prop and editing it. Didn't work. Only works if I manually put it in. Well guess I will go thru and see which ones work and don't. Or which ones I can tell anyways. Took a couple benchmarks, before I am going to apply tweaks.
Click to expand...
Click to collapse
i use root explorer. i just enter it in, or copy/paste it, save it reboot, and it always works. btw, my build.prop edit to get rid of the fps limit is..
debug.egl.swapinterval=0
copy this to your build.prop, save it, then reboot. to re enable the limit, change the 0 to a 1 and reboot.