[Galaxy Tab 7.7 Android Development] UpInTheAir:
FAQ & HELP

FAQ & HELP

MY RECOMMENDATIONS

* Governor = pegasusq, lulzactiveq, or ZZMoove

* IMO = Performance → → Battery

1. on-demand

2. pegasusq (snappy, but easier on battery than on-demand)

3. lulzactiveq

4. ZZMoove​

* Scheduler = SIO

* CPU freq = 200-1400/1600 MHz

* CPU vdd levels = SkyHigh "defaults"

* Enable zRAM for better mulitasking

* CPU Control app = ExTWeaks

Don't forget to use only one Control app at a time. They will conflict !

ISSUES?

1 Remove any kernel related init.d tweaks, 3rd party performance type apps etc

2 Wipe your CPU control app(s) data (menu > settings > applications > "your control app(s)" > clear data/cache)

3 Use only ONE CPU control app ! USE EXTweaks

4 Open SuperSU app > settings > full unroot (or unroot from with EXTweaks options)

5 Boot into recovery and wipe cache & dalvik cache

6 Re-flash SkyHigh Kernel

7 If requested by recovery - DO NOT install root (let the kernel do it)

9 Reboot

8 If still issue such as bootloop etc, try using MPLL mode for GPU, and or increase GPU voltages +50 mV

9 Try a kernel "legacy" versions

10 Back to stock for you :(

RANDOM SCREEN TINT AFTER CHANGING GOVERNOR

* Turn screen OFF-ON

* Use only SkyHigh defaults values

* Don't use a CPU control app to change kernel settings - Use init.d script instead

* OR IF IT BOTHERS YOU,...... DON'T USE THE KERNEL

zRAM

Info here : (INFO)What is zram and how does it work???

LOGS

* You can find various ExTweaks logs in the /data folder:

/data/.siyah

/data/extSdCard_fix.log

/data/fsrepair.log

/data/fstrim_lagfix.log

/data/Ran_FixEmissions.log

/data/sqlite.log

/data/zipalign.db

/data/zipalign.log

/data/crontab

PREVENT/REDUCE SCREEN-OFF FLICKER FOR CRT-OFF ANIMATION ENABLED ROMs

* Set fbearlysuspend msleep between 100 and 500 ms

* Set to 0 if you haven't any CRT-off animation mod

DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS

* [Christopher83]

WHAT IS A CUSTOM KERNEL

* First of all, watch this : Android Basics 101: Understanding Kernels – XDA Developer TV

* Is usually' modified and complied from source.

* My very first successfully compiled kernel just included the "SkyHigh" name. I suppose you could call that a modified "stock" kernel. On the other hand, you could also argue that any firmware modified from either official or built from sources could be called "custom". :)

HAVE THE STOCK KERNELS ATTACHED BEEN MODIFIED

* If you are referring to the stock MD3 kernels in Post #2, NO

* I just extracted the zImage from official firmware and repackaged for flashing via custom recovery or Odin. There are no changes made to the zImage. I have no plans to modify these.

ENTROPY

* MAX pool sixe 4096

* It's not instant, just use your device and it will grow.

* No need for entropy generator apps that consume battery (use extra CPU cycles)

WHAT ARE GOVERNORS / SCHEDULERS ETC

* Excellent source of info by droidphile :

[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs

FSTRIM LAGFIX

* fstrim is more of a maintenance binary. Android 4.2.2 and below are more prone to lag over time and prevalent as your internal storage is used up.

* Trims system, preload, data & cache partitions

* fstrim binary set to run by init.d 90lagfix script after boot to reduce impact on boot time

* A manual reboot once a week is suggested. Those users who have ample internal storage and or recently formatted their partitions via ROM flash or Nandroid restore may see little difference for now.

* More info : Google yourself or Nexus Storage Performance Over Time & TRIM 20130829

CUSTOM BOOT ANIMATION SUPPORT

1. copy bootanimation.zip to /system/media/ folder (mount folder r/w to paste)

2. ensure set permissions rw-rw-rw-

3. reboot

NOTE :

* For any further help or instructions for bootanimation, please open your own forum Q&A thread or post in a relevant bootanimation thread. There are many already built and can be found by searching.

* The size we need for our tab is 800x1280 or 1280x800 (depending on portrait or landscape)

CUSTOM BOOT SOUND SUPPORT

* Place custom boot sound PowerOn.ogg in /system/media

* To mute, create an empty file named mute in /system/media

* To unmute, create an empty file named unmute in /system/media

* To restore original boot sound, create an empty file named ori_sound in /system/media

* Reboot device after each process

NOTE :

* when creating a custom boot sound, make sure you use a capital "P" and "O" in PowerOn.ogg

* I will not provide a tutorial for creating boot sounds, you can Google yourself ;)

BENCH-MARKING

Freeze or Re-Boot

1 Try increase CPU 1600 Mhz voltage by +25 mV or +50 mV. I would not recommend any more than that !

2 Lower CPU OC back to stock max 1400 MHz setting

3 To find out which frequency cause the freeze :

a) If you have UV the CPU and the device freeze, obviously you need to increase the voltage to a particular frequency step(s)

b) Do a stress test with SetCPU (or other app) and lock your max frequency for each step (DO NOT SET ON BOOT WHILST TESTING)

4 Try a different governor

5 Use a different benchmark app/tool

AnTuTu Crashes?

* Try another benchmark app !

Low Bench-Marking Scores

* Consectutive tests as well as OC may heat the CPU high enough where thermal limiting occurs. Well here you go........... I observed my CPU regularly drop to 800 MHz after hitting a thermal limit during testing.

Here's the proof !

https://github.com/UpInTheAir/P6800_JB_SkyHigh_Kernel/blob/master/arch/arm/mach-exynos/mach-px.c

#ifdef CONFIG_EXYNOS4_SETUP_THERMAL
/* below temperature base on the celcius degree */
struct s5p_platform_tmu px_tmu_data __initdata = {
.ts = {
[COLOR="Red"].stop_1st_throttle = 61,
.start_1st_throttle = 64,[/COLOR]
.stop_2nd_throttle = 87,
.start_2nd_throttle = 103,
.start_tripping = 110,
.start_emergency = 120,
.stop_mem_throttle = 80,
.start_mem_throttle = 85,
},
.cpufreq = {
.limit_1st_throttle = [COLOR="Red"]800000[/COLOR], /* 800MHz in KHz order */
.limit_2nd_throttle = 200000, /* 200MHz in KHz order */

* With some undervolt and governor tuning, little OC impact will be felt on battery. Not everyone fixes their CPU to max with performance governor :rolleyes: so, providing your hardware can handle it, some OC should be OK for everyday use as the CPU only briefly scales to max freq with the 'right' governor.

* As you can see, this could be easily changed to allow (cheat) in benchmarks. This won't make much difference to everyday use, but IMO shouldn't be touched. My silicon may not handle it

RESET CUSTOM FLASH COUNTER

*There is a Samsung Galaxy Tab 7.7 flash counter introduced for P6800 JB 4.1.2 DXMD3, so any modified ROM, kernel or recovery flashed via PC Odin will increase the counter.

1. Have installed my P6810/P6800 SkyHigh kernel for JB 4.1.2 (patched for triangle away compatibility)

2. Install triangle away app v3.26

3. Reset counter

4. Reboot as requested

5. To check > open app again, or, power off and enter download mode

* Your custom ROM, kernel, recovery & root remain intact ;)

Anything else, IF I find the time ;)

.