yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] schen:
If 9800 is what you get using Antutu latest benchmark version then clearly there is something wrong. I can easily get 14000++ score with kernel 3.5, 4.2, 4.3 which is 1800 version. 13500++ score with kernel v3.6, 4.0 which is 1600mhz version.

I dont use any kernel apps for tweakimg. All is done with init.d script. The setting I use for 4.3 is as follow

# GPU Frequency

echo "160 267 330 400 440" > /sys/class/misc/gpu_clock_control/gpu_control

# GPU Voltage

echo "950000 1000000 1050000 1100000 1150000" > /sys/class/misc/gpu_voltage_control/gpu_control

# GPU Up Down Threshold

echo "65% 45% 70% 40% 75% 40% 80% 50%" > /sys/class/misc/gpu_clock_control/gpu_control

# GPU staycount

echo "1 1 1 1 1" > /sys/class/misc/gpu_clock_control/gpu_staycount

# CPU Frequency

echo "400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "1800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# Governor Setting

echo "pegasusq" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "800000" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_for_responsiveness

# CPU Voltage

echo "1325 1325 1300 1275 1250 1225 1175 1125 1075 1025 1000 975 950 925 900 900 875 875 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

# SD Cache

echo 1024 > /sys/devices/virtual/bdi/179:0/read_ahead_kb

echo 1669 > /sys/devices/virtual/bdi/179:24/read_ahead_kb

echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb

echo 1669 > /sys/block/mmcblk1/queue/read_ahead_kb

Result for Antutu is 14165. Gpu very smooth and responsive. I have to warn anybody if you want to try my setting use kernel setting apps or scripter first to see your device response to the 440mhz gpu, gpu voltage, cpu voltage. This is to make sure if your device cannot take the extreme setting you can just reboot to get back to skyhigh default.

---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------

I have no random reboot with or whithout my personal setting.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
[MENTION=647076]Shen[/MENTION] , what a "gas guzzler" of a settings :D

Your device can't handle GPU 520 MHz @ 1200 mV ? I know (and stated) that all hardware is different, but mine was rock stable on long intensive GPU testing. You might gain a few more % :cool: lol
[Galaxy Tab 7.7 Android Development] schen:
Dont know as I have not touch 520mhz. I tried the 440mhz with riptide gp2 with all graphics setting max out and it runs very smooth without a glitch and that is all I need. Dont know may be I will try later.
[Galaxy Tab 7.7 Android Development] ninekaw9:
I also have this issue.
[Galaxy Tab 7.7 Android Development] GalaxyGS:
Nice kernel for performance. My benchmark score :

-Quadrant : 5096

-Antutu 4 : 13159

But little bit battery eater than 3.9.0
[Galaxy Tab 7.7 Android Development] ninekaw9:
I also have this problem, my tab 7.7 reboot after going sleep.
[Galaxy Tab 7.7 Android Development] partola1:
Same problem for me. Rebooting, overheating and battery draining as crazy. Roll out to 4.2, it seems ok.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Check your ROM wake locks and remove any extra user installed "performance" type tweaks and scripts etc, then 're-flash kernel.

No default settings have been adjusted that would affect any heating. Default voltages and max freq are unchanged, unless user tweaked.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for confirming. I'll push an update soon (edit: today). Will increase the screen off "idle" freq back to 160 MHz & possibly stock voltage. If this fixes the problem, I can reduce just voltage later on.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v4.4.0 update

>> v4.4.0 UPDATE <<

NOT PESONALLY TESTED

CHANGES

ON P6800 PARTITION !!

** FOR P6800 partitioned device running JB 4.1.2 DXMD3 ROM !! **

1. Read warnings in Post #3 before flashing. I am not responsible, you are

2. Clear your CPU Control app defaults first. device settings/applications/all/"your control app"/clear data

3. You will need a CPU control app to adjust the CPU freq from the safe startup values (OC / UV / UC)

4. Recommend 200-1400 -or- 200-1600 MHz

5. Recommended governors etc = Read Post #3

** REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

CHANGE-LOG v4.3.0 > v4.4.0

** Source changes as per gitHub

* Random reboot when screen off (for some users) - FIXED ??

Increase GPU idle (screen off) from 108 MHz / 900 mV > stock level 160 MHz / 1000 mV

Will look at a slight UV if fixes reported issue

++ PLEASE REPORT BACK ON THIS !! ++​

* Set L2 bus (memory) speed from 133 > 160 MHz via config file

- Might look at slight UV later on

- Default MHz now:

L0 = 400

L1 = 267

L2 = 160 MHz / 1000 mV (stock = 133 MHz / 950 mV)​

* lowmemorykiller: change default debug_level to 1 (currently overde by intramfs tweaks set to 0 )

INSTALLATION

** REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

1. NANDROID (just in case)

2. Flash SkyHigh P6810 JB 4.1.2 ROM or bodivas P6810 JB 4.1.2 ROM

3. Remove any previous CPU control settings from starting at boot

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

4. THIS WILL PROBABLY "BREAK" currently installed V6SuperCharger scripts ! (test kernel first, and then re-install scripts)

SUGGESTED CPU CONTROL APP : Trickster Mod app

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

CURRENT BUGS :

* Random screen tint (Read Post #3)

ISSUES?

* READ POST #1, #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] schen:
Iam quite satisfied with with 4.2 actually but want to know if increase frequency of memory bus has any significant effect on day to day use ang playing games. Applied my setting immediately after flashing 4.30. I have no bootlopp.

4.2 battery life with my setting actually quite good. I have -50mv to -75mv for cpu and -50 to -100mv for the gpu over standart default frequency. So standby time actually inprove a lot. Active time battery drainage actually depends on how much you stress out your gpu and cpu usage.

BTW I tried 520mhz with 1150mv briefly and it is no go. 1200mv might do the job maybe. But I wil stay at 440mhz for now.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
No will not affect games, just general usage.

In most cases, graphic intensive games running at 400 MHz (or whatever you set), will have bus scaled to L0 (400 MHz). As per my commits and change-log, this is stock and SkyHigh kernel default level

You can monitor with cool tool app :

/sys/devices/system/cpu/cpufreq/busfreq_current_level

output either 0, 1, or 2​

Just edited the change-log to be clearer........

.
[Galaxy Tab 7.7 Android Development] ninekaw9:
Thanks for the update 4.4 but it still doesn't fix the reboot problem while in sleep mode. I've also deleted all init.d scripts. By the way, I am using eRobot v1 (Tablet mode). No multiwindow mod, multiwindow mod take too much RAM for me (600/800 MB after boot in even safemode) and cause the device to lag like hell. Without multiwindowmod ram usage is around 400-450 MB.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Your not using any other performance type tweaks, apps, screen off profiles, our any other change to SkyHigh default etc?

I will try implement a patch to disable vpll mode during sleep, so device falls back to mpll with stock voltage table. I'll take a look later.

Yes, the mod does use more RAM, but my kernel LMK tweaking helps with that, keeping enough free memory. My device doesn't lag, especially with this kernel. Maybe you need to fstrim your partitions and delete some stuff from your internal sdcard.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
REBOOT BUG FIX (for some)

Got a "work-around" and patch source to enable / disable vpll-mpll mode via sysfs init.d script.

Tested OK, will update tomorrow with v4.5.0_TEST those with reboot issues for test and FEEDBACK.

vpll :

SkyHigh default = 5-step (108-160-267-330-400)

min freq =54

max freq = 520

mpll :

4-step = (100-160-267-xxx-400)

min freq = 50

max freq = 400

xxx = invalid (ignored freq)

Any mpll scripts still must have 5-step, otherwise the script won't work.

If you have an app that can execute the widget when screen off and on (profile), you could have at least the best of both worlds. Does anyone know of such an app? I don't know if script manager (pro) can do it?

I'm not sure which I'll eventually make default yet, I personally use vpll !

Edit: I might try and make it enabled / disabled by same way lagfix fstrim is done. For more user compatibility, probably make mpll the default. Advanced users with capable device can use vpll.

Edit 2: All the above will only happen if it fixes devices affected with screen off reboot issue (under SkyHigh default settings)
[Galaxy Tab 7.7 Android Development] schen:
Someone asking my script file through pm. So here it is. Please try it with script manager first before applying it through init.d. Thanks

BTW I was back to 4.3. It gave me better benchmark (read feeling). My benchmark is my feeling.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v4.4.1_test build

v4.4.1_test build

THIS IS FOR THOSE USERS WHO

REPORTED SCREEN OFF REBOOT

WITH SkyHigh DEFAULT SETTINGS

REQUIREMENTS

1. Have a screen off reboot issue with v4.3.0 or v4.4.0 (under SkyHigh kernel default values)

2. No kernel tweaking via installed init.d scripts, "performance" type apps or mods etc (ie. kernel performing under default values)

3. Willing to provide feedback under kernel default conditions

4. Custom recovery installed to flash files

FLASH INSTRUCTIONS

1. Meet above requirements

2. Flash in custom recovery:

a) v4.1.1_test.zip

b) 01mpll_enable.zip (installs script to init.d folder to change from vpll > mpll mode on boot)

3. Reboot & SETTLE

4. Screen off

5. What happens next - reboot or stable?

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
There have been 6 downloads of the test kernel & only 5 of the script (someone forgot ! )

So how about some feedback please...

Using the requirements & given instructions, has it fixed your screen off reboot issue?
[Galaxy Tab 7.7 Android Development] partola1:
Hi, UITA!

After applying patch on 4.4.1_test kernel restarting steel here. Sad...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Can you please confirm the script had installed to /system/etc/init.d folder. Thanks
[Galaxy Tab 7.7 Android Development] partola1:
Yes, script is installed in this folder.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
A shame it doesn't fix the problem. I'm not sure of the way forward or how to "fix" it. I really like the extra GPU OC and freq options and 5-step..... appears some devices just don't like it (just with I9100 siyah kernel).

I could compile two separate kernels, but I'd need to make another source branch in gitHub so not to contaminate builds and build 3 or 4 kernels instead of 2. A lot of extra work and time I don't have.
[Galaxy Tab 7.7 Android Development] schen:
Probably the answer to the reboot problem is just to set gpu frequency to start from 160mhz and gpu voltage from 950mv. No?

-100mv at 160 and -150mv at 267mhz from stock kernel might be too much for some device.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Nothing (shouldn't be anything) to do with it.

mpll freq and voltages are same as v4.2.0 and much earlier.

Reported screen off reboot for v4.3.0 and v4.4.0....... the difference being 5-step GPU.

The test kernel + script is essentially the same as earlier v4.2.0, but 5-step using only 4 (330 MHz ignored)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v4.4.2_test build

v4.4.2_test build

THIS IS FOR THOSE USERS WHO

REPORTED SCREEN OFF REBOOT

WITH SkyHigh DEFAULT SETTINGS

REQUIREMENTS

1. Screen off reboot issue with v4.3.0 or v4.4.0 (under SkyHigh kernel default values)

2. No kernel tweaking via installed init.d scripts, "performance" type apps or mods etc (ie. kernel performing under default values)

3. Willing to provide feedback under kernel default conditions

4. Custom recovery installed to flash files

FLASH INSTRUCTIONS

1. Meet above requirements

2. Flash in custom recovery: v4.1.2_test.zip

3. Reboot & SETTLE

4. Screen off

5. What happens next - reboot or stable?

CHANGE-LOG

v4.4.0 > v4.4.2_test

* revert to 4-step GPU control

* default GPU freq = 108-160-267-400 MHz

* default GPU volt = 900-900-950-1050 mV

* still retain GPU vpll mode (optional frequencies 54 >......> 520 MHz)

++ FINGERS CROSSED ++

.
[Galaxy Tab 7.7 Android Development] partola1:
Again Reboot...

May be a problem have another reason than videosettings?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Although no complaints, please retest versions 4.2.0 or earlier.
[Galaxy Tab 7.7 Android Development] partola1:
Using 4.2.0 now. Working fine.
[Galaxy Tab 7.7 Android Development] stenny:
Test-1 solve my reboot issue, great job. I'm using Note 8 rom with My repartitioned Tab7.7.
[Galaxy Tab 7.7 Android Development] schen:
I think this is what causing the reboot. Wakeup from sleep the gpu shoot pass any limit we set and goes straight to the highest. My setting has 440mhz as the highest setting. My cooltool reading shows 520mhz. No reboot on my tab but a temporary freeze about 5 seconds and after this gpu stays at 520mhz. I can feel the temp getting hotter now and I will reboot.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
The problem is that users say when screen is off, not at wake-up.

I doubt your tab can handle 520 MHz? Not stable? Try running "ice storm extreme" with 3D Mark app.
[Galaxy Tab 7.7 Android Development] schen:
Wake up is after sleep. This mean that during sleep the gpu jump to 520. I can only see it after waking it up. My tab can handle 520 that is why I am still able to wake it up. Those who cannot will get reboot during sleep.

In fact I am still running my gpu at 520mhz NOW. Constant 520mhz. Cannot scale down anymore.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
A little confusing. vWorks for some and not others.....

vpll 5-step = reboot (v4.4.0)

mpll 5-step = reboot (v4.3.0 or v4.4.1_test + script)

vpll 4-step = fix & reboot? (v4.4.2_test)

mpll 4-step = ok (v4.2.0)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
But that's not what users have reported - reboot happens when screen is OFF. GPU obviously need to scale once device requires it to ie. Screen on, unlock, home etc

Nothing to do with freq, as 400MHz remains max, same as v4.2.0

Stuck freq, Don't believe a kernel issue, get rid of your script and reboot.....
[Galaxy Tab 7.7 Android Development] schen:
It turns out that I was testing the gpu voltage with kernel 4.4 when mine happen. Instead of my usual seeting that I posted I lowered it down -50mv for all frequency which is

900mv 950mv 1000mv 1050mv 1100mv.

160mhz 267mhz 330mhz 400mhz 440mhz

That is what causing my gpu stuck at 520mhz during sleep.

I am now back at my own setting (posted earlier). It should work fine as before.

You should increase your default gpu by 50mv. I think. Your default gpu voltage at 160mhz is -100mv from samsung stock. 267mhz is -150mv. Maybe too much for some device.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
As I posted above, nothing to do with mpll freq or voltages as all are same as v4.2.0 .....

What I am going to do is leave it (for now). I have tried a logical sequence, reported results conflict, and I don't have time (or maybe knowledge to sort through logs) because I like the 5-step vpll GPU. I won't be supporting 2 kernels and want to keep the changes I've made so far.

So unfortunately, users that have screen off reboot, I will direct them to install v4.2.0 for stabilty.
[Galaxy Tab 7.7 Android Development] schen:
You draw your own conclusion. I was telling you that this setting

900mv 950mv 1000mv 1050mv 1100mv -> gpu stuck at the higest frequency during sleep. If I leave it a bit longer maybe it will get a reboot as it is getting hotter and hotter.

950mv 1000mv 1050mv 1100mv 1150mv -> working fine on kernel 4.3 and 4.4. Have use this setting for days now. Everything on my tab is the same except the gpu voltage I change.

NB: I wasnt use your test kernel. I use 4.30 and 4.40
[Galaxy Tab 7.7 Android Development] UpInTheAir:
NOPE : you are wrong. GPU scales when user wakes device, think about it..... You turn on screen, it wakes, and scales uppppppp, sometimes rapidly to accomodate demand. It does not sleep at max.

As I said, ALL test mpll voltages and freq are the SAME, so no different to v4.2.0.

My device is fine, nice and cool at idle and general use. Any stuck freq is GUI
[Galaxy Tab 7.7 Android Development] schen:
My device is fine too, nice and cool, fast and responsive WITH gpu voltage +50mv from your default. As soon I use YOUR DEFAULT voltage my tab start acting WEIRD.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Should I just ignore this post? WEIRD is NOT constructive or helpful.

Must be GUI, otherwise you would have reported it earlier and given proper feedback for help ????????????

Please refer to the ISSUES section........

You didn't bother to read & DIGEST my previous posts did you. I don't care anyway.

AGAIN,....... users post OK with v4.2.0 which has SAME mpll frequencies and voltages as test kernels :rolleyes: SO it

cannot

be this !

Anyway, development is suspended. I have other things I want to do rather than debate GUI :cyclops:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Finally managed to UL v4.6.0

Please read ALL Posts #1-3, Installation Instructions & Change-log before flashing.

If you have "issues" with SkyHigh default values, please ensure you have re-read at least BUGS & ISSUES section first. Your reply may already be there ;)

If you have a stable device and wish to try tweak even further, using a init.d script will be required for most variables. If you can't manage a script yourself, you shouldn't be tweaking anyway. By reading Post #3, you will find EXAMPLES of script code, but this thread is not concerned with script and any user personal settings. You can PM each other or share out of thread thanks.

Enjoy :highfive:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
BUG

Reported exFAT not working with v4.6.0

Think I've found the problem. Will take a look
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v4.6.1 update

>> v4.6.1 UPDATE <<

NOT PESONALLY TESTED

CHANGES

ON P6800 PARTITION !!

** FOR P6800 partitioned device running JB 4.1.2 DXMD3 ROM !! **

CHANGE-LOG v4.6.0 > v4.6.1

** Source changes as per gitHub

* Fix exFAT (forgot to enable in config for P6800 version)

INSTALLATION

** DO NOT USE ANY 3RD PARTY TWEAKS OR “PERFORMANCE” TYPE APPS & REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

1. NANDROID (just in case)

2. Have installed any P6800 JB 4.1.2 ROM based from official Samsung sources

3. Remove any previous CPU control settings from starting at boot, remove any 3rd party tweaks etc

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

5. If requested by Recovery to install SU, DO NOT. Instead - Let the kernel do it on boot

CURRENT BUGS :

* Random screen tint (Read Post #3)

ISSUES?

* READ POST #1, #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
RESET CUSTOM FLASH COUNTER

"How To" in Post #3
[Galaxy Tab 7.7 Android Development] frogeed79:
random start

Hi...its just me or anybody else? V4.30, v4.40, v4.60 make my tab random restart...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
This has been already discussed over the last few pages.......

You can also try switching to GPU mpll mode with a init.d script. Example on Post#3.

Other than that, please read the BUGS and ISSUES section.

It appears the implementation of 5-step GPU isn't compatible with some devices and also 5-step + vpll mode. For all subsequent releases, GPU freq step voltages remain the SAME (unchanged) from stable version 4.2.0.

I might try revert to 4-step GPU for test again (at some point), but I like 5-step for now.

+ I definitely won't be getting rid of GPU vpll mode +

Edit: The unfortunate thing is that any release after v4.2.0 may be incompatible with your device :(
[Galaxy Tab 7.7 Android Development] frogeed79:
Thanks....i really like your kernel
[Galaxy Tab 7.7 Android Development] deani77:
Been using almost every version of UITA kernel. Never faced random reboot so far... Using it with stock 4.1.2 and UITA custom ROM.
[Galaxy Tab 7.7 Android Development] WildmanJoe:
Yes, I've experienced it as well. On the 4.6.1 version as well. Reverted back to stock / 4.2 and things are ok.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I'll be off the radar for a bit.

Trying to get an "experimental" version together & working. Let's see where things go.......
[Galaxy Tab 7.7 Android Development] Silver-7:
Thanks , I'm using 4.6.1 no random reboots so far.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Development is suspended again.

For the next couple months, real life priorities are in force.

Shame, was making good headway on the experimental build, but not yet at a stage for an alpha release. Needs heaps of work.

Cheers,

UITA
[Galaxy Tab 7.7 Android Development] ngoonee:
Much appreciation for your stellar work on this outdated (but still awesome) device man
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I have to go away sometime mid-week for a couple months.

I am working hard on the experimental alpha release.

I will try my absolute best to have it released as alpha before I go. Many things working, some not and some need removing....... I will not have time to refine anything.

I will not give any hints about what's in it or ETA. Users will be pleasantly surprised. :)

Edit: Maybe not too, having issues with Wi-Fi connecting. Reverting all my work to try find out why......

Edit 2: don't know why Wi-Fi issues...... and too much work to do. The more I dig into the code, the more work I see needs to be done to port many options to our kernel. Will have to leave it for now. I can't / won't release anything with a known Wi-Fi issue.

Edit 3: Wi-Fi issues are fixed ! Just a few things to try and fix before considering a first v4.7.0_EXPERIMENTAL_alpha release. Running out of time though......
[Galaxy Tab 7.7 Android Development] lomniom:
Good job mate!
[Galaxy Tab 7.7 Android Development] Silver-7:
4.6.1 working good for me

Till I installed trickstermod to enable zram, and had freezing (forced to reset) for 3 times. After uninstalling trickstermod everything is ok again. I don't know how's that related tho.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for letting me know.

I'll try find time to retest zRAM later on, but dedicating what time I have for the experimental release.

I have tweaked zRAM recently, so might have something to do with that. But as I said, I'll try and test if I have the time.
[Galaxy Tab 7.7 Android Development] deani77:
As for me I have no problem using Trickster to activate ZRAM... Have no reboot problem. Was on latest kernel using Wheatley/SIO, 200/1400mhz
[Galaxy Tab 7.7 Android Development] rezadentevil:
i used 4.6.1 and set CPU

my tabs speed was too low and i had so many cashes .even its crashed and nothing has work. even the power botton. i had to push power for 4 sec to restart.

and now i switch to stock kernel ant i think its better no crashes and...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I have no idea what you're on about.....

SetCPU, zRAM, your SetCPU profile ??
[Galaxy Tab 7.7 Android Development] sas_sas:
I flashed with the last 4.6.1 and I did not have any problem at all.

As a matter of fact, I have been with Skyhigh kernels since the beginning.. No problem at all..

I am with SkyHigh Rom v3.5 too.

Ths UITA..
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Hey, please prepare for a beta release of my "experimental" version later on today ! :)

IMPORTANT : DELETE ANY CPU CONTROL APPS AND REMOVE ANY SCRIPTS BEFORE FLASH !