yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Just edited my previous post to include some more info and clarification. At some time, I will also edit the OP or FAQ to include more info.

OT:

My SGT 7.7 days are fast coming to an end. When I return home in approx 4 weeks, I will be purchasing a Samsung Galaxy Note 3 sm-n900 (Octa International version). If a recognized dev hasn't made an appearance by then, I will be trying to help out there with either a ROM or kernel (probably the later as there is absolutely nothing). Yes, it will indeed be a big challenge...

The SkyHigh P6810 and P6800 kernels will still (edit: hopefully) continue development for a release or two yet. There are still a few things to try implement before passing my device to my 9yo son :) But beyond that, there will be no promises.
[Galaxy Tab 7.7 Android Development] lomniom:
Very sad to see a good developer leaving, but every thing that begins should always end. Thanks for all your efforts. Btw the 3.7.1 works great on my tab and I am staying with this kernel for now.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
When I return home, I need to re-build my PC and build environment. After that, compile a kernel for the new P6810 JB 4.1.2 ROM. I am confident that having the firmware on my device, I'll be able to get a configurable GPU voltage/freq sysFS interface working for both P6810 & P6800 JB 4.1.2 kernel versions. I have it working nicely for ICS, so being able to test and make the relevant source changes for JB shouldn't be a problem now.

OT : Maybe my son will never get the tab.....

I'm not sure if I can part with it. I might get him something else instead. Who knows, I certainly don't :)

I still enjoy the SGT-7.7 using & tweaking the hell out of it (given the time & opportunity) :)

But as you said, all things will end eventually....
[Galaxy Tab 7.7 Android Development] lomniom:
Great! Your kernel already integrate fstrim right?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I have no idea about what kernel source changes are needed for this or even thought about looking into it. I am very busy away at work and my current location has very limited internet.

If you or anyone else finds any good information on source or intramfs changes needed for the kernel, please feel free to post the links etc. I'll try take a look when I return.
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
Good thing you found a replacement for your 7.7. I'm getting bored waiting for sammy to announce the 7.7 successor. For now, I'll stick with it. By the way v3.71 works without any issues on my gtab.

••••• | Sent from GT-P6800 using Tapatalk Pro | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
So the v3.8.0 has "issues" with Thunderbolt IO scheduler tweaks? Or just conflicting with your other tweaks/mods? All fine on my ICS.... I will soon be able to test myself using same JB MD3 firmware. In any case, the plan eventually is to have it (along with some modules) optional in the Aroma installer.
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
Must be isolated case for me. I still have no idea what caused it. No mods, scripts or tweaks running in my tab. Just Stock JB 412.

••••• | Sent from GT-P6800 using Tapatalk Pro | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Sorry, might have missed something somewhere. What is "it" ?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
OK. Found out how to implement fstrim (system, data, cache) on my SGS4 on boot. Works well. No need for any app !

Unfortunately, can't yet test on my P6810 due to SkyHigh ICS kernel brick-bug patches. Is more of a ROM tweak, but I'm sure I can implement into kernel no problem once I return from work and flash the P6810 JB 4.1.2 firmware for my tab.

Only thing I'd like to do is put a timer on it, so it runs every x mins/hrs/days or only when screen is on etc. I will look further. :)
[Galaxy Tab 7.7 Android Development] schen:
I dont think its is a good idea to have fstrim run automatically every x hours or at x oclock everyday. Somehow it takes significantly longer when trimming tab 7.7 compared to note2 or gal chat for example. Singnificantly I means much much longer to run on tab 7.7. Might interupt something. So run every reboot is more than enough. Currently I have mine run at every reboot using third party apps.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I have thought about that, but will test a little first. As you suggested, on every boot is probably the way though. Just like most zipalign, sqlite etc

Edit: Running on boot, I do expect the boot process to slow down a little, or maybe I will just give it a sleep 10 or something to counter that.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Deleted, quoted instead of edit...
[Galaxy Tab 7.7 Android Development] lomniom:
Good idea buddy.
[Galaxy Tab 7.7 Android Development] bodivas:
I tried to compile the kernel for p6810 from your source and it turns out this error:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Difficult for me to look into the driver error from my current location. I am really busy with 24 hr shift work and just have very basic communications. I assume you are using toolchain 4.4.3 and v3.8.0 config, along with build environment setup correctly? You might also need to extract the initramfs from the zImage and use that as a base (with your mount point changes).

Other than that, I just don't have time and resources with me until I return home. Sorry.

Edit: You're welcome to keep trying, but I would prefer you use for personal use.

Rest assured, I will sort out a SkyHigh P6810 JB kernel for users soon enough. ;)

Please be patient. :)
[Galaxy Tab 7.7 Android Development] bodivas:
I did just so (with standart config all right..

I'm not going to release this kernel (even though a lot of people want it), i wanted to see how stable than the configuration of samsung. Eventually I got bored-look forward to your return.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
When I return, maybe we could collaborate on the build? If you have a gitHub account, you could also fork the source and push changes. I don't pretend to know or understand everything. Help and informed (constructive) advice is always welcome :)
[Galaxy Tab 7.7 Android Development] nyoknying:
guys, anyone still has the stock voltage table? I messed up my voltage setting and would like to revert to stock (instead of kernel)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Just search my source commits, everything is there for all to see ;)

https://github.com/UpInTheAir/P680...mit/945df4e297faec569788f17ca1a3b5d578871e10

Look at the 2nd column:

Red = Samsung stock (MHz=200-500-800-1000-1200-1400)

Green = SkyHigh default -25 mV (MHz=200-500-800-1000-1200-1400)

Cheers,

UITA

Edit: If you just want to revert to SkyHigh default, just wipe CPU control app data (or delete init.d script) and reboot.
[Galaxy Tab 7.7 Android Development] lomniom:
UITA, for the next release, would you please put back the stock voltage? Your kernel is rock-stable without any reboot when the stock voltage is applied. Thanks.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Are you using any CPU UC, min freq100MHz ?

If you are, I suggest just using the recommended SkyHigh defaults. 200---> 1400 MHz.

You can also do CPU stress test by locking your min/max (performance governor) to each freq step. This way you can find out which freq/vdd combo your CPU doesn't like. (Edit: higher freq may give you thermal limiting if stress tested for extended periods. If your CPU is stable at these freq/vdd, further UV will help lower the temp and reduce thermal limiting).

You can use the Stability Test app: https://play.google.com/store/apps/details?id=com.into.stability

SetCPU app may also have the function.

DO NOT set any freq/vdd test combo at boot ;)
[Galaxy Tab 7.7 Android Development] lomniom:
No, I use 200-1400 as default. Normally the tablet reboot when it pushes the maximum power for RAR decompression for example. After raising +25 mV, it doesn't reboot anymore.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Development update:

Haven't forgotten about you guys here. Been away working and should be home at the end of this week. After a little family time, continue with development.....

First of all, need to flash the latest JB 4.1.2 Port, build/buy & re-setup new PC with build environment, followed by a SkyHigh JB kernel up and running for my P6810.

2nd, a minor release with fstrim on boot

3rd, GPU frequency/voltage control (sysfs interface) for the JB kernel.

4th, Continue with this kernel development. I have LOTS still on the list. Some may be doable, others maybe not due to lack of knowledge, time, and or other commitments.

5th, possibly a (personal) custom ROM with lots of mods the way I want. If I have time, I MIGHT share with both P6810 and P6800 users. Wait and see. I don't really have the time to support it and will just be a little side project. Maybe I'll just release a patches/add-ons for stock JB ROM instead- a more reasonable idea ;)....

Although I'll probably be handing this tab over to my son.....

THIS KERNEL & MY CONTRIBUTIONS HERE ARE FAR FROM DEAD JUST YET ! :)
[Galaxy Tab 7.7 Android Development] lomniom:
Waiting for them boss! :good:
[Galaxy Tab 7.7 Android Development] ninekaw9:
Me too, the game lag badly and load very slow with very high i/o usage. Running skyhigh 3.8, erobot 3.2, multiwindows mod v2.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Try a different governor/IO scheduler combination. Start with stock on-demand /CFQ. Let me know how you go.
[Galaxy Tab 7.7 Android Development] schen:
I shared my setting several post before this. I used that setting on 3.5 (1800mhz max) and 3.6 (1600mhz max).

Try set your voltage, min max freq, governor, scheduler, freq for responsiveness, sd cache the same as mine and then do wipe cache, dalvik cache. I am sure it will run as smooth as mine if your tab can take the under voltage like mine.

One thing I just found out is that DISABLE Enthropy contribution fell better for mine.

I did not try asphalt 8 but I do tried temple run oz, riptide gp2 with graphic setting all max out, plant vs zombies 2, angry bird friends. All run without a glitch except pvz2 and riptidegp do stretch the cpu big time its frequency keeps throttling to 800mhz after 10 minutes of play time. Cpu temp can even reach 75degree after 20 minutes. It means that first throtle wont be able to bring the temp down below 65. But games play fine.

Uhhh...if you install asphalt 7 or 8 you should make sure Media Storage DO NOT scan asphalt data directory because the data consist of thousand of small files instead of one large obb files for example. I had problem before with asphalt 7.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
JB 4.1.2 Volume

Hi, Does anyone understand this commit and how to increase the volume at kernel level?

https://github.com/HomuHomu/android_kernel_samsung_smdk4210_new/commit/0527f5e026865abfc0dd30259e8ced881613bd36

We have same code in a different build file mc1n2.c for our SGT-7.7 device :

https://github.com/UpInTheAir/P6800_JB_SkyHigh_Kernel/blob/master/sound/soc/codecs/mc1n2/mc1n2.c

I really have little idea about what those changes exactly do !

Any info would be appreciated, I'd like to implement approx 3db volume gain.

Thanks
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.9.0 update

>> v3.9.0 UPDATE <<

RE-COMPILING NOW - MADE AN ERROR !!

** FOR P6800 (GSM/3G) 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

CHANGE-LOG v3.8.0 -> v3.9.0

* Disable zRAM debug

* IO scheduler set the same for internal & external sdcards via initramfs : default = SIO

- [MENTION=647076]Shen[/MENTION], yes it's working this time ;)

Added & changed code in Green in the init.smdk4210.rc initramfs file

# SISO-ANDR_PERF :: START Changing scheduler to [COLOR="Lime"]SIO[/COLOR] and reseting cpu min freq to -1 after boot complete
on property:sys.boot_completed=1
write /sys/block/mmcblk0/queue/scheduler [COLOR="Lime"]sio[/COLOR]
[COLOR="Lime"]write /sys/block/mmcblk1/queue/scheduler sio[/COLOR]

.

* Updated to SuperSU 1.65 & binary v1.61 (installs only if you don't have any)

* fstrim lagfix on boot (trims system, data & cache) - slows down reboot, but who cares, aren't we more concerned with using device?

* Reboot after first flash !

* Increased windowsmgr.max_events_per_sec from 90 to 200

TO-DO

* Lots

INSTALLATION

1. NANDROID (just in case)

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

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

4. Reboot again to fstrim your partitions

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)

* The CPU freq

may

exceed the max cap setting on wakeup. ie max CPU freq set @ 1400 MHz -> turn on screen -> 1600 Mhz very very briefly -> then back down

Can't fix the CPU Level 0 bug. Refer to my post HERE. It is a FIRMWARE bug present in both stock and SkyHigh kernels​

ISSUES?

* READ POST #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
RE-COMPILING NOW - MADE AN ERROR !! v3.9.1 WILL BE UP SOON.

v3.9.1 is up :)

Sorry to anyone that DL & flash v3.9.0. Please flash v3.9.1

Cheers,

UITA

.
[Galaxy Tab 7.7 Android Development] lomniom:
Now testing 3.9.1. Reboot is longer because of fstrim but I don’t test yet the difference with 3.8.0.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
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.

I thought about a script timer, but a manual reboot once a week should help. 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.

Edit: I have added some more info to Post #3 FAQ fstrim lagfix
[Galaxy Tab 7.7 Android Development] lomniom:
Antutu was 13197 on 3.8.0, now 13363 on 3.9.1.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
A reboot a week should help. Other ROM tweaks such as sqlite and zipalign might help keeping the tab running smoothly as well.

Just been trying to update the source to the latest Mali drivers. Just can't get it to compile....... I need this to be able to implement GPU freq/voltage sysfs Interface Control. It's just not working :(
[Galaxy Tab 7.7 Android Development] sas_sas:
Flashed w/the new version of the kernel, seems better..

Ths UITA...
[Galaxy Tab 7.7 Android Development] ngoonee:
Hi UpInTheAir, am looking at your kernel but noticed its only for stock 4.1.2? Not usable for PAC Rom (4.2)?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
No, only Samsung based JB 4.1.2 ROM.
[Galaxy Tab 7.7 Android Development] Silver-7:
Tried this kernel for few days, good performance.

But besides the long time boot that was mentioned by OP, after restating the device it reboots itself again after few minutes which is really annoying.

Also Auto Brightness isn't accurate, very slow response.

Thanks for you efforts.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
1. Read Post#3 "ISSUES" first.

2. Then try increasing all CPU voltages +25mV to "stock" level before the reboot.

Ref: Auto brightness - haven't noticed any difference to that of stock kernel.....
[Galaxy Tab 7.7 Android Development] Silver-7:
Thanks.

About deleting or renaming 90lagfix file. I noticed that after reboot the file back again to init.d folder , and therefore do the fstrim and cause long boot time..

Just a suggestion to disable this feature in next Kernel updates, as we can do fstrim anytime manually by lagfix apk.

Thank you
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thank you for the feedback and suggestion.

I don't use lagfix app, and the script trims system, data, cache, and preload. Our JB 4.1.2 uses preload partition and the app doesn't trim this. Another reason I don't like it is because it's an unnecessary extra app, taking up either resources or space.

The average user doesn't/shouldn't need to reboot that often, so it stays. In my ROM, I have increased it to 60.

If the power user wishes, just change the sleep 30 to whatever you like in seconds. You might need to mount init.d folder R/W first, but don't forget to R/O after. If you've got it right, check the script log output after reboot and some x seconds.

In any case, I like this feature, and it will stay, but maybe with some future adjustments though.
[Galaxy Tab 7.7 Android Development] ngoonee:
Am downloading your ROM now, may I assume since this thread is active that your ROM uses the stock kernel and this is meant to be flashed on top of it for those who want to?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
You need to flash this kernel separately after the first ROM boot.
[Galaxy Tab 7.7 Android Development] lomniom:
For the next version, would you use Aroma to choose UV or stock, to have fstrim or not on reboot please?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I just don't feel like looking at kernel for a while.

If there's another version, I "might" remove the -25mV.

I don't think I'll continue with Aroma version because you can't use it in .tar Odin version. Wait and see on that.

If you don't like the fstrim, open the init.d script and comment out the lines. Ie. Put a hash # at the start of all lines and then save.
[Galaxy Tab 7.7 Android Development] deani77:
Working so far with last kernel...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v4.0.0 update

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

** DELETE ANY INIT.D 90lagfix SCRIPT BEFORE FLASH **

CHANGE-LOG v3.9.1 -> v4.0.0

* Reverted in-built entropy generator for now

* Added sleep 60 command to lagfix script. Minimal impact on boot time now

* fstrim lagfix will now trim preload partition (there is

no app

that can do this, only this tweak !!)

* lagfix tweak can now be disabled and re-enabled. Please refer to Post #3

INSTALLATION

1. NANDROID (just in case)

2. Flash SkyHigh P6800 JB 4.1.2 ROM or any other P6800 ROM based on official 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)

5. Reboot again to fstrim your partitions

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)

* The CPU freq

may

exceed the max cap setting on wakeup. ie max CPU freq set @ 1400 MHz -> turn on screen -> 1600 Mhz very very briefly -> then back down

Can't fix the CPU Level 0 bug. Refer to my post HERE. It is a FIRMWARE bug present in both stock and SkyHigh kernels​

ISSUES?

* READ POST #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] lomniom:
Did you revert back to stock voltage?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
It's not on the change-log or commit on gitHub, I haven't done it.

I only looked at this thread after I'd released and posted the update. Sorry. Next time maybe?
[Galaxy Tab 7.7 Android Development] Silver-7:
Thanks for the update looks good.

Glad you gave us the option to enable and disable fstrim! That's great. And about that is it enabled by default? Coz I can't see 90lagfix script in init.d folder..the folder is empty.

Thanks
[Galaxy Tab 7.7 Android Development] UpInTheAir:
enable by the file command in Post #3 and reboot twice

Edit: First boot installs but doesn't trim.

2nd (or subsequent boots) trims partitions

You can check the log output and time after trim has finished
[Galaxy Tab 7.7 Android Development] Silver-7:
Thanks it worked :thumbup:

So it was disabled by default.

Boot time is better now , it did the trimming after 2nd boot.

Thanks for your efforts.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I have for next release........ ;)

Check my gitHub commit https://github.com/UpInTheAir/P6800_JB_SkyHigh_Kernel/commits/master

I'm still playing, so NO ETA soon. :)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Hey, have patched the kernel to stop CPU scaling above max set frequency. Thanks to code from Yank555.lu Yeah :)

So this means that I've re-introduced optional CPU OC to 1800 MHz (up from 1600 MHz) ! SkyHigh default will still be 200-1400 MHz though ;)

Currently integrating & testing some more V6SuperCharger values into kernel. Also, increasing the LMK minfree values really make the ROM fly, just trying to balance between performance, multi-tasking and using zRAM.
[Galaxy Tab 7.7 Android Development] schen:
Nice to hear this. I might opt for 1800 version if we can stop scaling above max frequency for real.

Since you are preparing an update I might as well give you some feedback from version 4.0 that I just install:

SD Cache setting seems to be the other way round than usual: Internal:1024; External 256

Scheduler both set at SIO but I cannot set my scheduler through init.d anymore. Has to be through apps like SD Booster or Faux Clock (The only two apps that allow us to set internal and external independently) But this two apps has given other problem as well so I currently just use default SIO. I am wandering if you dont tweak the scheduler in the kernel what will be the default scheduler?

Lastly can you take a look at your GPU Voltage: You have set as follow:

100 MHz = 900mV

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

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

400 MHz = 1050 mV

I am wandering if we can use 1000mV for 400MHZ? This is really important if we want to run it at 1800MHz as it get hot quite fast. I can test the 1000mV for 400MHz for you before you post the release if you want. at the same time I can test 850mv for 100MHz also

Thanks
[Galaxy Tab 7.7 Android Development] UpInTheAir:
It's real :) it's fixed, and 1800 will be back. Check my commits. I don't recommend it, but is there as an option. I will publish the usual warnings along with it.

Don't know about the read ahead cache. Mine shows 1024 internal and 1664 external as default. I'll check if init.d scripts can change it. Getting too late here. Might be an issue where I put the fstrim code in the sbin/SkyHigh.sh script placed after the init.d enable?...

Edit: have been testing with custom SkyHigh ROMs with in-built init.d support. Will check on stock JB later.

From memory, if I don't tweak kernel, stock scheduler will be cfq. (noop, deadline, cfq).

My device isn't stable at GPU 1000mV/400 MHz. I have been testing my P6810 device with JB 4.1.2 installed and also re-partitioned as P6800, so don't really need any testing there thanks.

Appreciate the good feedback though. Thanks.

Edit; update is a while away yet. Having a few issues with a couple things and getting sidetracked looking at and reading other stuff....
[Galaxy Tab 7.7 Android Development] lomniom:
For my phones, S4 and Nexus 5, ROW (Read Over Write) works best for eliminating stutterings and lags.