Database Users

SetCPU on Incredible?

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.

[Q] Overclocking and Agnostic CM7 OS

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.

[TELUS T959D Fascinate]-Running S.U.R.F.A.C.E ICS

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?

CleanRom 2.62 Inheritance for TF300T

I have the TW version of TF-300T in HK, i'm already have root my tablet and tries more custom OC Kernel roms (1.6Ghz - firmware 10.4.2.17) eg. [email protected] and BlueAndrid V.1.0 from surdu_petru which are success to run in !
Cause i like this rom and wanna to improve my tablet's OC performance and tries more times to flash the Clemsyn's "CleanRom 2.6-2.6.2 Inheritance" or "Energy JB rom" on whole day but i got same problems upon completed for the following items:-
1. OC 1.8Ghz by system turner pro or setCPU when run benchmark test of Antutu 3.0.2 just got not more over 13200 marks ; not more than 4800 for Quadant Standard edition on both "performance" mode ( same marks nearly OC even set to 1.6 or 1.7Ghz) ,
2. i got same can't read problem to about my 64G mircoSD(exfat format) on your all verson of roms ,even upon install Stock file manager or other file apps........just can read internal SD only ,can fix it or caused my wrong install steps?.......need reflash the stock Kernel as first than choice option OC Kernels?
3. How to install the correct step of all and Data2SD app patch on my tablet ....i got black screen and FC upon flash in ......sorry i'm just a new hand here!
Hope someone can help for solve my problems....thank you so much

Which recovery do you use ?
Try TWRP Recovery which is the recovery most functional. I use it and I have no problem for read my Sd card 32GB (NTFS format- 22Gb and Fat 32-10 Gb)
And I use Es File Explorer with root rights

[Mod] Disable ZRAM [Swap] in Marshmallow

For those that remember @EarlyMon posted how to disable Swap long ago when the 5x was on Lollipop.
Well since the 5x has been updated to Marshmallow this method no longer works. So I started looking around for a solution
and I found this >> https://forum.xda-developers.com/moto-g4/development/mod-disable-zram-t3435613
Turns out this works just fine on the Honor 5x on Marshmallow.
If you'd like to give it a try, I have updated the files from the post above and uploaded them to my AFH Here
Here is a copy / paste of the instructions from the post above by @redbeard1083 ...Thanks Go to him and EarlyMon
We hate zram. This easy mod will disable it on the stock Moto G4 rom. In our experiences with disabling zram we've been able to notice performance gains on devices from 1-3gb of ram (Moto E 2015, Moto G 2014, Honor 5X, Huawei GX8).
8/13/16 Update: Now flashable via TWRP.
1. Have TWRP and MAKE A NANDROID BACKUP BEFORE YOU DO ANYTHING. I am not responsible if you break your phone. If you don't already know how to restore your device to the way it was when you bought it, do not do any of this.
2. Flash via TWRP:
Zram Off: https://www.androidfilehost.com/?fid=24588232905722629
To return to stock (I cannot promise this is exactly the same as the G4 Plus. If any G4 Plus users want to send me a hastebin of the /system/etc/init.qcom.zram.sh file to compare that would help).
Zram On: https://www.androidfilehost.com/?fid=24588232905722630
Old instructions if you prefer to do it manually:
1. Be rooted.
2. Have a stock nandroid backup.
3. Backup /system/etc/init.qcom.zram.sh to some safe place.
4. Unzip MotoG4_Zram_Disable
5. Using root file manager of your choice (I like Solid Explorer) copy init.qcom.zram.sh to /system/etc folder and overwrite the existing file.
This has been tested working on the XT1625 and likely works on the G4 Plus as well. If this works for you on a different variant, please leave a reply and I'll do my best to update this post.
Links:
Disable Zram: https://www.androidfilehost.com/?fid=24588232905722479
If for some unholy reason you'd like to turn it back on, follow the same process copying your backed up init.qcom.ram.sh file back to /system/etc.
Thanks to @EarlyMon for his edits that allow us to keep zram disabled without having to run terminal commands at every boot.
Click to expand...
Click to collapse
Again you can use my files or the ones from the original post (they both work)
Also Remember on the H5x you can Boot TWRP recovery to do the flash
Code:
fastboot boot kiwi_twrp_recovery.img
Have fun !

Reserved

thanks, I will try it.
one question tho, how can I know that zram is now disabled? like will I see an improvement in ram management or phone will be more fluid??
in my knowledge, zram manages the background process by compressing the actual process behind, (when the app is not running , but stays in the recent apps) and decompressing the task when we choose it..so this causes some lag.. and if we remove zram, the phone will be much snappy??
please correct me if I'm wrong.. thanks for your work

one question tho, im on b370 kiwl22 now, (the firmware which causes bootloops for custom roms), can i flash it??

thilak devraj said:
thanks, I will try it.
one question tho, how can I know that zram is now disabled? like will I see an improvement in ram management or phone will be more fluid??
in my knowledge, zram manages the background process by compressing the actual process behind, (when the app is not running , but stays in the recent apps) and decompressing the task when we choose it..so this causes some lag.. and if we remove zram, the phone will be much snappy??
please correct me if I'm wrong.. thanks for your work
Click to expand...
Click to collapse
I use Ram Truth to verify the swap is gone.
theirs plenty of discussion on if you want to disable it or not, start with the links i posted and follow it to the h5x thread on disabling swap
most people see an immediate improvement in the phone. zram is a stupid waste of CPU cycles on a phone with more that 1gb or ram
thilak devraj said:
one question tho, im on b370 kiwl22 now, (the firmware which causes bootloops for custom roms), can i flash it??
Click to expand...
Click to collapse
yes it should work just fine

clsA said:
I use Ram Truth to verify the swap is gone.
theirs plenty of discussion on if you want to disable it or not, start with the links i posted and follow it to the h5x thread on disabling swap
most people see an immediate improvement in the phone. zram is a stupid waste of CPU cycles on a phone with more that 1gb or ram
yes it should work just fine
Click to expand...
Click to collapse
thank you for the info and letting me know about ram truth

working like a charm.. I can see some performance improvements