yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] schen:
Yes I flash the new script with 10s delay...no go.

Then I change to 15s delay still no go

Then I change to 20s delay still no go.

It always revert back to 2048.

Your test scrip work fine though.

So far we know:

1. the init.d support is working(the S90test script successfully executed after boot).

2. The first set of script for changing read ahead cache is working(manually run)

3. The second set of script with delay is working(Manually run)

4. Changing the read ahead cache using the script at boot - Not Working

Please can someone test the read ahead cache script to see if the cache change after boot.
[Galaxy Tab 7.7 Android Development] theerachai:
not work for me too.

it change back to 2048.

my solution is use script manager and set it to run this script at boot then read ahead cache will be 1664.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Lack of info here......

What ROM was the first test, mod tweaks etc

What ROM was the latest test, mods tweaks etc
[Galaxy Tab 7.7 Android Development] schen:
Hi, UpInTheAir. Since there is a second person experience the same problem with changing read ahead cache from inid.d also will you please leave out tweaking the sd in the kerner level on your next revision of the kerner? And just do it from thr inid.d level so that we can manually set cache size to suit our own sd card. Thank you.

I have not seen anyone successfully change the cache through init.d despite init.d support working properly on ver 2.0.8
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Sorry, I don't see it as a "problem" as I prefer those settings. I will make it 1664 though.

For whatever reason, those that don't like the setting can use an app to mount the script or change cache.

This tweak is proven to work and enhance the kernel.

By making it an init.d tweak, then makes it a ROM tweak, and therefore nothing to do with the kernel.

If for whatever reason a user installs another ROM, the init.d tweak MAY be wiped, and the tweak unknowingly lost. The kernel would need to be re-flashed, but some inexperienced users wouldn't necessarily know that.

That's also why I'm reluctant.

If you haven't already.

1. Delete the tweak

2. Boot recovery

3. Flash stock kernel (don't reboot)

4. Flash v2.0.8 (don't reboot)

5. Flash tweak script

6. Reboot

Sorry, I don't have anymore time to devote to this "issue".
[Galaxy Tab 7.7 Android Development] schen:
If there is anyone successfully change the cache through init.d at boot then I will do the list you asked me to.

Sadly no one. So I dont see the need to flash and reflash. That is logical thinking.

Aside from not being able to change the raed ahead cache your kernel and DXMD3 run quite good provided IF I change the read ahead cache back to default 128 or the most 512. Obove that it is running a bit wild. Hick-up here and there. Freeze here and there. None of that happened with 128 and 512. This is purely for your feedback.

You see that there is no PARTICULAR BEST value when taking about read ahead cache....It has been discussed for years and still no one agree to one BEST value for the cache. People try one value, do the benchmark, try another one, do a benchmark, conclude one number that score the highest is the best for HIM. Others do the same and arrive at different number and it has been going on for years. There is a reason Samsung put 128 as default and I happen to agree with Samsung on this one. While I can use many apps to run at booth the change the value back...the init.d method seems to be a better way to do it. It is just too bad I cannot do it with your kernel. I am under the impression that we can always change that value through init.d.

I am sorry if the issue seems to bother you (judging from the tone of your last post...). I will not bother you no more. I was just hoping that there are more people trying out your script at boot successfully. Happy cooking and thank you for your time on this.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I would think that taking a little of your time to do what I asked wouldn't hurt, would it? Take a look a the time I spent yesterday trying to help you out !! geez :rolleyes:

I never said it was the "best", but best for the setup I have to test, read back through the posts ;) The benchmarking scrores were best for my device, and probably most others.

Yes there is a reason Samsung have set to 128: Partly explained before.............. is that not all cards are equal and they allow for lower end spec cards, also lower cache allows for very slightly less RAM useage & CPU.

I don't pander to individual needs, but do try to help out where time permitting and able. I have more than tried ti help you out, and by the way, you're welcome for the my help or at least trying :)

You are welkcome here, and in this thread, but no need to continually spam it. I have tried to help, and given you alternatives. Thanks. :cool:

Lastly, please remember, this is my time I am freely donating away from my family time!

Edit: Particularly for a device model I don't own.

Edit2: Overlooked the enrty in the init.rc, yep it is definately wriiten there as it's supposted to. There will be a way to change that with a init.d script, which I'll look into at some other time. You can probably change that manually yourself though and should work after reboot. Edit again: could have been the V6SuperCharger entry, have a look later.

.
[Galaxy Tab 7.7 Android Development] sas_sas:
"5. Flash tweak script"

What & Where is tweak script ?

Is this below ?

CWM_P6800_sdcard_read_ahead_1664KB.zip
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Yes.

Users reported the settings won't stick.

Most likely overridden by the kernel init.rc. Trying won't hurt. Can always delete the script and reboot if need be.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Will have the next build probably ready for release tomorrow.

Most things I tried were unsuccessful, but some tested ok,

Nearly done now, but trying to push a couple changes to gitHub,...... seems to be down.

Once that's done, I'll build and send for QC first :)
[Galaxy Tab 7.7 Android Development] Alcibiade:
With original ROM and kernel, but overclocked at 1.6Ghz with Tegrak...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
So what's original got to do with with thread?

Edit: unless you meant "SkyHigh kernel"?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v2.1.0

v2.1.0 is UP !!

Change-log

* Disable governors

- lulzactive

- userspace

- powersave​

* Added new governors

+ pegasusq (siyah version)

+ lulzactiveq (siyah version)​

* Auto EFS backup

+ EFS folder & partition saved to : /data/media/EFS_Backup (thanks siyah)

If you don't know about the importance of EFS backup, search XDA ;)

* Revert to Gzip compression

* Removed internal sdcard cache tweak. Samsung default = 128 KB (may/most probably change again in future ;) )

* External sdcard cache tweaked from 2048 to 1664 KB

* Removed some left over install files from /res folder

* Some battery saving tweaks in

setprop

(thanks wanam)

pm.sleep_mode 1

ro.ril.disable.power.collapse 0

wifi.supplicant_scan_interval 180​

Thanks again to edan1979 for the test.

CHEERS,

PS. sorry, couldn't get the FIOPS to complie

UITA :D

.
[Galaxy Tab 7.7 Android Development] hong25:
Great getting better. thanks for the hardwork
[Galaxy Tab 7.7 Android Development] aeron16:
does anyone know/tested this kernel with the eRobot custom rom?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I know of some that have.

Just try, and if it's not for you, flash the stock kernel zip or tar.

Pretty simple :)
[Galaxy Tab 7.7 Android Development] edan1979:
Yes... i test thelatest one with erobot
[Galaxy Tab 7.7 Android Development] loolser:
will it work on stock jp p6210xxmd3?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Read the OP. :rolleyes:
[Galaxy Tab 7.7 Android Development] nyoknying:
Hi UpInTheAir, I'm currently roaming - and I get a lot of "Modem Crash!!! bla bla bla" when I use v2.1.0 - more or less once every 6 hours. I reverted back to stock kernel (downloaded from the OP) and not having any for more than 12hrs now.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
So what are your kernel/governor settings, and UV anything etc? Maybe don't OC CPU, and set to stock 1400

Your ROM version etc?,

Any other ROM tweaks that "might"impact the kernel?

as data connection is ROM/modem related...... not kernel. Strange.
[Galaxy Tab 7.7 Android Development] aeron16:
Done it :) so far so good for half a day!
[Galaxy Tab 7.7 Android Development] UpInTheAir:
16 step CPU freq and voltage interface. Part of the next release :D sometime

Or maybe part of an extreme version with OPTION to OC to to 1700 and or 1800 MHz. Can't see it being really stable though ;) looking at adding an extra GPU step 520 or 533. (bringing it from the current 4 to 5) too

We'll see.......
[Galaxy Tab 7.7 Android Development] Redtabs:
Can't wait to flash it and try ! ;)) you the man UpInTheAir!!
[Galaxy Tab 7.7 Android Development] wlw6600:
cwm update,

but reboot when samsung appear,loop
[Galaxy Tab 7.7 Android Development] UpInTheAir:
You are running P6800 with JB 4.1.2 DXMD3 base firmware?

Read installation instructions and post#3
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Looks like the 16 step CPU will need for more work with the voltage interface. Changing any freq vdd + or - and tap "apply" with SetCPU app, results in crash/reboot. :eek:

Will take a look tomorrow and hopefully something simple and easy to find..... Otherwise I'll just have to skip it until I have the time to look more closely.

Managed to integrate the 5 step GPU max 520 with improved step thresholds (less aggressive and probably easier on battery) and tested 5 consecutive times with 3dmark app "ice storm extreme" with no issues. Only very minor GPU benchmark improvement (over v2.1.0), but probably due to the thresholds. Still needs work and plan to integrate stable UV .
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v2.2.0 UPDATE

>> v2.2.0 UPDATE <<

** FOR P6800 GSM/3G device running JB 4.1.2 DXMD3 ONLY !! **

Installation as per Posts #1-3

Change-log

* increased 4-step to 5-step GPU 114-160-267-533 MHz

* Increased 7 to 16-step CPU 100 - - - - - - -> 1600 MHz & voltage interface

* Increased pegasusq (siyah) "freq for responsiveness" from 500 to 800 MHz. Maybe slightly more battery, but with UV will be negligible.

* Slightly UV GPU freq voltage levels. Not sure if it's actually done right, but no negative affects though.

* Removed some stock governors : conservative, interactive, adaptive, powersave

* Couple other small GPU less aggressive threshold adjustments etc.

* Will update OP freq.vdd table later on.

++ Although I have increased the GPU max freq from 400 to 533, I don't really expect any real noticeable (real life) performance increase from 400 MHz. My GPU benchmark testing indictaes a relative low increase, if nothing at all.

Edit: Sorry no CPU 1700/1800 MHz option until able to lock the startup freq to 1400 or 1600 MHz. This is a safety measure to prevent freeze/reboot on thoses devices that can't handle it. I will look into it later, but not even in the "to-do" list.

CHEERS

UITA

.
[Galaxy Tab 7.7 Android Development] cymagnus:
Coming from 2.1.0, installed 2.2.0 and after some casual internet browsing on wifi, the back of the 6800 feels hot. Not sure you guys encounter same.

Do not have this heat issue on 2.1.0 or 2.0.8, I am not using any OC or UV progams or 'Pimp My ROM' btw. Reverted back to stock kernel..
[Galaxy Tab 7.7 Android Development] grazy:
Coming from 2.1.0 as well, but for me the 2.2.0 feel better and lighter. BTW i'm using pegasusq governor with row scheduler, no OV/UV. Thanks Dev.
[Galaxy Tab 7.7 Android Development] Alcibiade:
If you read the initial post I was answering to, the author was writing "Wow i just topped 5000 with quadrant this is crazy!". It's great to be enthusiastic, just wanted to show him that if what he was looking for was benchmark records I could get better another way and no, this was not "crazy". It did have t do with the thread, comparing apples with apples

Anyway,I love your work (Been on your all your ROMs on ICS) and your kernel looks really exciting with all the functionalities you have been introducing! Thank you for giving us so many nice devs
[Galaxy Tab 7.7 Android Development] UpInTheAir:
You are already OC @ 1600 MHz.

Try a CPU Control app to lower the max freq to stock 1400 or 1500 MHz. Maybe your device doesn't handle it. Also, adding a slight UV may help.

Or maybe it wasn't your device and was something else other than the kernel? Something else using extra CPU cycles in the background?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
No worries, but Tegrak still nothing to do with this thread.

Others can get those scores with with kernel, some can't. Some are just lucky. It's all about repeatability/consistency with minimal "effort".

Most benchmark junkies don't realise there is inbuilt thermal protection to stop the CPU from cooking. It will be limited to around 800 MHz. I have seen my CPU benchmark scores drop during extensive testing, and the CPU drop to 800 max regardless of any Control app locking out at max.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
With the added CPU freq steps, should scale a little less aggressive, although have noticed some aren't being used. I have increased the Pegasusq responsiveness frequency to 800 MHz (like smartassV2) and my device feels allot snappier.

This would be at the expense of very slightly more battery drain. You can use a control app such as SetCPU etc to lower the governor settings back down to (500) if you don't feel any difference between the two.

To counter any extra battery drain (at 800 MHz step), would suggest a slight UV. Some info in post #3. My "old" mild 7-step UV settings are on the table in Post #1 cab be used as a guide. must update it sometime.....
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Just to let you know that the 5th GPU step (533 MHz) doesn't appear to work.

Also, the first 114 is being displayed at 100 MHz, but 114 might be an unsupported freq, it defaults to 100 instead?

I suspected something during my pre-release benchmark testing, but wasn't totally sure.

After loading the GPU so the frame rate eventually drops, it max out at 400 MHz, which isn't bad, but still would like to know exactly why.

Observed actual freq steps in use are :

4-step 100-160-267-400

I'll have a look into it sometime, got a lot on today. Maybe forgot something or got it wrong. But anyone can look through my gitHub repo and look for the error or omission, please PM me or post here if you find something conclusive.

Thanks

Edit:

after some digging around, can't really find anything why, but have found how to ensure the GPU voltage changes will work properly. Not sure exactly which lines on the voltage table for our device ( B or C), so will change the whole column to reflect each frequency step vdd level. :)

A little bit of GPU UV seems to work nicely..... so far.

Still can't get the max GPU freq above 400 yet, might be some lines somewhere that need commenting out to unlock the 5th step at 533 (if it's available). Not really that important though, so might see if can 5-step 100 to 400 instead, otherwise back to a working 4-step.

Also trying to implement some sort of GPU interface. Maybe I can get something working, but will most probably require a script to affect changes. Just getting a little confused right now and starting to lose the plot, so will leave it for another day.
[Galaxy Tab 7.7 Android Development] abima80:
my preference goes to 2.1.0.

Feels that power over battery life more balance compare to 2.2.0.

tried 2.2.0 before but then revert back to 2.1.0 due to high battery drain.

anyway thanks skyhigh for your kernel.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
any battery stats to go with your post?

You can adjust Pegasusq "the freq for responsiveness" back to 500000. Currently set at 800000 for obviously "better responsiveness".

If using 800000, I do recommend a slight UV, to help save battery, but keep responsiveness. I have previously mentioned this before.

To change the governor settings, I use SetCPU or NSTools. There are other apps too.

I may change to 500000 in future, but currently like it. In previous builds, the siyah kernel settings were at 400000 (for S2), and this kernel didn't then support that voltage step. For my liking, 500000 didn't seem to work as nicely as 800000, bigger screen, higher stock max CPU etc than S2.

The next build is just about there, but I'm busy moving house, and unable to make final adjustments before sending for QC.
[Galaxy Tab 7.7 Android Development] abima80:
i only use setcpu free edition, just can select governor, dont have knowledge on how to set the voltage, Flash only.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
NSTools is free ;)

Just select the governor options, scroll down to "freq for responsiveness and change it. Save, and after testing ok, set on boot.

Next release will have a very slight UV (-25mV) from freq 100-1400. 1500 & 1600 will remaining as is.

Edit, forgot to mention the GPU is UV, UC/OC properly now, and some final tweaking will help too. Except for the 400 MHz set at 1050mV. In comparison, stock max 267 MHz is 1000mV. Unless you max out the GPU all the time, battery should be slightly saved too. The idle GPU is set at 100 MHz (900 mV) compared to stock 160 MHz (950 mV).
[Galaxy Tab 7.7 Android Development] TarjeiB:
Faster charge would be most excellent. I'll definitely try this if you get it working!
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Very easy done to change USB, misc, & A.C. charge rates, but don't won't do it if I can't have direct control (on/off) via app or script. It may not be a good thing for all....

I have also found some info to enable fast USB 3 charge as A.C.. there is an app for modded supporting kernels to turn it on/off. Not sure if the code is compatible, but will be worth the try.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v2.7.0 UPDATE

>> v2.7.0 UPDATE <<

** FOR P6800 GSM/3G device running JB 4.1.2 DXMD3 ONLY !! **

INSTALLATION as per Posts #1-3

DOWNLOAD in Post #2

Change-log

* Revert to a WORKING 4-step GPU 100-160-267-400 MHz (114 & 533 MHz are invalid freq)

* Lower min GPU freq to 100 MHz from invalid 114 MHz (stock 160 MHz)

* Added support for Triangle Away app (not sure if we even have a counter?)

* Slightly UV CPU freq 100-1400 MHz by -25mV. 1500 & 1600 remain unaffected

* Increased GPU 267-400 MHz threshold

* Better 4-step GPU "idle" and light use battery savings with UV & tweaked thresholds

* UV GPU properly, now working

100 MHz = 900mV

160 MHz = 900mV (-50 mV > stock 950 mV)

267 MHz = 950 mv (-50 mV > stock 1000 mV)

400 MHz = 1050 mV​

* Updating OP now. Will update OP freq.vdd table later on.

* Sorry, could not get any GPU Control Interface working for P6800 JB device, works for ICS. I need JB for my P6810 to test a lot further. :(

* This is the last release for quite a while, so enjoy :good:

* Thanks again to edan1979 for test

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] B4R7H:
busyBox installed to system/sbin not xbin anymore?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
It can be installed to system/bin, system/xbin or sbin.

I just borrowed wanam's (adam kernel) code from his initramfs to speed things up. ;)

# busyBox
if [ ! -f /system/xbin/busybox ];
then
ln -s /sbin/busybox /system/xbin/busybox
ln -s /sbin/busybox /system/xbin/pkill
fi

if [ ! -f /system/bin/busybox ];
then
ln -s /sbin/busybox /system/bin/busybox
ln -s /sbin/busybox /system/bin/pkill
fi

You can view it in sbin/SkyHigh.sh

I don't know which is better or why. I just know it works for me, so why change it? :)
[Galaxy Tab 7.7 Android Development] skycruzer:
From what I've seen, P6800 has no counter.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
That's what I believe too, but Samsung are getting sneaky with their firmware releases.

The SGS4 has it hidden in the bootloader, and not shown in download mode. ChainFire is working on it and other affected devices.

Our device models are most likely not included in Samsung's efforts though. But I'm only guessing.
[Galaxy Tab 7.7 Android Development] skycruzer:
Well, lets hope so...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Extreme v2.8.0 (unofficial release)

*** EXPERIMENTAL *** Done just for fun. :laugh:

This is

untested

on P6800 JB, just don't have the time ;)

>> Extreme v2.8.0 Unofficial Release <<

** FOR P6800 GSM/3G device running JB 4.1.2 DXMD3 ONLY !! **

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

2. If you dare to flash, you will need a CPU control app to adjust the CPU freq from the safe startup values

INSTALLATION as per Posts #1-3

DOWNLOAD in Post #2

Change-log

* CPU min/max safe startup freq default = 200-1400 MHz

* CPU min/max safe voltage = 800-1450 mV

* CPU OC to 1700 or 1800 MHz with CPU control app

* UC to 100 MHz with CPU control app

* 100 MHz voltage increased +25 mV to 950 mV for stabilty

* BTW - I couldn't get great benchmark results at 1800 MHz due to thermal throttling of the CPU to 800 MHz.

In other words, I used Cool Tool app to show CPU freq on screen whilst benchmark. I could see the 1800 MHz max, then limited to 800 MHz due to EXCESSIVE CPU HEAT !

There is a way to increase the thermal limits, but I don't want my silicon melted ! I am sure 1600 MHz is more than enough.

CHEERS :D

EDIT : I did say that 2.7.0 was the "last for a quite while", but I couldn't help myself :)

UITA

.
[Galaxy Tab 7.7 Android Development] sas_sas:
I can not manage to change Governor and I/O options.

Tried with pimp my rom and NStools but can not change why?

I have Erobot's v1 rom.. Flashed w/ 2.7.0...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Was hoping someone could suggest something, but please try;

1. Force stop all CPU control apps and clear data.

2. If CPU Control app uses init.d script, delete it.

3. Re-flash kernel

4. Use just ONE control app at a time
[Galaxy Tab 7.7 Android Development] sas_sas:
Ths for your kind concern.

I did all your recommendations.. Flashed 2.80 this time..

I installed only NSTools. It tweaks I/O Sch but can not change Governor options, meaning not active governor tweaking at the NSTools.. İt says 'not available'..

Why?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I'm not sure..... maybe ROM...

Try delete NSTools and reboot wipe dalvik & cache. Restore NSTools app (no data) from a previous Titanium backup (not market).

Not all governors are supported and able to be tweaked.

Also, does the Superuser log show current SU access?
[Galaxy Tab 7.7 Android Development] sas_sas:
SU access is okay. But not works..

Tried with CPU control pro but it also can not change anything..

Most probably there is something related with ROM itself...

Always remain with Defaults pegasusq and ctq..

I wonder if there is someone else having erobot's rom and flashed SkyHighKernel and managed to tweak this kernel ?

Ths again UpInTheAir..
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Unroot with option in SuperSU / settings / "full unroot", boot into recovery, wipe cache and dalvik and re-flash kernel.

The kernel will then install root for you.
[Galaxy Tab 7.7 Android Development] theerachai:
don't have any problem, using erobot and skyhighkernel.

I use setcpu .
[Galaxy Tab 7.7 Android Development] sas_sas:
I carried out this solution and installed setcpu and WORKED ...

Thanks...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Nice :)

Away traveling and don't know exactly why your SU problem occurred. Unable to take a look at the ROM to see if there might be a slight kernel incompatibility somewhere.

But, Kernel doesn't install root if you already have it though...... you can always check the code found in /sbin/SkyHigh.sh

ROM or kernel fault, doesn't matter for now, at least there's a solution. :)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Delete