Related
When I wiped my ext partition and had maybe 20 default apps on, the app launcher moved like a beast, instant, basically like the godly iphone UI + a discrete adjuster.
However now I'ved restored my 250ish apps/elements it now lags like a mofo. What I want to know is what physically is being limited hardware wise, and is there any way to boost the performance of this memory? I assume it would be between CPU, RAM and GPU, although I dont understand how it could be annoy of those [sorry for my noobishness]:
CPU: Snapdragon, OCed, not exactly CPU intensive anyway
RAM: Have 250MB free, never seems to get 'full' when i quickly tab to the usage
GPU: This is what I guess, but if so why cant we get around this with a less intensive menu setup? Surely all that is happening is we have 20-25 icons + labels floating up and down on a screen? To be honest id prefer literally just that on an instant screen over the 'oo that looks nice.... oh wait it lags like a *****' we have now.
Any comments would be appreciated
MOD EDIT - Moved to Q&A
well, one thing which would probably slow down the launcher is the sd card speed... and considering u've got a helluva lot of apps on ur sd card, it seems like a plausable reason...
Is anyone able to confirm that? Surely though its precached the icons and names somewhere though :/
dogiedogie said:
Is anyone able to confirm that? Surely though its precached the icons and names somewhere though :/
Click to expand...
Click to collapse
if you use CM rom you can go to spare parts and enable "keep launcher in memory" that usually helps a lot
I have Kang, so has a launcher over CM. The setting was enabled, but i dissabled and renabled to see if that was a problem. Possibly did solve a bit of it, but it still takes at least half a second for the menu to catch up with my finger, even including 'touch lag'. The only way you can see what I mean is if you play with an empty phone, its INSTANT.
dogiedogie said:
I have Kang, so has a launcher over CM. The setting was enabled, but i dissabled and renabled to see if that was a problem. Possibly did solve a bit of it, but it still takes at least half a second for the menu to catch up with my finger, even including 'touch lag'. The only way you can see what I mean is if you play with an empty phone, its INSTANT.
Click to expand...
Click to collapse
probably some runaway apps taking a toll on ram and system resources.
i did a major clean up yesterday and my phone is zippier than ever
dogiedogie said:
Is anyone able to confirm that? Surely though its precached the icons and names somewhere though :/
Click to expand...
Click to collapse
You mean the activity/app choice list right? (like when you make a application shortcut, or view installed applications). It does lag when you have a lot of apps. If it does cache the data its definitely short-term, if you try it again after a day its slow the first time.
Lets hope froyo has something to make it faster, systemwide.
britoso said:
You mean the activity/app choice list right? (like when you make a application shortcut, or view installed applications). It does lag when you have a lot of apps. If it does cache the data its definitely short-term, if you try it again after a day its slow the first time.
Lets hope froyo has something to make it faster, systemwide.
Click to expand...
Click to collapse
Sorry, if there is any misunderstanding I am talking about the app menu, where you go to open your apps from the home page.
dogiedogie said:
Sorry, if there is any misunderstanding I am talking about the app menu, where you go to open your apps from the home page.
Click to expand...
Click to collapse
ok, I dont have noticeable lag with my 140 apps. I have a 6 column launcher too
britoso said:
ok, I dont have noticeable lag with my 140 apps. I have a 6 column launcher too
Click to expand...
Click to collapse
I assume the only difference between our phones then is SD card.
I have http://www.amazon.co.uk/gp/product/B001CQT0X4/ref=oss_product
EDIT: http://www.steelbytes.com/?mid=20&cmd=download&pid=1&lang=eng I used that and got a read speed of 3mb/s, could you do the same so we can see if its that?
Cheers.
then is SD card.
I have http://www.amazon.co.uk/gp/product/B001CQT0X4/ref=oss_product
EDIT: http://www.steelbytes.com/?mid=20&cmd=download&pid=1&lang=eng I used that and got a read speed of 3mb/s, could you do the same so we can see if its that?
Cheers.
Click to expand...
Click to collapse
for my Ridata 16GB (class6/6x), tested by mounting and via usb.
Read: 3.1 MB/sec (approx 20x)
britoso said:
for my Ridata 16GB (class6/6x), tested by mounting and via usb.
Read: 3.1 MB/sec (approx 20x)
Click to expand...
Click to collapse
Hmmm :/ So its not my SD card. I just dont understand why it physically lags, when I watch people showcasing some new app etc, their menu is perfectly fluid, even with a similar number of apps.
Anyone have any other ideas?
Tired of your widgets redrawing and lagging when you come back to the home launcher? Well then enter this into your data/local.prop file
Code:
ro.home_app_adj=1
Just put that into your /data/local.prop file and then reboot
You should be good to go!
How does this work ?
Does it keep them the widgets and homescreen elements in memory thereby increase memory usagE ?
StDevious said:
How does this work ?
Does it keep them the widgets and homescreen elements in memory thereby increase memory usagE ?
Click to expand...
Click to collapse
Yes it keeps them in memory. However, the X has plenty to spare. No performance issues whatsoever, just a faster redraw.
Its almost like the checkbox in LP that say "Attempt To Force into Memory", only this way actually works.
Is this just for the Blur Home or will it effect things like ADW.Launcher?
thanks bees!
Ubermicro13 said:
Is this just for the Blur Home or will it effect things like ADW.Launcher?
Click to expand...
Click to collapse
AFAIK, It works for every home.
Thanks Beesley! I'll give it a shot.
So after performing this, i checked the local.prop and it appears to have been overwritten upon reboot...
tdrussell said:
So after performing this, i checked the local.prop and it appears to have been overwritten upon reboot...
Click to expand...
Click to collapse
Same on mine I'm on rubiX Focused 1.6.
tdrussell said:
So after performing this, i checked the local.prop and it appears to have been overwritten upon reboot...
Click to expand...
Click to collapse
Happened to me also on Fission 2.1
fantastic! I use it.. in fact, I used bees' other mods for awhile. Love 'em!
I'm running Fab's ApeX ROM and after doing the edit and rebooting the edit is gone. I've tried deleting the backup file prior to rebooting but it still does not stick.
I used text editing the local.prop file with fission rom v2.1.RC2 through root explorer. The setting seems to stay after a reboot. However, I did not notice any improvement at all.
didn't survive reboot
local.prop just went back to how it was before
Hi all,
I have a question while enjoying my Milestone to the max, thanks to CM7!
Since RC4 I have a problem with ADW Launcher after booting the device.
First it seems like there's a delay connecting to the SD card, because the icons of apps installed on SD don't show up on my homescreen. Instead a stock or native icon is visible.
Then the homescreen goes black for a few seconds and reloads completely. The icons of apps on SD still don't show, and my weather widget says it can't connect.
After a little while a message pops up, saying that "activity ADW Launcher in process android.process.acore doesn't respond". I can choose to close ADW Launcher or wait. In both cases all loads well after making one of those choises, it doesn't matter which one.
Since I suspected some kind of delay affecting the SD card and Internet connection, I expected this to be (partially) solved in RC4.1 according to this release note: "fix: kernel modules sometimes installed too late (sd-ext not mounted, overclock not applied)". But unfortunately in my case it isn't.
I already have tried disabling Sense previews and Wallpaper Hack in ADWLauncer settings, but that didn't help. Am I the only one with this problem or does it sound familiar? In that case, what can be done?
Thanks a lot,
Gerard
The Netherlands
the problem of the launcher crashing is sumthin everyone faces .. n it does slow the phone down as well .. ask a techie if u can remove adw launcer and install another launcer cuz ther has to b a launcher faster than adw ..
Okay, but I can't imagine this behaviour occurring on every device at the moment?
on most devices u c this prob .. tht is wher stock rom is better and snappier ..
in rc4 sumtimes the power control widgets in the notification bar also disappear .. its werid ..
twixyz said:
Okay, but I can't imagine this behaviour occurring on every device at the moment?
Click to expand...
Click to collapse
Not on supercharged phones. No launcher redraws. Ever.
Plus, gingerbread packed with apps feels as light and fast as stock froyo with nothing installed on it.
You should try it.
zeppelinrox said:
Not on supercharged phones. No launcher redraws. Ever.
Plus, gingerbread packed with apps feels as light and fast as stock froyo with nothing installed on it.
You should try it.
Click to expand...
Click to collapse
I sure will. In fact, I wanted to supercharge my Milestone since I read the topic, but I'm still struggling through the loads of information trying to figure out what I need and need not to do. Once I created a step-by-step instruction, I'm good to go.
Maybe you can help me to make me see the big picture. From what I understand, I need an app like AMM and one of your scripts. In the app I can modify the minfree settings. The script takes care of loading these settings on every boot. Is this correct? If so, can you please tell me which files I need for the first 2 steps? I don't need extra apps like GScript and Busybox so far, do I? Trying to start off simple...
Any additional instructions are welcome!
Thanks a lot,
Gerard
The Netherlands
Go Launcher Ex... was the solution of all my launcher problems...
Good Luck!
twixyz said:
I sure will. In fact, I wanted to supercharge my Milestone since I read the topic, but I'm still struggling through the loads of information trying to figure out what I need and need not to do. Once I created a step-by-step instruction, I'm good to go.
Maybe you can help me to make me see the big picture. From what I understand, I need an app like AMM and one of your scripts. In the app I can modify the minfree settings. The script takes care of loading these settings on every boot. Is this correct? If so, can you please tell me which files I need for the first 2 steps? I don't need extra apps like GScript and Busybox so far, do I? Trying to start off simple...
Any additional instructions are welcome!
Thanks a lot,
Gerard
The Netherlands
Click to expand...
Click to collapse
Latest and greatest... http://forum.xda-developers.com/showpost.php?p=12883386&postcount=379
Yes all the steps are in the Gscript section.
You don't need AMM or AKMO but I use AMM just for diagnosing and poking around to see how everything is working.
All you gotta do is install busybox and gscript as per instructions in the Gscript section.
Hi all, and especially Zeppelinrox,
Since CM7 RC4 my launcher hardly ever gets NOT redrawn/reloaded. Very annoying. I've tried every setting and combinations of settings with no luck. So I've decided to step into the deep and give Superlaunch and Bulletproof a go. I'm still not sure if I understand the whole package though, so I'd like to verify whether or not I did the right thing.
I've just installed Gscript and in there I activated from script v5: balanced, status and the Bulletproof launcher. I unchecked the "keep launcher in memory" setting. Then I rebooted.
Now I'm gonna do some tests, but was this procedure correct and complete? And does this stick after a reboot? If not, how can I make it stick for both Superlaunch and Bulletproof? I assume I don't have to manually execute these scripts after rebooting every time?
I'll report my findings later today. Thanks in advance!
Regards,
Gerard
The Netherlands
Yes it all sounds correct and the settings will persist after reboot.
However, by default the launcher is not bulletproof you can run that script separately if tou still get redraws.
V6 has Hard To Kill Launcher which is as strong as it can be without bulletproofing - much stronger than lock home in memory.
With V6, bulletproofing should not be necessary at all while allowing games to be played.
But it is still an option for those that don't play games.
Sent from my Milestone using Tapatalk
Well, I can tell you this: it's awesome! I've been poking around for hours now, and never had a single redraw. My Milestone runs smoother than ever. Fan-tas-tic!
I just don't understand the AMM readings. It always shows it's own mild settings, but shouldn't it display the script values?
Thanks a lot!
Gerard
Which script did you apply?
AMM is stupid that way lol
Just be sure SuperUser give no permissions to AMM
AKMO will show the current minfree values when you run it though - just disable it's apply settings at boot option - or don't give superuser permission.
I applied Balanced3 from gscript-Custom_ROMS_SuperCharge+BulletProof_Pack_v5.zip (10.7 KB, 461 views)
In SuperUser permissions for AMM are denied.
So AMM doesn't read the current values at all and I'm OK? Guess I'll have to calculate the values myself from the show status script then, or is there an easier (preferable newbie) way to verify if all settings are correct?
Now we're at it, later today I'm gonna install the CM7 update. I know I'll have to recalibrate the battery after that, but do I have to run these scripts again too?
Thanks again!
Gerard
Ya I'd like to figure out a way to do the calculation with the script.
I haven't been able too get to far on that as of yet.
I mentioned in my prvious post - you can quickly check with AKMO - Autokiller Memory Optimizer - just disable the apply on boot option.
There is also Minfree Manager.
Yep, run the scripts again after flashing a rom
I just installed AKMO and it displays the scripts values flawlessly!
Don't know what AMM did, but apparently it kept on changing the values to very strange numbers after a reboot. I can't remember them, but the 3rd one was 256 (1). I'm sure it had no root permissions though. But now AMM is gone, all loads well after rebooting according to AKMO.
It makes all the difference in the world, I can tell you that. My Milestone runs like a complete new device. So smooth, fast and stable. I can recommend it to everyone!
I have just one more question. What script is best suitable for running big map apps, like Google Earth? It's lagging, freezing and closing with the standard minfree settings. The Balanced3 script makes it better, but can it improve even more?
Thanks again and again and...
Gerard
I dunno.
That's a big app
Maybe you can overclock it more LOL
btw... I DID IT... I got the script to convert pages to mb... woohoo
I'm already at 1000 Mhz, can't seem to get it running at 1100 or higher though, cause it keeps rebooting from the M logo. But maybe there's potential for a script handling "big apps" ;-)
Anyway, congrats on your progress with the scripts! I wonder why devs haven't implemented this in their ROM's yet.
Now it's time to move on to my next project: an ext-partition. I read so much about it. Still no idea about the advantages though, so I'll start by figuring that out first.
Thanks for all your help and good luck with your work!
Gerard
twixyz said:
I'm already at 1000 Mhz, can't seem to get it running at 1100 or higher though, cause it keeps rebooting from the M logo. But maybe there's potential for a script handling "big apps" ;-)
Anyway, congrats on your progress with the scripts! I wonder why devs haven't implemented this in their ROM's yet.
Now it's time to move on to my next project: an ext-partition. I read so much about it. Still no idea about the advantages though, so I'll start by figuring that out first.
Thanks for all your help and good luck with your work!
Gerard
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10994672&postcount=226
Use that and only do the steps to create the ext2 partition. Then after that, reboot CM7 and you should have all of your apps on your ext2 partition, thus making your phone a bit faster(less internal memory used) and the potential for a TON of more apps installed on your phone, depending on the size of your ext2 partition.
Really! You just saved me a lot of reading, thanks!
So after I created the ext2 partition through my PC, rebooting the device handles moving my apps? No reinstalling, no manual uninstalling from internal memory? But how about apps without apps2sd option, will they be unaffected? Or does ext2 simulate internal memory, so all apps can be installed there? If so, will apps from the Market then automatically be installed on ext2, with or without apps2sd?
Sounds great!
Thanks in advance,
Gerard
twixyz said:
Really! You just saved me a lot of reading, thanks!
So after I created the ext2 partition through my PC, rebooting the device handles moving my apps? No reinstalling, no manual uninstalling from internal memory? But how about apps without apps2sd option, will they be unaffected? Or does ext2 simulate internal memory, so all apps can be installed there? If so, will apps from the Market then automatically be installed on ext2, with or without apps2sd?
Sounds great!
Thanks in advance,
Gerard
Click to expand...
Click to collapse
All you should have to do is reboot and the reboot might take longer than usual as CM7 would be transferring all your apps to the ext2 partition. All apps that are installed afterwards are installed on your ext2 partition.
Sent from my Milestone using XDA Premium App
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?
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.