Related
Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4
mikerulez121 said:
Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4
Click to expand...
Click to collapse
Looks like only simple switches like "performance, userspace, etc" and for some reason advanced settings will make a difference. I believe persistent/kernel-level switches not provided for in the UI cannot work at present because we can't write to the build.prop, user.conf, or init.rc.
P.S., the DI's processor is upgraded from N1's. Same product line, newer model.
So im out of luck until a new kernel is out? Ok. But if i get a new kernel, will i be able to keep the default os or does that require a new rom?
Give 1.6 a try. Maybe it works for you.
larsdennert said:
Give 1.6 a try. Maybe it works for you.
Click to expand...
Click to collapse
Nope, even in 1.6 direct throttling still does/can not work, but seems like selecting userdata, performance, or ondemand has an effect on where the processor speed averages
You will need a overclocked kernal for SetCPU to work.
You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.
from my understanding is you will need an unlocked kernel and RW NAND
Berzerker7 said:
You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.
Click to expand...
Click to collapse
Now THAT makes sense. I'm not sure I want a Nand unlock; but I'd like an easier way to push stuff in recovery so I can make intentional tweaks and protect the OS the rest of the time.
Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
eljanor said:
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Now I'll check your link, thanks.
EDIT: GREAT! IT WORK PERFECTLY! Now it's only find the way to run at boot a script for activating wifi, but I think it's easy, with or without a program.
Thanks a lot
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
x1l0n said:
How did you try to do it?
Anyway, there are a lot of ways to do it. Let's try first with adb (I'm writting this for a windows environment, because I'm too lazy to boot into linux, so sorry):
You plug in your tattoo through UsB on your PC. You start your command prompt and go to the folder where adb.exe is contained. The you write adb pull /etc/init.d/02squashsf c:\02squashsf <- this will save 02squashsf from your tattoo to your pc in the c:\ directory/partition. After that open the 02squashsf file with ... notepad/notepad++ and comment the line as described in my previous post. After you save the now modified 02squashsf file go to command prompt again and execute : adb push c:\02squashsf /etc/init.d/02squashsf <- this will copy 02squashsf from your c:\ to your tattoo. Pretty easy!
2nd Way:
Start RootExplorer on your tattoo and go to the folder /etc/init.d. Then click the small button in the upper right corner which says "Mount as R/W" (this will mount the system partition as Read/Write access). Find the 02squashsf file and long click it (until the menu pops up) and then choose edit as text file (or something similar). After it has been opened comment out the line as described in my previous post and save the file after the modification. That is all.
By the way, there is a 3rd way - unpacking the squash and editing its contents to be correct. But I don't really have the time...
And remember that a backup takes only a few minutes to make, but a mistake can cost you hours to fix if you have no backup
Click to expand...
Click to collapse
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
eljanor said:
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
Click to expand...
Click to collapse
Eheheheheeh I'm using a safe "fourth way", that I thought.
A normal way (not that 3) is typing these commands on Terminal Emulator directly from the phone.
Well, so why don't insert them into "Preferences -> Initial command" and give to Terminal Emulator the superuser authorization (with flag "Remember")?
Now, every boot, I simply open Terminal Emulator with a link on the desktop, waiting few seconds and it work!
Sometimes the default power widget doesn't work, so I must enter in Settings -> WiFi and turn it on. But it work without typing nothing more or modify a system file
Baboo85 said:
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Click to expand...
Click to collapse
Talking about voltages, are they controllable in some accessible way? I'd give it a go any time if I could find any useful information on the subject. Any help?
Baboo85 said:
Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
Click to expand...
Click to collapse
Just a question of confirming something.
With the new SPQRom 0.7 room we still have to flash a new kernel like eljanor user advised?
[Q] SetCPU on Tattoo
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/show...767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
Or it's this new room already is ready to be Over-clocked?
Thanks in advance
So, how far have you guys have went? I've read that for some of you, 710 MHz is the stable max, but for me, my tattoo seems to crash occasionally on that clock speed. My stable max is one step lower, 691 MHz.
bladez said:
My stable max is one step lower, 691 MHz.
Click to expand...
Click to collapse
I agree. Most stable and powerful is 691MHz. I have tested tatto by System Benchmark from market and its shows max results on 619MHz, next 710MHz are got worst resulsts in Cpu and Graphics tests. 691MHz optimal.
I also experimented with System Benchmark, and I got the best results on 730, though it did reboot occasionally.
my is 680
Hi everybody...
I know I'm not a dev, but I like to explore my android phone. So you are developing, and right after i'll be trying to do it... on my own
I believe I followed all the steps refered in x8 overclock module thread in devs section, but since I can't ask this there, i'll ask it here.
1st - Download and unzip x8oc.zip (the right version), then copy x8oc.ko to system/lib/modules (I'm sure the file is there, system is mounted rw).
2nd - Edit hw_config.sh on pc with notepad++ (my edited file is attached) and "glue it" back to system/etc after editing.
3rd - Reboot... and then what?! It reboots, but when I go to set cpu, I have same frequencies as before (122-600mhz). So, my x8 is not overclocked right?!
Beside this steps do I need to do something else?! In set cpu, do I select any device configuration or just auto detect frequencies?!
Do I need to set custom frequencies in any other files?!
I've just tried lot's of changes and nothing worked.
Please help me on this...
I'm using floyo 0.15 on my x8, rooted and with xrecovery on it...
Thank you all
the attachment is correct..and don't change the set cpu. i use the same roms like yours
Do you think that having baseband version 006 instead of the 015 could be the cause for this problem? I never updated it...
Because, I've done it again without touching set cpu and still no overclock... If you say it's correct, then I really don't know what else could it be...
Thank anyway for the reply
I think it is very influential on baseband cuz for the rom said that use xx15,...if yours non xx15 so try to change it ...what you've applied on the hw_config is same on mine so it's quitely correct.
Hi mate
So, I'll tell you what i've done.
Went to SE's site and repaired to the original 2.1 so restarted the phone, updated to baseband 015, then root, then xrecovery... and then, installed miniCM. As you know, miniCM has an update.zip to easily overclock it to 710MHz.
I tried it and it worked fine. BUT! I prefer Floyo 0.15 (the best till the moment for me) and so I tried to do something, when I restored back to Floyo.
Adding the code to the original hw_config.sh in floyo's file didn't work again. So I thougt... Let's trie to put MiniCM's hw_config (the file that comes in the update.zip) to floyo's system. And... It's working FINE!!! I'm currently running at 749(x27)Mhz and it doesn't go off... it's stable. Also handles 767(x28)Mhz but it's not so stable. Now I'm really satisfied with my overclocked x8.
But there is one reason that made me think of where was the mistake.
When I opened floyo's original hw_config and added the code, in notepad++ it was apparently correct and the visual configuration of the file was equal to miniCM's hw_config file (already with the code). But, when I opened the both in wordpad, the file I edited had the same format as in notepad++ and the file from MiniCM had all together and a different layout. So I thought that it was possible that android wasn't reading the file well, since the configuration of the code was different. And it worked so smoothly
So my question is, does notepad++ write in the language needed for this to work?! or is there anything needed to change in order to make it legible to android system?
Thanks again
Sorry for all this noob questions, but since you use the same rom as mine, it's a good chance to ask what I don't know. lol
Our rom comes out with app2sd pre installed right?
So it was suposed that I could move some programs to sd.
But, when I go to settings/apps manager There's the option to move apps to sd, but they all say "fail moving the app".
What do I have to do to make it work well?! Heard that the sd had to be partitioned. What program did you use to do that?!
That's the only thing left to make x8 perfect and full of memory lol
Thanks
I managed to OC it manually to 710 MHz in miniCM6, BUT no performance increase was detected. Quadrant score was consistently lower (~750) compared to no overclock (~850),
Any ideas?
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
MaScXDA said:
I OCed it to 719MHZ with miniCM and i really felt an improvement. Switching menus and sliding on the home-screen (GO launcher) is really smoother.
Quadrant-Standard-Score:
@600MHz (ON DEMAND): ~520
@719MHz (PERFORMANCE): ~920
Click to expand...
Click to collapse
and about battery life, noticed any difference after OverClock your Phone?
biscoitu said:
and about battery life, noticed any difference after OverClock your Phone?
Click to expand...
Click to collapse
it drains a bit faster with the PERFORMANCE-govenor, but my phone is loaded every night anyway.
It is even less important to me, because when it reacts faster, i don't need to have it turned on as long as when it is laggy. And the display really needs most of the battery-power, so i may even save battery, when i can turn it off earlier.
Return to 600mhz
I can not use the overclock because when I reboot the phone it is on 691Mhz soon after he returns to 600mhz. I know that the CPU clock is dynamic, but he never returns to 691mhz. What did I do wrong? I used the XDA tutorial for overclocking.
Don't work yet
I just try full wipe and did not work. I think it's some parameter or file permission...
I'm wondering if I'm able to install an Overclock Kernel with this.
I'm using the Size-Agnostic SD Card image that loads CM7's latest build from the SD Card.
So I don't even know if the kernel would work for that, if so, how do I get it back to where I can select the kernal by booting with the SD Card? Obviously if I put another boot SD Card in it wouldn't work because the OS is missing.
Any help would be great, I'm just a little confused on all of this.
Thanks!
joehempel said:
I'm wondering if I'm able to install an Overclock Kernel with this.
I'm using the Size-Agnostic SD Card image that loads CM7's latest build from the SD Card.
So I don't even know if the kernel would work for that, if so, how do I get it back to where I can select the kernal by booting with the SD Card? Obviously if I put another boot SD Card in it wouldn't work because the OS is missing.
Any help would be great, I'm just a little confused on all of this.
Thanks!
Click to expand...
Click to collapse
I've running dal's 4/24 OC kernel and it's great! You do have to update the kernel via adb (as opposed to just flashing a zip); see DizzyDen's excellent instruction in post #2231 of
http://forum.xda-developers.com/showthread.php?t=925451&page=224
Good luck!
Hmmm......okay. I didn't do anything with ADB, according to this thread (They way I did the Install):
http://forum.xda-developers.com/showthread.php?t=1000957
I only had to replace the uImage file. And I did that on my PC before putting the card back in my nook. Changed the top speed to 925 rather than 800, and the min is set to 300. Thanks for letting me know about ADB!! I've got to get my PC setup to do that, I always get an error when trying to run it.
joehempel said:
Hmmm......okay. I didn't do anything with ADB, according to this thread (They way I did the Install):
http://forum.xda-developers.com/showthread.php?t=1000957
I only had to replace the uImage file. And I did that on my PC before putting the card back in my nook. Changed the top speed to 925 rather than 800, and the min is set to 300. Thanks for letting me know about ADB!! I've got to get my PC setup to do that, I always get an error when trying to run it.
Click to expand...
Click to collapse
I feel your pain. Initially I tried to manually replace the uImage only and then I got into trouble with quadrant -- see the top of post #2231 in the link I gave you. DizzyDen points out that addition files need to be updated (see post #2258 of the same thread), which is where ADB comes in (the quadrant went away after I updated the kernel via ADB).
Soo.....what's quadrant? I'm guessing a benchmark utility?
Also did you see increased battery life with the Overclocking?
I really only read on my Nook Color, so I'm hoping that it keeps it right around the 300Mhz and will increase the life.
You can run the 4/4 stable overclock kernel by just replacing the Uimage, it works fine as that is what I did. That procedure does not work with the test kernels though, and you apparently have to use the adb push method above.
Are the nightlys considered test kernels?
My problem with ADB right now is that I've got Java SDK installed, but when installing the ADB kit it says that I DON'T have it installed....huh??
joehempel said:
Are the nightlys considered test kernels?
Click to expand...
Click to collapse
No. CM7 nightly builds come with their own kernels. The OC kernels are what you put on to replace them. That is why, every time you update a new nightly, you need to reinstall the OC kernel.
The latest stable OC kernel is dated 4/4, the latest OC test kernel is dated 4/24.
For OC kernels up to 4/4, you can simply replace the uImage and you will have an OC kernel. For the test OC kernels, you will also need to adb push the system files that come with it or you will not be able to boot.
joehempel said:
Soo.....what's quadrant? I'm guessing a benchmark utility?
Also did you see increased battery life with the Overclocking?
I really only read on my Nook Color, so I'm hoping that it keeps it right around the 300Mhz and will increase the life.
Click to expand...
Click to collapse
Quadrant is a benchmarking app, yes.
Battery life would depend on how you set the CPU parameters. There should not be any difference between non-OC or OC kernels if you set max cpu cap at 800/950Mhz. But why limit it when you run an OC kernel?
Even if you set max cpu at 1.1/1.3Ghz with the OC kernel, you can set the governor at Conservative and on light usage it will not ramp up a lot.
Okay, thanks.
I'll just keep the one I have, it doesn't seem like I need to have it done via ADB, I don't plan on using my Nook Color as a tablet, I would rather have it clocked down to save battery.
First of all I would like to give credit where credit is due and say thank you to SamHaLeKe for all the work he put into this port and all the other Developers involved to bring ICS to the SGS
If you would like a full run down of this ROM and what is included as any new developments, please visit the ROM thread
Now off to the good bits ...
Install
I AM NOT RESPONSIBLE IF SOMETHING GOES WRONG AND YOUR PHONE CEASES TO WORK. THIS IS NOT A DETAILED WALK THROUGH BY ANY MEANS. I AM ASSUMING YOU READ ONE OF THE MANY OTHER TELUS THREADS THAT HAVE THE FULL INSTRUCTIONS INCLUDED TO PERFORM THE BELOW STEPS.
Note: I am not going to post all the links to files as I do not have the time to update them everyday when something changes. I will however post links to the ROM and Kernel threads for your reference.
I decided to start fresh (and I mean fresh) from stock FROYO with a full SD format and the works.
Step 1
Flashed back to stock with ODIN. Again I used FROYO but I am sure GB would work. If you want to start fresh as I did, go to options storage and format the internal SD (13 GB).
Step 2
Download the ROM and Glitch V13 kernel (what I used) and copy them to the SD card of the phone. I suggest removing any external SD as not to copy the files to the wrong spot (guess what I did LOL).
Step 3
Flash voodoo kernel from ODIN to root and install clockwork recovery making sure that you do not repartition in ODIN
Step 4 - Note: The older voodoo kernel gave an "assert failed" error trying to flash the ROM through recovery)
Boot into recovery and wipe cache and dalvik then flash the Glitch V13 kernel from zip and reboot. At this point you will most likely be boot looping but no worries everything is OK
Step 4
Pull the battery and then boot into recovery with volume up + volume down +power. Wipe cache and dalvik and flash the ROM from the ZIP
Let the ROM boot and then again boot to recovery and flash the essentials zip.
Voila you should be running S.U.R.F.A.C.E ICS, aint it beautiful?
I continued and flashed add on packs 1 and 2 but that is up to you
Now for my findings thus far ...
I am in no way a power user when it comes to my phone but I do play with it a lot. I have to say that this ROM seems to be the one of the smoothest to date and seems to take to our device nicely.
Battery has been nothing short of great for me. Through the week I can easily get 2 days out of it (work all day). Now I also try to minimize the drain by turning off whatever I don't need like WIFI seeing as there is none where I work.
I flashed the JL3 modem and it seems to work good for me but then I don't live where you do so you may have better luck with another.
The kernel included in the ROM (if you read the ROM post) is Glitch V14 pre which runs amazing as usual although still in the development stage. This kernel has a lot of new features that I will let you read up on yourself here
The ROM also includes supercharger and thunderbolt scripts (I admit I have little to no experience with these but I do know they help).
No FC's with this ROM other then the video camera but I have seen some posts regarding this and have not got around to working on it but will be I am sure very soon. It looks like just a file update maybe but too soon to tell.
Live overclock seems to work if I leave the voltage settings alone but that could just be a lack of experience in this area but it never hurts to try. If anyone has settings that are working for them I would love to know what they are. I have set the live overclock to 120% or 1.2ghz and it runs fine again if I do not change the voltage.
It's only been about 3 days since the install but this is what I got so far. I would recommend giving it a try for sure.
I know there are a few of us on this ROM so post up your findings here.
Thank you
Buck
Similar but running Glitch v14
Thanks for the write up Buck. I have been running this rom (Surface) for a few days also but I came from cm7 to this one. I have also been toying around with it over the last few days which has gotten me in a few tight spots lol. I have my Volt control set to 1304, no voltage changes and it runs flawlessly. The modem I put on was the JVT which also seems to work well.
What I have learn about Live OC:
First you set your clock speed in Volt control, then flip over to NStools (that is the easy part)
IMPORTANT.... If you choose to mess with this, make sure settings in NStools is NOT set to apply on boot or make sure you have a good recovery to go back to. Found this out the hard way
Click on live oc and you can make changes here... If you read the articale from Glitch on this it will help alot (found in the OP for T959D).
Live oc clocks up the cpu AND bus so it affects the gpu and memory along with the cpu (very important).
Findings... some settings work fine, 105, 106,110, 114, 116. 115 seems to have issues and provides lower performance considerably lower.
I use AnTuTu to check how things are working. That being said, if you apply set at boot and you hit a setting that first craps out the phone, causes a reboot then your going to be in a bootloop or it will start reboot start reboot. This is why you DON'T do this or like I said earlier have a good recovery handy.
Right now I am only running 1304 and 100% and everything is fine except the prior mentioned FC on video cam. Oh I should mention also I am running the Lazy governor atm which also seems to work fine (default is on demand).
Anyways
Well I think we may have broken the record for the longest 2 posts on the first page in xda history lol. Happy flash year everyone
Sent from my GT-I9000 using XDA App
Didn't notice you guys mention this, but Glitch V14 has an option in CWM to clear NSTools settings. It's right above the option to clear voltage settings under the Glitch Menu.
It works well, believe me!!
-Maniac
I'm on ICS!
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
baino said:
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
Click to expand...
Click to collapse
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
bucknetbucky said:
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
Click to expand...
Click to collapse
Hey Guys,
Why not just use rom toolbox? the build.prop tweaks give ya a niffty slider... no hackin involved...
Anyone got the files for stock GB?
cowvun said:
Anyone got the files for stock GB?
Click to expand...
Click to collapse
you looking for T959D?
Yes
Sent from my T959D on Darky's Rom 10.3.
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
baino said:
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
Click to expand...
Click to collapse
Nothing like that here maybe the way it was flashed I am not sure. Have you added anything?
Sent from my GT-I9000 using XDA App
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
baino said:
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
Click to expand...
Click to collapse
Depends what you did before flashing. I had issues after flashing a lot and never deleting anything lol
Sent from my GT-I9000 using XDA App
Working NSTools values for OC and UV
CPU:
Governor = Lazy
Min CPU = 100 (109 after live OC)
Max CPU = 1200 (1308 after live OC)
OC Value = 109%
Deep Idle = On
Custom Voltage
Arm:
1400 = unchanged
1304 = 1375
1200 = 1325
1000 = 1225
800 = 1150
400 = 975
200 = 875
100 = 875
Int Voltage
1400 = Unchanged
1304 = 1150
1200 = 1125
1000 = 1075
800 = 1050
400 = 1025
200 = 1025
100 = 925
Just set these values tonight and so far all is good and no crashes or reboots. See if it helps the battery as the days go by. Give it a shot or post your working values for others to try.
AND NO I NEVER SLEEP
bucknetbucky said:
Working NSTools values for OC and UV
Click to expand...
Click to collapse
Thanks for posting your OC and UV values. I'll give those a try.
I've been experiencing random crashes and reboots (woke up this morning to a dead phone). It was plugged in overnight but crashed at some point and did not charge. Battery voltage dropped down to almost nothing.
Anyone else experiencing random reboots?
I was using an OC value of 1304 (no live OC). UV values left stock. Ondemand governor, Deep idle ON, noop IO scheduler.
I did not format my sdcard prior to install. Just did a data wipe/factory reset, format cache and dalvik then installed according to the instructions. Installed Add-on Essentials and Add-on Pack One. All other apps were reinstalled from the market (after using market enabler and changing DPI back to 240 using ROM manager).
Everything works great except for the random crashes and reboots. I'll probably start from scratch again when v1.3 comes out (except I will format the SD card). Maybe even start from stock Froyo as recommended in the OP.
EDIT:
Tried the settings and my phone was not happy. It froze when setting the UV values. My phone seems to have a problem with any live OC value other than 100%. As soon as I increase it I lose all stability.
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Settings
I'm on Glitch v14 pre5 and I just clocked it up to 1300 and added 104% live OC for a stable 1352, no undervolting battery sitting @ 68% 1 day 22hrs. I did turn off some stuff I dont use and had data running on and off for the whole time.
For the guys that are having problems with flashes, I generally wipe everything I know its a pain but I don't experience any problems either. I also wait until i have a full battery too. It seems to pay off in the long run...
Happy Flashing!!!
Phone and contacts are working well now, but I can't get app data to save. For example some apps t's&c's keep asking for approval everytime I open the app. Also beautiful widgets skins keep reverting back to default. I'm going to wipe, format the SD card and install 1.3 from stock Froyo. here's hoping.
bucknetbucky said:
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just wiped and running 1.3 now. So far seems much better and faster than my last flash. You guys know of any way to change the haptic feedback intensity in ics?