FEB-9-15 [] Post_boot tweaks - An *interactive* boost - AT&T Galaxy Note 3 General

Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0

Man that's one hell of a disclaimer.

Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.

Was wondering if anyone tried this, ill wait til after you update n test!

Updated dl link.. give it a go

I tried it didn't seem to have a noticeable difference in my opinion . I of course used the first script have yet to try the update.

Tried it
red_can_soda said:
Updated dl link.. give it a go
Click to expand...
Click to collapse
My phone started rebooting after 2 to 3 minutes....not sure what it is..perhaps low voltage or frequency...

red_can_soda said:
Updated dl link.. give it a go
Click to expand...
Click to collapse
Been running it all day no issues.

carl1961 said:
Been running it all day no issues.
Click to expand...
Click to collapse
Notice any improvement?

setfly95 said:
Notice any improvement?
Click to expand...
Click to collapse
I really haven't had time to notice, I will know in a few days.

Related

[Q] SetCPU on Tattoo

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

[Q] x8 does not overclock

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...

[REF] Nexus S ROM&Kernel Survival Guide

Introduction:
Please read and try to do some research instead of bombarding the developers with the same questions over and over, cluttering the threads with useless and recursive information. I will try to include terms for all the ROMs and Kernels in the Development Section, and remove the obvious things as much as possible. That doesn’t mean it will be perfect! I hope this will be useful for beginners, because it provides most of the basic information you need to get started. From now on, it’s up to you what you do.
I am fully aware that the information included here is for one time use, enough to get you started. Some of these things ARE well known by many of you, but they are still useful for others that are just beginning to learn about their NS. Besides definitions and explanations, I’ll also link to useful posts around xda and other sites, which provide further information on the respective subject.
ROMs​(ROM: a firmware that contains the Android operating system, and at least critical apps necessary for running your phone (but usually more apps than just those); can be stock or custom, and comes packaged in a *.zip file, flashable under recovery)
AOSP-built ROMs
Features: these are built from source code, from the Android Open Source Project, delivered free of bloatware and with rich customizations.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyanogenMod 9 (still in alpha stages for now)
IML74K Android 4.0.3 Build 4 - Quad Lockscreen + More MODS (1/15/12)
nuhetri- v1.0.0
Slim ICS
AOSP+ V2.3|ICS 4.0.3|Source Built|Status Bar Widgets + Nice Mods
4G VERSION
vhgomez36-ICS-NXS-4G-4.0.3 r2.0
IML74K Android 4.0.3 Build 3 - Quad Lockscreen+More MODS
Crossbones v0.1.3
CyanogenMod 9 v4.0.3 - Alpha 20
Click to expand...
Click to collapse
Moddified ROMs
Features: these are modified versions of stock/AOSP ROMs/other custom ROMs, that keep the look of the base ROM up to a certain point. Also generally free of bloatware and with some additional modifications.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyberGR-MOD|NS.NGN ver. 4.0 Ultimate
NSCollab 1.0.60
Ultimate ICS v4.0
-=Nexus MV 1.12.09=-
KANGY6 | ICS | AOKP |
NexusBeam 4.2.3
CyberGR-MOD|NS.NGN ver. 3.0 Hybrid ICS
Click to expand...
Click to collapse
MIUI-style ROMs
Features: unique type of ROM, developed by the Chinese. Has a strong iOS feel, highly customizable.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
◄ ▌ [09.Jan.12] [ROM] Brainmaster's MIUI 2.1.6 ICS | Stable 2.3.7b v2 GB ▌►
DianXin OS (DX ROM) ICS | GB ROM
4G VERSION
◄ ▌ [28.Nov.11] [ROM] brainmaster's MIUI NS4G 1.11.25 | OTA ▌►
Click to expand...
Click to collapse
Stock ROM
Official releases from Google. The reasons most people here flash a stock ROM are: they want to update/ are bored of custom ROMs/ want to start over with their phone/ warranty reasons.
If you want to go back to stock for some reason, check this thread and read carefully, so you get the correct version for you.
Click to expand...
Click to collapse
Once we decide for a type or ROM (except stock), we head over to the ROMs thread and begin reading the list of features. Now would be a good time to PANIC! No, no, just kidding Those words do exist in some kind of language (not necessarily English). So here’s a very basic list of the most common terms found in our ROM threads:
Code:
[B]AOSP[/B]
[quote]Short for [url=http://source.android.com/]Android Open Source Project[/url]. Its purpose is to maintain the development
of the Android platform. Anyone can use the Android source code for
any purpose, and this is when custom ROMs come in. The [AOSP]
tag is used here to signal a ROM built from Google’s source, a pure
ROM, free of bloatware, with very good performance (generally)
and a very extended degree of customization. [/quote]
[B]Build.prop[/B]
[quote]This file is located in /system/build.prop. It holds the majority
of the runtime flags that are used when Android boots. Basically, it
lists specific information about your device, for applications to use.
You can also edit lines, with a file manager that has access to
/system, in order to change LCD density, build number, device
model and many more. [/quote]
[B]Busybox(ed)[/B]
[quote]Busybox is a collection of simple, but powerful Linux
utilities, that Android doesn't come with by default. It is used
by applications like MetaMorph and Titanium backup in order
to do special operations. You can manage ther version installed
on your phone with various apps from the [url=https://market.android.com/search?q=busybox&c=apps]market[/url] [/quote]
[B]/boot partition[/B]
[quote]This partition includes the bootloader and kernel, and
it enables the phone to boot. Wiping it must be done only if
requested, and the phone must not be rebooted after this operation.
Instalation of a new one is done by flashing a ROM that includes
the /boot partition. [/quote]
[B]/cache partition[/B]
[quote]Inside this partition, Android stores frequently accessed
data and app components. Performing a wipe of the /cache does
not affect personal settings or files, but simply gets rid of existing
data there, which gets automatically rebuilt in time. [/quote]
[B]Dalvik cache[/B]
[quote]Dalvik cache collects the information about the installed
applications and frameworks, and organizes them into a writeable
cache. Under this writeable cache, it stores the “optimized”
bytecode of the applications which is used by the applications
themselves later for a smoother operation. This dalvik cache can
grow as more applications are installed on your phone. It is safe
to wipe dalvik-cache. It will be rebuilt again when the phone
boots. This also explains why your phone takes ages to start up
for the first time. [/quote]
[B]/data partition[/B]
[quote]Also called userdata, the data partition contains the user’s
data – this is where your contacts, messages, settings and apps
that you have installed go. Wiping this partition essentially performs
a factory reset on your device, restoring it to the way it was
when you first booted it, or the way it was after the last official
or custom ROM installation. When you perform a wipe data/factory
reset from recovery, it is this partition that you are wiping. [/quote]
[B]Deodex(ed)[/B]
[quote]In Android file system, applications come in packages with
the extension .apk. These application packages, or APKs contain
certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application
that are optimized before booting. Doing so speeds up the boot
process, as it preloads part of an application. Deodexing is basically
repackaging of these APKs in a certain way, such that they are
reassembled into classes.dex files. By doing that, all pieces of an
application package are put together back in one place, thus
eliminating the worry of a modified APK conflicting with some
separate odexed parts. The advantage of deodexing is in modification possibilities. On the other hand, since the .odex files were supposed
to quickly build the dalvik cache, removing them would mean
longer initial boot times. However, this is true only for the first
ever boot after deodexing, since the cache would still get built
over time as applications are used. [/quote]
[B]EFS folder[/B]
[quote]This is a VERY important folder. It contains phone-specific
information, like IMEI (encrypted in the nv_data.bin), wireless
devices MAC addresses, product code (also in the nv_data.bin)
and more. I advise you to make a backup of this folder, and keep
it safe. Remember, backup BEFORE flashing anything. Use [url=http://forum.xda-developers.com/showthread.php?t=1138873]this tool from forum member Borky_16[/url]. [/quote]
[B]Init.d[/B]
[quote]Init.d is very useful because it runs scripts that you can
just delete or replace in the /system/etc/init.d folder. The scripts
are also very flexible and can be used to call other scripts or set
a variety of system settings. [/quote]
[B]G-apps/Gapps[/B]
[quote]A long time ago, in a galaxy far far away, there was a
developer. And he used the Force for developing something called
CyanogenMod. For the happiness of the other folks in the galaxy,
he included some applications from Google. But the Emperor…
oh, sorry… But Google didn’t agree with him including these
proprietary apps, so they sent him a cease and desist letter.
Long story short, the Google Applications are provided separately
via a flashable .zip file. This is the case for pure AOSP ROMs,
and theoretically this is how it should be done. Theoretically. [/quote]
[B]Host File[/B]
[quote]Located in the /etc/ folder, it is used to block ads.
Most ROMs come with a “blocks ~95% of ads” statement. You
can also manage it with apps from the [url=https://market.android.com/search?q=ad+block&c=apps]market[/url]. [/quote]
[B]Logcat[/B]
[quote]The Android logging system provides a mechanism for
collecting and viewing system debug output. Logs from various
applications and portions of the system are collected in a series
of circular buffers, which then can be viewed and filtered by
the logcat command. You can use logcat from an ADB shell to view
the log messages.[/quote]
[B]NANDroid[/B]
[quote]When you take NANDroid backup, it means you are
backing up entire ROM. It’s basically a picture of the ROMs’
state . So when something goes wrong, you have the
chance to restore your phone to the backup state using the NANDroid. [/quote]
[B]NSTools[/B]
[quote]An essential tool that manages tweaks like BLN,
BLD, BLX, Liveoc, OC, CPU Governor, Deep idle and so on.
Written by arifhn, available in the [url=https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result#?t=W251bGwsMSwyLDEsIm1vYmkuY3lhbm4ubnN0b29scyJd]market[/url] and on [url=http://forum.xda-developers.com/showthread.php?t=1333696]xda[/url],
this is a must have application for managing these various options. [/quote]
[B]Odex[/B]
[quote]These ‘odex’ files are actually collections of parts
of an application that are optimized before booting. Also explained at deodex(ed). [/quote]
[B]Power Menu[/B]
[quote]A multiple choice menu that appears when long pressing
the power button. In stock, these are critical options,
such as powering down the device. Developers have also
added options for taking snapshots,
rebooting normally/into bootloader/into recovery and so on. [/quote]
[B]Radio[/B]
[quote]The radio controls basic low-level functions like
network connectivity, Wi-Fi, and GPS. It comes as a radio.img file,
and generally, developers try to leave this out of their
ROMs because different areas require different radios. Pay attention
to this when choosing to flash a new ROM. There is a reference
thread with all the radios [url=http://forum.xda-developers.com/showthread.php?t=1116884]HERE[/url]. [/quote]
[B]Ramdisk[/B]
[quote]Ramdisk.img is a small partition image that is mounted
read-only by the kernel at boot time. It only contains /init
and a few config files. It is used to start init, which will
mount the rest of the system images properly and run the
init procedure. A Ramdisk is a standard Linux feature. [/quote]
[B]Recovery[/B]
[quote]Recovery mode in Android provides an environment for
users to wipe cache, data, factory reset the phone or update
it with a .zip file. There are custom recoveries like [url=http://www.clockworkmod.com/rommanager]ClockworkMod[/url] or [url=http://forum.xda-developers.com/showthread.php?t=1399565]TWRP[/url], which provide additional functionality,
and are very popular for this reason. [/quote]
[B]RTL[/B]
[quote]Short for Right-to-Left and refers to support for languages requiring this type of writing. [/quote]
[B]SetCPU[/B]
[quote]An application built by coolbho3000, which allows CPU speed tweaking and management, allows overclocking, and sets CPU governors. Available on [url=http://forum.xda-developers.com/showthread.php?t=505419]xda[/url] and the [url=https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.]market[/url] (try to buy from the market if you want to support his work). [/quote]
[B]SIM Toolkit (STK)[/B]
[quote]Now if you live in the States, you might not even know what
the STK is, so a bit of explaining is in order. Put simply, the STK
allows carriers to load a simple set of menus and 'applications' on
your SIM card. Earlier versions of Android, up to 1.6, actually
included a rather rough, but functional Sim Toolkit application, but
at some point it was dropped. [/quote]
[B]/system Partition[/B]
[quote]This partition basically contains the entire operating system,
except the kernel and the bootloader. This includes the Android
user interface as well as all the system applications that come
pre-installed on the device. Wiping this partition will remove Android
from the device without rendering it unbootable, and you will
still be able to put the phone into recovery or bootloader mode
to install a new ROM. [/quote]
[B]Unsecured Boot.img[/B]
[quote]Used for adb remount, gets you root by default on a shell. (ro.secure=0) [/quote]
[B]V6 Supercharger Script[/B]
[quote]A more technical explanation could be done here, but
the bottom line is that this is used to make your phone run
faster, by better management of memory. [/quote]
[B]Zipaling[/B]
[quote]Zipalign is an archive alignment tool introduced first
time with 1.6 Android SDK (software development kit). It
optimizes the way an Android application package (APK) is
packaged. Doing so enables the Android operating system to
interact with the application more efficiently, and hence has
the potential to make the application and overall the whole
system much faster. Execution time is minimized for zipaligned
applications, resulting is lesser amount of RAM consumption
when running the APK. [/quote]
Kernels​
(Kernel: provides the most basic level of control over all of the phone's hardware; consider them a link between the hardware components and the ROM)
With kernels it’s a little bit easier. At least this is how it may seem. Right after rooting the device, many choose to first flash a kernel (including me) mostly because it gives the opportunity to flash something while not modifying the appearance of the phone. Furthermore, it gives you the ability to change things like CPU clock speed, internal and ARM voltages, and also have different patches and mods designed to prolong battery life/improve speed/provide stability.
Kernels are abundant for the NS, so I’ll be naming the most popular:
GLaDOS
ICUP Kernel Edition
*Matr1x*
SG-NS-ICS - 14-01-2012 - 11UV|Voodoo|BFQ|BIGMEM|BLN|BLD|BLX|TW|Lazy|3.0.15
Netarchy Nexus
NS+4G Trinity (E)UV and OC CM9 + m(any) roms
Click to expand...
Click to collapse
Many users ask around about which could be the best kernel. For this, xda member bedalus decided to set up a thread where he benchmarked ICS kernels (accurately enough). This should give you an idea where to start from.
Also, there are terms which appear frequently in the features list of kernels, so here’s a very basic list of the most common terms found in our kernel threads:
Code:
[B]BFS[/B]
[quote]A Brain F**ked Scheduler will perform better on CPU intensive
process, which usually cause them to get higher benchmark scores.
However because it only dedicates minimal CPU to background
processes you may experience lag when switching quickly between
different tasks. [/quote]
[B]BLD[/B]
[quote]Backlight Dimmer provides an option for the lights of the
touchkeys to be turned off after a certain period. This can be
tweaked from NStools. [/quote]
[B]BLN[/B]
[quote]Backlight Notification is a mod developed by neldar,
which converts the touchkey backlights into a notification led. [/quote]
[B]BLX[/B]
[quote]Battery Life eXtender, from Ezekeel, manages the maximum
percentage to which the battery is being charged. By default,
the Nexus S is charged to about 95% capacity. [/quote]
[B]CFS[/B]
[quote]A Completely Fair Scheduler is more suited for multitasking.
You may notice performance issues when using CPU heavy
activities like HD games because it is trying to keep the other
processes in the background equal to the one that is hogging the
CPU. It should also be noted that, as designed, this type of
kernel should handle going from listening to music to sending a
text to surfing the web with minimal lag. [/quote]
[B]Deep IDLE[/B]
[quote]Another mod by Ezekeel, which allows the phone to
enter a “deep idle” state while performing tasks when the screen is
off. For example, listening to music with the screen off and
Deep Idle turned on, you should get better battery life than
without Deep Idle. [/quote]
[B]Governors [/B]
[quote]There is a much to be said here, and this would stretch
this dictionary too much. I recommend reading [url=https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt]THIS[/url], a very good explanation of
governors—from CyanogenMod. [/quote]
[B]OC (Overclock)[/B]
[quote]An overclock is usually one of the first things users
figure out after gaining root access on a new phone. If you
want to push your smartphone's CPU to run more clock cycles,
you have to know that extra power isn't coming from nowhere.
However, it is generally considered good practice, but it
depends on your handset. Some phones may be able to support
overclocking to 1.4 GHz, while others may never get past
1.2 GHz. Just proceed with caution. [/quote]
[B]Touch Wake[/B]
[quote]Yes, yes, Ezekeel again. This mod allows the user to
wake the device after a set amount of time, just by touching
the screen or the capacitive buttons. The time after which the
screen no longer responds to a touch is set with NStools. [/quote]
[B]UV (Undervolt)[/B]
[quote]This refers to lowering the voltage to conserve power while
still achieving the same performance, assuming your settings
remain stable. Both SetCPU and NStools allow the user to change
voltages. Like overclocking, this is also a trial and error process,
because each phone is different. The benefits are low energy
consumption and less thermal output. [/quote]
Tools & Mods​
So you have a rooted phone. Maybe even a custom Kernel or ROM, whatever works for you. But you still want to be a tad different from the other guys using the same configuration as yours. So here's a small selection of mods and apps developed by members of the community, enough to get you started. Feel free to experiment, and remember: read before flashing, search before asking and you should be alright!
Mods for AOSP+ Rom
[BOOTANIMATION] Plain, Simple & Colorful + color variants
Nova Launcher
Flavours for stock OTA ICS 4.0.3
Search key to ICS recent apps [add CM9 version]
[NS][NS4G]FaceLock for ICS 4.0.3
Enable on-screen buttons in ICS roms
Click to expand...
Click to collapse
NOTES:
I am hoping this little survival guide is useful FOR BEGINNERS in understanding the basic terminology used here in the Nexus S sections. As the title suggests, it was made with beginners in mind, so I don’t want posts of so called “experts” saying how they already knew this.
IMPORTANT: I do NOT guarantee the explanations written here are completely accurate or complete, FOR NOW. I will keep working on this, correcting mistakes as I continue to read.
If you find something that you think is not correct, or consider something must be added, please post here, together with a link to a credible source.
All of this came from sources off the internet, so please bear with me. Also, sorry for any typing mistakes. If you see any, please be sure to signal them
If I have helped you in any way, or if you appreciate the work invested in this (now and for the future), press the THANKS button.
Thank you! (Hoping to see this stick) And many thanks to all the great devs working on ROMs and Kernels for us. Keep up the great work!
W O R K - I N - P R O G R E S S
(I will be sure to notify you when I believe this is complete)​
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
ljordan2 said:
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thank you! I'm just worried it is a little bit long... but in the next couple of days I will be making it more reader friendly
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
nice thread! thanks
Hey great post, i still haven't rooted my nexus s but you just made me flash a kernal. I was tkinking about it but never too serious.
thanks!
Love it!!! Cleared so much up (you recieved my first Thanks button click!)
Just wanted to clarify something about the Kernel. My Rom is stock 2.3.6 that was received OTA when I unboxed the phone (Nexus S GSM i9020A, I'm in Canada). The bootloader is unlocked, phone rooted with CWM recovery via one click (QBKing's Video). Am I able to flash a custom Kernel to a stock Rom? Reading the above seems to lean towards the "yes", but wanted to make sure first.
Also, do not use the one click method on the Nexus S GSM if you want to easily return to stock. The one click stock only supports the 4G, which is extremely silly and inconvenient IMO. I'm currently still trying to figure out how to return to stock, incase something does happen and the phone needs warranty work. Let's just say, I'm not making much progress and this is extremely uncomfortable ATM..
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Thanks so much for taking the time to do this
Sent from my Nexus S using XDA App
Harbb said:
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Click to expand...
Click to collapse
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
very useful for us newbie, thanks for sharing
heX79 said:
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
Click to expand...
Click to collapse
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
great post OP
Nice thread! Great Work ,Thanks
Hey thanks! Happy to see good feedback on this.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
Great beginners guide, and thanks for the link!
For kernel benchmarks and more, see here: http://goo.gl/mpeHI
Thanks very much! I will give it a try shortly, just to confirm if I recieve any issues. I've also installed the recommended CWM version for my model, not sure if it makes a difference, but I flashed 5.0.2.0 anyway as the version I was getting an error with had a higher build number.
Right now I'm enjoying AndroidME 1.2.3 with Speedy 6 kernel and have no complaints so far! (Kernel updated this morning from Speedy 5)
I will report back with any issues once I have some time to do a Nandroid backup and test the stock Rom.
Thanks for your help!
It's nice to know there's a way to revert back to stock, should anything need servicing! I've also started reading up on Odin
flodb113 said:
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
Click to expand...
Click to collapse
You're welcome! Looking forward to an update with your stock flashing situation. I also used ClockworkMod 5.0.2.0 a long time. I'm now on 5.0.2.3 only for the better menu layout.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
just one question...
can i install more than one kernel at a time...
for eg.like one i installed for battery usage and othr for sound..
can i do tht

About GPU Throttling

Hello everyone,
My question is about Throttling. We know in stock Nexus 4 kernel, throttling starts when battery temperature hits 37C. CPU throttling is fine, but problem comes when it starts throttling GPU. Is there a way we can stop it from throttling GPU? Can we edit the stock thermald.conf file? Is it safe to edit it and remove GPU option from it and make it throttle when the battery temperature reaches 40C?
TheRebel said:
Hello everyone,
My question is about Throttling. We know in stock Nexus 4 kernel, throttling starts when battery temperature hits 37C. CPU throttling is fine, but problem comes when it starts throttling GPU. Is there a way we can stop it from throttling GPU? Can we edit the stock thermald.conf file? Is it safe to edit it and remove GPU option from it and make it throttle when the battery temperature reaches 40C?
Click to expand...
Click to collapse
should work and should be safe. why dont you try it?
vollmilch said:
should work and should be safe. why dont you try it?
Click to expand...
Click to collapse
Thank bro
Lol, I thought I might hard brick my phone. Do you know anyone else tried it?
I know we can get rid of this gpu throttling (which happens so early) by using some custom kernel, but i've tried many custom kernels, but they don't seem to have same smoothness as stock kernel.
TheRebel said:
Thank bro
Lol, I thought I might hard brick my phone. Do you know anyone else tried it?
I know we can get rid of this gpu throttling (which happens so early) by using some custom kernel, but i've tried many custom kernels, but they don't seem to have same smoothness as stock kernel.
Click to expand...
Click to collapse
trinity kernel has battery temp throttle disable, and its extremely smooth.
simms22 said:
trinity kernel has battery temp throttle disable, and its extremely smooth.
Click to expand...
Click to collapse
thanks!!!
does trinity kernel throttles on CPU temperature? thermal throttling?
And do you have any idea about my question in first post? Is it safe to edit the stock kernel's thermald.conf file?
TheRebel said:
thanks!!!
does trinity kernel throttles on CPU temperature? thermal throttling?
And do you have any idea about my question in first post? Is it safe the stock kernel's thermald.conf file?
Click to expand...
Click to collapse
it has its cpu throttle temp raised. but there is a simple script you can run in a terminal emulator app or go to tbe location with a root file explorer and exit manually. in a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
i always run with thermal throttle disabled. tbe cpu safty temp is still intact, if you hit it, youll automatically shut down to cool off. the only way that you will hit it is if you try to hit it.
about editing the thermald.conf file.. is it safe modding your phone in the first place?
i believe that faux's kernel uses a modded thermald file (cpu throttle temp raised, gpu throttle disabled). i used to keep a copy of the file on my dropbox and i would post it here for you but I deleted it some time ago. why dont you ask someone in his thread to share it with you so you can just replace yours.
but keep a backup of your original just in case
simms22 said:
it has its cpu throttle temp raised. but there is a simple script you can run in a terminal emulator app or go to tbe location with a root file explorer and exit manually. in a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
i always run with thermal throttle disabled. tbe cpu safty temp is still intact, if you hit it, youll automatically shut down to cool off. the only way that you will hit it is if you try to hit it.
about editing the thermald.conf file.. is it safe modding your phone in the first place?
Click to expand...
Click to collapse
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
vollmilch said:
i believe that faux's kernel uses a modded thermald file (cpu throttle temp raised, gpu throttle disabled). i used to keep a copy of the file on my dropbox and i would post it here for you but I deleted it some time ago. why dont you ask someone in his thread to share it with you so you can just replace yours.
but keep a backup of your original just in case
Click to expand...
Click to collapse
Thanks for the reply. I've faux123 thermald.conf file. But I dont' know whether I should replace stock thermald.conf with faux thermald.conf. Because faux has used Sampling 1500 (while in stock the sampling value is 5000). I don't know about sampling though , just the values were different so i didn't replace the file, thought it might hard brick the phone
TheRebel said:
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
Click to expand...
Click to collapse
go to http://www.derkernel.com/mako.php , click on "experimental" and download the first one (TF133).
if your rom doesnt use a modded ramdisk, just reboot into recovery, flash it, wipe cache and dalvik, reboot
TheRebel said:
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
Click to expand...
Click to collapse
theres only one link for downloads, tf133 is the latest http://derkernel.com/jb-mako.php
simms22 said:
theres only one link for downloads, tf133 is the latest http://derkernel.com/jb-mako.php
Click to expand...
Click to collapse
is there any difference in throttling based on battery temp and CPU temp? which one exactly are modifying using the echo command?
CPU temp threshold can be raised easily in faux app, so what about battery temp threshold? can we change it?

[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

Categories

Resources