Database Info

[Q] Does Overclock pay?

As the title says:
Does Overclock pay?
I especially mean, is it really remarkable on games (angry birds seasons eg), transitions, general performance?
Which method/apk u use(d)?
How much do you personal overclock?
Is it stable if phone´s use long times?
concerning this, what is a governour?
Thanks in advance for your answers

Rodsengard said:
As the title says:
Does Overclock pay?
I especially mean, is it really remarkable on games (angry birds seasons eg), transitions, general performance?
Which method/apk u use(d)?
How much do you personal overclock?
Is it stable if phone´s use long times?
concerning this, what is a governour?
Thanks in advance for your answers
Click to expand...
Click to collapse
Well to be brief it pays
Though the entire experience is not that good if you try to run an HDPI game on our LDPI device, you can experience some lag of half screens
but other games like angry birds and all run flawlessly
The FPS of the games increase by appreciable numbers(Like sandstorm and other gameloft games ), though I havent yet faced any stability issue (Except the frequent Market FC) other things work normally
I use Lagfree governor and Deadline I/o scheduler
In short words governor determines how the frequency of the cpu changes with respect to the load on it

Thank you for the reply.
So I know it pays to overclock, now, as I won´t brick my second fit, is a question to me, how do I do this in a secure way?
Is is depending which ROM I use?
Is it APP or do I have to flash Kernel?
If it is Kernel which one matches with my ROM?
Many Questions, but before I make this step, I´ll be as sure as possible about this topic.

i've OCed my galaxy fit and so far i'm getting the best of my phone without any drawback. well if there IS a drawback, i think the only drawback it has is because of the governor which causes the phone unstable.
and to answer what a governor is, it's simply like a CPU manager which controls ur CPU speed at anytime. suppose i put my phone in my pocket and i don't use it, of course i don't want my phone to work 100%, no? so the governor slows down the CPU speed. of course, u can control what is the minimum speed of ur CPU (so far it's as low as 122 MHz for galaxy fit) and also what is the maximum speed (so far it's as high as 801 MHz)
there's so many governors but so far, the most battery conserving, yet doesn't sacrifice your phone performance when u need it most, is interactiveX. and the most performance efficient, yet doesn't suck a lot of battery juice when u don't use ur phone, is smartassV2. if u wanna know more about governors and I/O schedulers u can check it here
so far, the only OC-able ROM i know for galaxy fit is CM7, which is still unofficial but working properly without any significant bugs. and yes it needs to be flashed using CWM (it's CWM v5.0 for galfit so far). after u do that, u need to install some app like "no frills CPU" (market available) or "setCPU" (also market available) to make use the governors and set the max or min speed for your CPU.
to sum it up, how to OC ur galaxy fit (if u're using stock ROM or by now, CREED's ROM):
1. install CWM (ClockworkMod Recovery) link for tutorials and reference
2. flash CM7 (CyanogenMod 7 custom ROM) using CWM. link for tutorials and reference
3. flash ur kernels using CWM also. link for tutorials and reference
4. install CPU manager app like no frills or setCPU.
5. set ur max/min CPU speed, and choose the governor properly.
*update*
sorry for the wrong link. and by the way, did u bricked ur previous galaxy fit by using ROM manager? if u did, be careful coz this CM7 is pre-installed with ROM manager. i suggest u uninstall it immediately after u've flashed ur CM7. install Titanium Backup then go to the backup/restore tab, search the ROM manager, then uninstall it. ROM manager still isn't compatible with galfit tho
that's it and i don't mind u clicking the thanks button

Thank you also for the comprehensive answer.
I just have another question to that (gosh I hope I don´t get annoying to you all folks):
As I am using CWM and running ext4 and did the backup of my actual sys and would flash to cm7 like described in your answer, the cm7 is working fine etc, will I be able to "switch" back to Creeds ROM by chosing my backup, using cwm or do I have to flash it all anew?

i'm afraid i don't know the answer to that, sir.
well say that u've done the backup now when u're in CREED's ROM, u flash it to CM7 then u wanna revert it back to CREED's ROM, i think the safest way is to flash it all new the CREED's ROM, then do the restore data using CWM.
well, my guts say that if u're in CM7 n u do the restore data in CWM, u'll get back your ol' CREED's ROM, but it's just my guts sayin

I´ll try and report

I tried to start, but your links lead all to the same, the cwm Install Instructions.
still need cm7 link (cuz I am not sure which one of that) for cwm and the oc kernel (which I also dunno, which one of them. So if you pleasssse ...

Rodsengard said:
I tried to start, but your links lead all to the same, the cwm Install Instructions.
still need cm7 link (cuz I am not sure which one of that) for cwm and the oc kernel (which I also dunno, which one of them. So if you pleasssse ...
Click to expand...
Click to collapse
LMAO! sorry for the wrong link. wait i'll update my previous post, will post here when finished
---------- Post added at 02:38 AM ---------- Previous post was at 02:28 AM ----------
okay, i've updated my post. it now should link you to the proper post. don't forget to check my note on that post too though.

thanks for correcting and also the notes.
Yeah I bricked it by using ROM Manager, but it was completely my fault.
I wanted to fast, without reading AND a special portion of being silly
If ya like read this:
http://forum.xda-developers.com/showthread.php?t=1367853
I do it with cwa this time backup is already made
edit: dunno what is meant by mount /system? What do I have to expect, when I am chosing this and what does it do?
As far as I understood is it being made between cm7 and oc-kernel installation. Right?

Rodsengard said:
thanks for correcting and also the notes.
Yeah I bricked it by using ROM Manager, but it was completely my fault.
I wanted to fast, without reading AND a special portion of being silly
If ya like read this:
http://forum.xda-developers.com/showthread.php?t=1367853
I do it with cwa this time backup is already made
edit: dunno what is meant by mount /system? What do I have to expect, when I am chosing this and what does it do?
As far as I understood is it being made between cm7 and oc-kernel installation. Right?
Click to expand...
Click to collapse
sorry for the long reply, it's sleep time in my country lol
mount system is a command to mount ur system folder in order to install the required. in this case, u're installing the kernel, so u need to mount the system in the recovery mode. to do that, go to recovery mode (since now u're using CM7 u can go to rec mode using the power button, choose reboot, choose recovery). then choose mount and storage, choose mount/system. don't worry, it's completely safe.
by the way, u also need to mount system for installing google apps in ur CM7 ROM. CM7 ROM is not preinstalled with google apps (including market, maps, and so on), so u need to install it manually using CWM also, flash the zip files provided in the tutorial thread. it's called gapps_bla bla bla if i remember correctly.
when i was flashing the google apps, i didn't get the market and maps application. so i install it manually using this link.
but i just read some guy with the same problem, n he said this.
haven't tried the later, maybe that'll work also.

bufosp said:
sorry for the long reply, it's sleep time in my country lol
mount system is a command to mount ur system folder in order to install the required. in this case, u're installing the kernel, so u need to mount the system in the recovery mode. to do that, go to recovery mode (since now u're using CM7 u can go to rec mode using the power button, choose reboot, choose recovery). then choose mount and storage, choose mount/system. don't worry, it's completely safe.
by the way, u also need to mount system for installing google apps in ur CM7 ROM. CM7 ROM is not preinstalled with google apps (including market, maps, and so on), so u need to install it manually using CWM also, flash the zip files provided in the tutorial thread. it's called gapps_bla bla bla if i remember correctly.
when i was flashing the google apps, i didn't get the market and maps application. so i install it manually using this link.
but i just read some guy with the same problem, n he said this.
haven't tried the later, maybe that'll work also.
Click to expand...
Click to collapse
Thanx again for all the effort. Sleep is an overestimated thing
But to be serious. I also slept and thought about that all and decided, first to stay with Creeds Rom, cuz it is fast, runs stable, looks good and has many features I apreciate.
Maybe I come back later to that point I wanna Install cm7oc, then I know where to look.

Still lets me no rest.
There´s still a new question in my head about the OC-Kernel.
there are many to chose, so which one is the most stable?
------------------------------ Smart boot 17 feature Governor, SIO, VR, BFQ, CFQ, Deadline, noop --------------------
Download Link for OverClock kernel (763Mhz ) smart boot 17 feature Governors
"> www.mediafire.com/?1jvyh6lv8qabdap <"
use CWM, and before flashing , dont forget to mount /system first and then flash this zip file
use no-Frills for OC and I/O setting
if get unstable , please set max 600 Mhz again, enjoy
DO IT WITH YOUR OWN RISK !!!!
------------------------------ Smart boot 17 feature Governor, SIO, VR, BFQ, CFQ, Deadline, noop with UV/GPU module --------------------
Download Link for OverClock kernel (763Mhz ) smart boot 17 feature Governors with UV/GPU module
"> www.mediafire.com/?i2f8wtt3occy7p3 <"
use CWM, and before flashing , dont forget to mount /system first and then flash this zip file
use no-Frills for OC and I/O setting
if get unstable , please set max 600 Mhz again, enjoy
DO IT WITH YOUR OWN RISK !!!!
------------------------------ Smart boot 17 feature Governor, SIO, VR, BFQ, CFQ, Deadline, noop --------------------
Download Link for OverClock kernel (801Mhz ) smart boot 17 feature Governors
"> www.mediafire.com/?a0a8lyfn0u0f0gg <"
use CWM, and before flashing , dont forget to mount /system first and then flash this zip file
use no-Frills for OC and I/O setting
if get unstable , please set max 600 Mhz again, enjoy
DO IT WITH YOUR OWN RISK !!!!
Click to expand...
Click to collapse

bufosp said:
but i just read some guy with the same problem, n he said this.
haven't tried the later, maybe that'll work also.
Click to expand...
Click to collapse
It sure does No hassles
Rodsengard said:
Still lets me no rest.
There´s still a new question in my head about the OC-Kernel.
there are many to chose, so which one is the most stable?
Click to expand...
Click to collapse
There are two 768 MHz and 801.2 MHz
Both are stable

There is also a general question about oc.
why can´t I just use an overclocktool like no-frills or cpumaster on any kernel?
They "promise" to increase speed, so why install OC Kernel first?
Although I know it must have a reason, cuz you oc-guys all do it.

kernel is the cars engine
no=frills is the accelerator
thats the way i understand it /

yes overclocking your device gives you that extra mile ..by which you can run apps faster ..your phones bagginess goes!!! but has its cons also!! ..it does reduce your life expectancy of cpu atleast theoretically .. and you will get reduced battery life + your device will heat up a bit more than usual! ..other than that its awesome to have an oc.

I finally can conclude, Overclocking really pays. And still I can decide to keep my OCed cell running with 600 at max or give it a little or maybe big OC.
Thank you all guys for helping me, sharing your knowledge.

I am searching for a program like no-frills, which can also decide by profile (maybe even autodetect) when my phones connected to charger ---> use this profile/governor, if it is running from battery ---> that profile.
Does a program like this exist?

Rodsengard said:
I am searching for a program like no-frills, which can also decide by profile (maybe even autodetect) when my phones connected to charger ---> use this profile/governor, if it is running from battery ---> that profile.
Does a program like this exist?
Click to expand...
Click to collapse
Try SetCPU
Sent from my GT-S5670 using Tapatalk

[User Thread] Mazout360's CM10.1 Weeklies for the LG-P999

The reason for this User Thread is so that we can keep the development thread clean. Post in the development thread only if you have something useful to contribute such as a logcat, or any dev-related comments. Post any suggestions, bug reports, questions or comments about the rom in this thread,
What's working and what's not?
Working:
Camera - Yes, this means Camcorder also works! 1080P Video shooting and playback work great.
Bluetooth
WiFi
Audio
SD Card Storage
Battery Meter
And of course Hardware Acceleration!
Not Working:
RIL (Mobile Network) - This means no calls, no SMS, no Data, no anything related to the functions of your SIM Card! T-Mobile WiFi Calling also doesn't work.
Information On Dual Booting Roms
Since we currently have an issue with the network radio on our CM10 roms, most people will not be able to use this rom as a daily driver, and would prefer to stay on a fully functioning GB rom. This dual booting method lets us have the best of both worlds! You can have a buttery smooth and fast CM10 rom for enjoying all of Android Jellybean 4.2.1 goodies and a fully function Gingerbread rom when ever you need to make a call and such. For now, this is the best we can do. It's simple and very fast to switch between roms. What else could you ask for? ;D
Installation Instructions Including Dual Booting
DISCLAIMER
I (WE) AM NOT RESPONSIBLE of any damages to your device related to the use of this ROM or the dualboot toolkit. You do this at your own risk. Even though this has been tested and works well, using NVFLASH may brick your device if done incorrectly.
This ROM comes in two flavours: The dualboot toolkit or the Original flashable ROM
Dualboot ROM Instructions
WARNING! NVFLASH will format EVERYTHING, including internalSD. Make sure you backup your important files on your externalSD card
PART 1 - Resizing system partition
1) Unzip the dualboot toolkit and unzip NVFLASH_Resizer-G2X.zip.
2) Power off your phone and remove the battery. Keep vol. up and vol. down held and plug the phone via USB to a WINDOWS computer.
3) Windows should add an "APX driver". Go to control panel -> Device manager and right click on it -> Update driver -> search in system. Then, browse to the drivers folder inside the NVFLASH package and choose nvidiausb.inf. Approve any error messages (Windows 8 users read my FAQ). Install the Nvidia Fastboot driver.
4) Unplug your phone and hold down vol.up and vol.down. Replug it again and double click on flash.bat inside the NVFLASH folder. KEEP BOTH BUTTONS HELD DOWN DURING THE WHOLE PROCESS!.
5) When NVFLASH is done, unplug the phone and put back the battery. Reboot into recovery with power + vol. down. Plug it back and go to mounts and storage -> mount USB storage. If your PC asks to format the internal SD card, select yes.​
PART 2 - Installing ROMS
1) Download the desired "call/SMS" ROM and extract boot.img from it's flashable zip. Rename it to boot1.img. Extract Step3_bootimg.zip from the dualboot toolkit and copy-paste boot1.img into system/boot, replacing the file that is already there. Repack Step3_bootimg.zip.
2) Copy-paste your desired ROM into the 0dualboot folder and send it to your device SDcard with everything it contains (your device should already be in the "mount USB storage" menu).
3) From the recovery, flash Step1_enabler.zip. When the screen goes black, hold power + vol. down to get back into recovery.
4) Flash your desired ROM, then Step2_ROM1.zip. Reboot to the OS.
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
And there you go! To switch from one OS to another, just open the systemchanger app and click on "switching"!
Credits to bihariel for the original method. See the original thread here.​
Original flashable zip ROM instructions
1) Boot into recovery with power + vol. down
2) Wipe data/cache, then mounts and storage -> format system
3) Flash this ROM
4) Advanced -> Wipe dalvik cache and fix permissions
5) Reboot and enjoy!​
Special trick : In settings, go to About phone and click 6 times on Build number. This will pop up the developer and performances options. In performances options, CPU settings, change the governor from INTERACTIVE to SMARTASSV2.
Downloads
ROM with DUALBOOT Toolkit ***BETA***
DOWNLOAD HERE!
Original flashable ZIP (For single boot)
DOWNLOAD HERE!
Credits
See Mazout360s original thread here for the full list!
Thanks to bihariel for the original method for the Optimus 2X which I adapted for the P999. Great job!
Special thanks to Core Memory for helping me start this project[/CENTER][/QUOTE]
*All Information On this User Thread is from Mazout360s Thread in the Dev forums. Credits go to him for the Instructions/Downloads/Etc.

Quick template for now.. I'll update it as soon as I can.

Mazout Kernel on Stock 2.3.4
I flashed Mazout360's GB kernel over kwes' rooted 2.3.4/March 2012 basebannd. Was running pretty smooth, but had some problems
> Bluetooth icon at top of screen did not turn off "connected" status when I turned off my headset (BlueAnt q2.1)
> Had a few freezes. Installed SetCPU to keep max speed at 1015MHz but still some stops. Some out of nowhere, some in the middlle of doing stuff
> Finally started shutting down often. Tried to get a terminal emulator from the Market, but Market started crashing, even after several reboots. Could not get a kmsg to send.
Reinstalled my nandroid. No time at the moment to play more, need my phone reliable for some days to come. Hope lots of people try this kernel out and that I get more time with it. Nice to have new Dev activity for the G2x.

Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.

grantusmantus said:
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
Click to expand...
Click to collapse
Shouldn't matter, but I always use Winrar.

Micro SD card not detected
I was following along the steps and everything was going well until step 5 in part 1. when i rebooted my phone into recovery and pulged it into the PC nothing happened even though i followed exactly what the steps say, then i continued on and everything was going well until the end, where i found out that i couldn't get the data that I backed up to my Micro SD card because the phone doesn't see it.
Please help, I'm a noob around here.

I appreciate all the great work

did this project die?

reeshmd23 said:
did this project die?
Click to expand...
Click to collapse
No it didn't. My build computer broke and I need to setup a new HDD with my build environment. I'll make a new version as soon as possible.

hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?

0b095 said:
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
Click to expand...
Click to collapse
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.

Hey. I got everything to work and am dualbooting nicely. My problem is kernel. I flashed a recent CM7 with this and everything went fine. Then I went to install the most recent CM7 kernel from Maz (the OC) and that works until I switch to Rom2 and back. Then the wifi gets an error and wont do anything. The kernel wont stick. Did I miss something?
Also, last night went to bed with my phone charging and when I woke up my phone was burning hot. Had Max OC at 1100.
Thanks! Works great having a taste of 4.2.1 and a phone!
Sent from my LG-P999 using xda app-developers app

Mazout360 said:
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Click to expand...
Click to collapse
thank you, I see the problem now, and two question more; do I have to redo PART 1 - Resizing system partition everytime when I install different rom combinations or reinstall same roms and does that Resizing system partition harmful/useless or slows down the phone IF I only use 1 ROM?

I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999

Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999

adamiscool said:
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
Click to expand...
Click to collapse
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything.
Edit: fyi I use maz's latest kernel 0205OC
Sent from my LG-P999 using xda app-developers app

Freakthis08 said:
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything
Click to expand...
Click to collapse
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app

adamiscool said:
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
When you system switch back to GB, reboot back into recovery and flash a kernel. I wouldn't say it goes back to stock because if it did there wouldn't be a wifi error like that. But for some reason JB works fine nothing wrong I have seen yet, though I just noticed I don't have a camera/gallery.
After switching back and forth so much I just flash the kernel and don't do anything else because nothing has seemingly changed if I wipe anything or fix anything.
If Maz has answer for this I would be much appreciated or anyone else for that matter.
Sent from my LG-P999 using xda app-developers app

Edit: figured it out. A new boot1.img does need to get made with the new kernel already installed.
I created a new boot.img per the instructions on the original dual boot for p990 thread with maz kernel. Then I repacked step3_bootimg. Reflashed rom2 and the step3, then voila! So, you have to redo a couple steps if you want to update one rom's kernel.
Pic no longer related.

guys im having some trouble, when i go to the systemchanger app and grant permission instead of the screen going blank it gets stuck on a screen with two lg logos.
i think i havent installed the fastboot drivers correctly. i assumed it gets installed when i run flash.bat, but it may need to be installed seperately. if it needs to be installed how do i do it cause its just a .bin file and i have no idea what to do with it
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
adamiscool said:
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Click to expand...
Click to collapse
hey, i have the same question, did u install the fastboot.bin separately or does it get installed with the flash.bat???

[Q] that .10 kernel-which power config?

I put on cromi-x 5.4 using that .8 kernel...All is good.. sort of ...
Main problems I have is Flixster doesnt seem to work. AND also with my precious Zen Pinball. Can't go into portrait mode. Had this problem on stock but it fixed as was perfect when it updated to stock .10 .. Would going to " _that's .10" solve this? If so, which cpu power config would be best? I noticed when you choose that kernel you get a choice of 3 and no indication of what is default. H.A.N.O. (Help A Noob Out)

Anyone got an opinion on which power config to use for the that.10 kernel.?? Anyone?Anyone?

toastman430 said:
I put on cromi-x 5.4 using that .8 kernel...All is good.. sort of ...
Main problems I have is Flixster doesnt seem to work. AND also with my precious Zen Pinball. Can't go into portrait mode. Had this problem on stock but it fixed as was perfect when it updated to stock .10 .. Would going to " _that's .10" solve this? If so, which cpu power config would be best? I noticed when you choose that kernel you get a choice of 3 and no indication of what is default. H.A.N.O. (Help A Noob Out)
Click to expand...
Click to collapse
I don't understand the question
What does power mode (power saving, balanced and performance) have to with portrait? I think you are confusing _thatv10 with the Aus stock upgrade .10. They are different things.
The default is 1Ghz / 1.5GHz / 1.7GHz. When you install _that in the rom installer you get 1.3/1.5, 1.5/1.8 or 1.3/1.8 (power saving stays the same).
If you install _that v10 you will just have 1.5/1.8 but you will still have the same issues.
I think you need to lookup how to take a logcat, start the app, let it fail to do what ever you expect it to do, then grab the logcat and post it here

sbdags said:
I don't understand the question
What does power mode (power saving, balanced and performance) have to with portrait? I think you are confusing _thatv10 with the Aus stock upgrade .10. They are different things.
The default is 1Ghz / 1.5GHz / 1.7GHz. When you install _that in the rom installer you get 1.3/1.5, 1.5/1.8 or 1.3/1.8 (power saving stays the same).
If you install _that v10 you will just have 1.5/1.8 but you will still have the same issues.
I think you need to lookup how to take a logcat, start the app, let it fail to do what ever you expect it to do, then grab the logcat and post it here
Click to expand...
Click to collapse
ok, so there's no correlation between the app and the kernel, got it..fine..
So I guess main questions now are..is the that.10 kernel so much better over the .8?
And if I went to .10, which config do people like?
Thanks for the understanding.

toastman430 said:
ok, so there's no correlation between the app and the kernel, got it..fine..
So I guess main questions now are..is the that.10 kernel so much better over the .8?
And if I went to .10, which config do people like?
Thanks for the understanding.
Click to expand...
Click to collapse
It's not It's basically the same kernel but _that added some stuff to add better preinit scripting for auto detecting partition types and using romn2sd and data2sd etc. For normal users _that v8 = _thatv10.
If you flash _that v10 you will lose the abilty to choose a config and be forced onto 1.5Hz and 1.8GHz as I already explained as you are just flashing a kernel and it will overwrite your cpu settings. You could use trickster mod to set the frequencies yourself of course

Lollipop improvements for HOXL

Hey guys and gals.
So I got myself a new/old HOXL and immediately flashed a Candy5 ROM on it with all lollipop and CM12 bells and whistles. To keep things even more interesting, I threw a nice package of google apps on top of it and enabled Google Now.
Guess what I found out immediately after my phone booted
My phone was sloooooooow. Like, it was fast for 1 hour or so after reboot and then it started to drag. After a day of moderate usage it became barely usable; sometimes I would miss a phone call because it wouldn't show me the bloody dialer and let me answer.
My phone was sucking battery like a thirsty camel in an oasis in the middle of Sahara desert... ok, ok, just don't throw that tomato at me. Anyway, I was losing 10-15% of my battery per hour.
So, I started messing around with the phone and found out several interesting things. I think it's worth sharing and discussing. In the next posts, I will share my findings with you. Please share yours.
My goal is pretty obvious: fast, smooth experience on CM12 and decent battery life. I was getting 2 full days of moderate usage on my good ol' HD2, so that's my current target with HOX. I also want Google Now working, at least to some extent. I especially like the feature when it shows me my parking location and things around me, so disabling locations altogether is not an option.

First step to smoothness: swap and OOM
DISCLAMER. The script below plays with your system settings. It might cause bootloops, brick your device or start nuclear war. Please use at your own risk.
So, first thing I noticed was that the phone was getting slow because it didn't have enough memory to run. I figure that CM12 and lollipop in general is probably optimized for 2GB RAM, whereas our device has only 1GB. So I tried to play with OOM values, but didn't get the desired results. So I went and enabled swap. Guess what? Works like a charm.
Here's how I did it:
1. install SuperSU from here .
2. open it and let it install its su module. this part might be tricky; for me, doing this via recovery didn't work and regular install didn't work either. i ended up having to open ADB terminal and setting SELinux to permissive manually, like so:
su
setenforce 0
and only after that did it succeed to push its su module to system/xbin.
3. go to SuperSU's settings and make sure you have checked the following:
a. Enable Superuser
b. Enable su during boot
c. Trust system user (this is not mandatory; however, if you don't check this, you will be flooded with requests to grant su to system apps)
4. after you have everything set up, reboot to recovery and install the attached zip like you would install a ROM.
5. reboot and enjoy your new silky smooth HOX
This script enables swap on data and cache. The files are pretty large, too: 250MB on data and 250MB on cache. I saw that even with this I still have plenty of room on data and cache to keep rolling. This gives me 0.5GB of swap, virtually enlarging my RAM to 1.5GB. This seems to be enough for all my needs.
The script also sets swappiness to 50, sets OOM to the values that work best for me at the moment and brings over several optimizations from my HD2 ROM. Feel free to edit the values and share.
EDIT: uninstalling script attached
EDIT2: scripts updated to reflect my latest changes.
EDIT3: reduced small (small_swap.zip) attached for those who want to use swap with ZRAM
Second step to smoothness: kernel
This step proved to be extremely important for smoothness. For some reason, stock CM12 kernel appears to be severely underoptimized... or the kernels that our devs generously made available for us are heavily overoptimized
To my best knowledge, currently there are only two kernels that work with LP and support swap: Torched Kernel v1.4 and Frosted Kernel.
IMPORTANT: if you are going to flash Torched kernel, be sure to flash LP version 1.3 or 1.4. Previous versions break swap, thus hurting speed and stability
IMPORTANT: if you are going to flash Bricked kernel, you ABSOLUTELY MUST flash the voltage table (see this post). First flash the kernel and then the voltage table. Not following this procedure can damage your phone.
I am currently using the Bricked kernel and the results are extremely impressive.
Third step to smoothness: Ext4 optimizations: disable journaling, enable dir_index
This step helps quite a bit if you decide to stay with ext4 for now. But even if you don't and want to switch to F2FS (see step 4), it's worth doing it on the /system partition.
WARNING. Journaling slows your system down quite a bit but it also adds stability. Please beware. You may lose your data or may even have to reflash your ROM in some extreme cases.
I never experienced any problems with non-journaling systems, but be aware that google enabled it for a reason.
Note: Your system might became unstable only if you forcefully shut the device down by long-pressing the power button or if you run out of battery. In case of normal work and normal shutdowns/restarts, everything will be fine.
1. Flash the attached zip (no_journal.zip).
2. Profit! Your cache, data and system partitions have no journaling now.
Fourth step to smoothness: F2FS
It took me some time to figure out this one, but it proved to be extremely helpful in terms of speed and general smoothness. Stability is yet to be tested, but I have it for ~24 hours now, and everything looks fine so far.
0. You need a F2FS-enabled TWRP. Luckily, we have jrior001 with us, who took care for that. Grab it from here (please thank jrior001 in his thread).
1. Install Torched kernel 1.4. (Bricked supports F2FS too, but for some reason, the performance is degraded and the stability is much worse than with Torched).
1a. If you had Bricked installed, remove undervolt script from /system/etc/init.d
2. Install attached zip (evita_F2FS_conversion_v2.0_pav.zip). This will enable you to work either with ext4 (with some extra optimizations) or with F2FS, so you can always go back without having to remove it. (note that you'll have to flash this zip each time you install a new kernel)
3. In TWRP, go to Backup, select data and cache and unselect system. I also disabled compression, just in case. Start the backup and wait for it to finish.
3a. STOP! Check that backup returned no errors. If there were errors during the backup, don't go any further or you'll lose your data!
4. Now connect your device to the PC. On PC, browse to Computer\One X\Internal Storage\TWRP\BACKUPS\<number of your device>\<latest backup>
5. You will see a bunch of files whose name contains ext4. For example, data.ext4.win.md5
6. Go ahead and change ext4 to f2fs for each file. The names should now look as follows: data.f2fs.win.md5
7. Back in TWRP, choose Restore -> your latest backup.
8. Sit back and relax while TWRP reformats your data and cache partitions as F2FS and restores all your data.
9. Reboot and enjoy!
10. If you'll ever want to go back to ext4, just go to TWRP, connect your device to the PC, on your PC, restore the original names of the backup files (rename f2fs to ext4), in TWRP choose restore and you're back to where you stated

First step to battery life: wakelocks
1. Go to Settings -> Privacy -> Privacy guard.
2. Scroll down till you reach the word Google.
3. Enable privacy for everything that starts with the word Google, including (!!!) Google Play Services.
4. Long-tap to enter each row and disable "keep awake" and "wake up" wherever applicable
Also, I use ServiceDisabler (from Play Store) to enter Google Play Services and disable Google Analytics
Second step to battery life: WIFI
Settings -> WI-FI -> three dots on top of the screen -> Advanced.
Disable "Keep WIFI on during sleep" (set to never) and "Scanning always available"
Third step to battery life: build.prop
Attached is my modified build.prop. It is derived from the stock build.prop, with some important tweaks that I brought over from my HD2 ROM. The measurements here are not that objective, but I felt that I could squeeze ~30% more juice from a single charge.
Of course, uninstall script is attached as well, just in case.
Fourth step to battery life: data usage
1. Head to Settings -> Data usage.
2. Scroll down till you see Google App.
3. Click on it and enable "Restrict app background data".
4. Go back and scroll further down till you find cLock.
5. Enable "Restrict app background data" as well.

for me

another one for me

last one for me

Cannot end a call by pressing the red button.. After unswap everything is normal again.. Can you please check it?
Nice work!!!!

How did u unswap ?
My phone was kinda cool.... Until I flashed this, my phone lagged the more.
Nice work BTW.
I want to unswap please!

Flash unswap.zip.. But i just notice that despite unswapping problem still persists.. Maybe it.s a cm12 bug.. I dont know

flashing unswap.zip should remove any traces of what swap.zip has done. if the problem persists after you flashed unswap, then the problem is elsewhere

I downgraded firmware from 2.18 to 2.15 and now i can terminate the calls.. I also install your swap file in latest cm12 02.19 nightly and seems to work fine..

I flashed Candy 5 and noticed that even after installing Torched kernel and overclocking, optimizing, etc, my phone would slow to a crawl by the end of the day and it definitely wasnt a memory problem as I had plenty free. What I found was that randomly my IO settings reset to 128Kb read-ahead and the scheduler resets to ROW. Changing back manually to 512Kb and FIOPS and suddenly the performance is back to what it was. This has happened twice in two days and I'm not sure if this is a Torched/CM/Candy/or Lollipop bug but at least I figured out what was causing it....

Hi thelonewolf_pav,
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work? I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now. I hope torched can figure out what the problem is. Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps. One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Thank You,

Hi harpin,
harpin14789 said:
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work?
Click to expand...
Click to collapse
nope. it starts alright, but it's never actually used
harpin14789 said:
I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now.
Click to expand...
Click to collapse
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
harpin14789 said:
Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps.
Click to expand...
Click to collapse
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
harpin14789 said:
One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Click to expand...
Click to collapse
very simple. run terminal from the phone or start ADB. then type:
free
Click to expand...
Click to collapse
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you

thelonewolf_pav said:
Hi harpin,
nope. it starts alright, but it's never actually used
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
very simple. run terminal from the phone or start ADB. then type:
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
Click to expand...
Click to collapse
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place

harpin14789 said:
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
Click to expand...
Click to collapse
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?

harpin14789 said:
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
Click to expand...
Click to collapse
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...

thelonewolf_pav said:
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
Click to expand...
Click to collapse
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks

harpin14789 said:
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
Click to expand...
Click to collapse
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all

thelonewolf_pav said:
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
Click to expand...
Click to collapse
ok, thanks

CTT mod improve performance eliminate lag updated 7/6

I've converted my CTT mod for the lg g3 to work with the nexus 7 this is now the official version as I've just been using it on a stock ROM with elementalx kernel and no problems so far so good should work with most ROMs.
Instructions,- Make a backup of your ROM and move your thermal files to a safe place. Then delete the originals Then boot into recovery flash mod and wipe caches reboot and enjoy
Right now these have only been tested on stock based ROMs but should work with any ROM
thermal mod 75 for stock kernel-
https://www.androidfilehost.com/?fid=24052804347769758
thermal mod 75 for elementalx kernel OC'd to 1.62 -
https://www.androidfilehost.com/?fid=24052804347769759
thermal mod 75 for elementalx kernel OC'd to 1.94 -
https://www.androidfilehost.com/?fid=24052804347769760
Please let me know what you think the more feedback the more improvement I can make
Thank Rob
Also here's the link to the original mod for the lg g3 to read up on what it does
http://forum.xda-developers.com/lg-g3/development/thermal-mod-t2907363?nocache=1

I want to try this with the new clean rom when it's released. I use your 75 mod on my g3. Can't wait.

What does the one for elementalX does?
I have elementalx's kernel but I just OC one step
Also, thanks for this mod, I have a G3 and have been following your mod since almost the start, and its been awsome, and also the fps unlock mod.
So glad your working on N7 too

Papote3 said:
What does the one for elementalX does?
I have elementalx's kernel but I just OC one step
Also, thanks for this mod, I have a G3 and have been following your mod since almost the start, and its been awsome, and also the fps unlock mod.
So glad your working on N7 too
Click to expand...
Click to collapse
there you go I made one for elemental x oc'd to 1.62 which should suit you in the op

Robshr said:
there you go I made one for elemental x oc'd to 1.62 which should suit you in the op
Click to expand...
Click to collapse
Thanks, will try and let you know

Robshr said:
there you go I made one for elemental x oc'd to 1.62 which should suit you in the op
Click to expand...
Click to collapse
Working great so far... What app do you use for displaying cpu frequency and temp on status bar?

Papote3 said:
Working great so far... What app do you use for displaying cpu frequency and temp on status bar?
Click to expand...
Click to collapse
I just use CPU temperature it has an overlay to display CPU in the status bar but only that I think I just open the app to see both the cpu temps and frequency as well as the battery temps

Is it necessary to clear Dalvik Cache after flashing this mode? It takes ages to complete that process, so I tend to avoid it as much as possible.
Also, isn't copy & pasting your modified thermal.conf file (after deleting the stock file) & then rebooting the device would be just fine?

Diljinder said:
Is it necessary to clear Dalvik Cache after flashing this mode? It takes ages to complete that process, so I tend to avoid it as much as possible.
Also, isn't copy & pasting your modified thermal.conf file (after deleting the stock file) & then rebooting the device would be just fine?
Click to expand...
Click to collapse
No it's not necessary and yes copying and pasting then rebooting would work
I just like to clear everything for good measure just to make sure there's nothing hanging around that would cause the mod not to work properly

Is it possible to unlock fps in this device?

I'm facing some weird unexpected issues with this mod.
I, first, copied & pasted the modified thermal file manually & rebooted the device. The device booted up normally but i experienced severe lag while using it. Normal operation like swiping through home screens etc seemed like at 5fps.
Thankfully, I had backed up before, so I restored it after proper clean up. Device worked normally. But I thought of giving it another chance, this time by following proper guide.
So I flashed the zip file, wiped Dalvik Cache/cache. But I experienced same issue as before. The device just got bogged down to crawl.
What exactly is causing this behaviour? Just to let you know, I use xposed on this device. Device is running Stock ROM with Stock Kernel & I used zip for Stock Kernel.

Just checked out the thermals in marshmallow and they have changed them to almost the same as my mod

Robshr said:
Just checked out the thermals in marshmallow and they have changed them to almost the same as my mod
Click to expand...
Click to collapse
Wow...if it was me, I wouldn't know if I'd be pleased or pissed off.........?