yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] frogeed79:
Hi,....

I think, its my tab have problem....v 3.2 same 3.3.....laggy when play asphalt8...I want reset when have a time, or maybe just stay with your stock kernel until new release....thanks
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.5.0 update

>> v3.5.0 UPDATE <<

** 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. 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-1600 -or- 200-1400 MHz

5. Recommended governor = ZZMoove & scheduler = SIO

Change-log v3.4.0 -> v3.5.0

* FIXED custom bootanimation support for JB

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 ;)

* Updated to ZZMoove governor 0.7b (thanks zanezam)

* Re-tweaked ZZMoove governor

* Set SkyHigh kernel default governor = ZZMoove

* added xz compression support to kernel source

* Compiled kernel using xz compression for better compression/decompression to size ratio [ref: lkml.org]

* Remove legacy & ID Mapper from NFS module

* Updated thread Posts #1-3

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 -> 1800 Mhz very very briefly -> then back down

ISSUES?

* READ POST #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I feel a bit of a fool..... How long have I have my tab ?!?!

Just added configurable vibration intensity!

BUT, guess what.........?

The tab already has it in menu/settings/sound :laugh:: laugh:

I'll "give myself an uppercut" :eek:

Edit: Too much flashing, and not enough time actually using it :)
[Galaxy Tab 7.7 Android Development] B4R7H:
dear UITA..cant u make ur Kernel max freq only 1600Mhz so that no freq exceed to 1800Mhz? If this situation same on stcoks just ingore me :silly:

I never using 1600-1800Mhz tho cuz it might damage our cpu...I love my tab so thats y Im not over clock it...

P/s: I just load v3.5...:D
[Galaxy Tab 7.7 Android Development] UpInTheAir:
The bug will very very briefly exceed your max set frequency to whatever is level 0 is in the voltage table.

Example 1

L0=1800 MHz

Your max freq=1400

Will very briefly jump to 1800 MHz on screen wake or tapping home button.

Example 2

L0=1600 MHz

Your max freq=1400

Will still exceed your set max freq very briefly, but to 1600 instead of 1800

Safe default start-up limits are set 200-1400. So in reality, even if I change level 0 from 1800 to 1600, the bug will still cause you to OC ONLY on some occasion to 1600 as I described above.

This is not a new bug, but been there all the time. I just haven't managed to fix it. I just put it in the change-logs now so it is better known.

Edit: I still might bring level 0 down to 1600 MHz in future builds, though no promises, but we'll still have the bug.

Edit 2: OC on this tab is quite stable for brief period, just the CPU will get hot and will be protected by thermal limiting/throttle to 800 MHz during benchmarking. For more info, have a read of Post #3. Your device could freeze or reboot if it can't handle the freq or insufficient voltage, but your tab won't cook.
[Galaxy Tab 7.7 Android Development] konsolen:
Why you recommend the zzmove gov? I get around 20% less power on different benches. And if we let benches out, i dont see any plus of smoothness in normal use. Is the bateery factor better?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
From my "observations", it seems to scale quite well, using what freq is actually needed.

I don't use my tab to benchmark a great deal, in the real world, there isn't too many circumstances where you need to max out the whole device at once (and instantaneously).

Without any hard data to post, but based on my observations and monitoring using cool tool app, seems to be OK with battery and balanced with effective scaling and real life performance. On my device, it scales to max freq when needed without any apparent lag.

As per OP and gitHub, I have also tweaked ZZMoove smooth up threshold for slightly better battery (at expense of responsiveness). I can't see any negative effects on my tab as yet.

If your just concerned with the benchmark, use on-demand or (performance) ;)

If you don't like ZZMoove (for whatever reason), just change it, or try experimenting with various governor settings. :) If you aren't sure, have a read of and post in zanzam thread here at XDA.

But the above is my reasoning why I currently use it as default.

Edit: here is zanazam thread, http://xdaforums.com/showthread.php?t=2326544 .

It's based partly on a de-tuned on-demand (conservative) governor. Info on various governors in Post #3
[Galaxy Tab 7.7 Android Development] stenny:
I also notice zzmove not as smooth as 3.4 default, I also notice cpu getting hot with zzmove. I revert back to version 3.4 for now.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Why don't you please be constructive and see what might be the cause ? Install cool tool app to monitor what the CPU is doing ;) It can't cause heat unless stuck on a high freq (for whatever reason).

If the governor isn't too your liking, just change it.....simple.
[Galaxy Tab 7.7 Android Development] schen:
Ha...ha...ha...be constructive. BTW have you thanked Stenny for showing you how to fix the init.d problem that is there from the beginning.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Next update: will be trying to get an Aroma installer working with some of the kernel tweaks and modules etc optional during instal. Don't know when it will be done though, but have a headstart thanks to yank555.lu permission to kindly use/modify some of his work.. Only just started, but may not finish it (even for my P6810) anytime soon.

Maybe have a minor update before that though, as this project will soon be put on hold for a month or so :(
[Galaxy Tab 7.7 Android Development] lomniom:
The settings for 3.5 is different from 3.3 in the trickster mod. I adjusted my responsiveness and wakeup at 600000 for the 3.3 and cannot do the same anymore on the 3.5. So going back to 3.3 at the moment.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I don't understand you..... Did you read the change-log or gitHub commits ?

Have to say user error here. The default governor has now changed to ZZMoove governor. Written by different dev. Of course things would be slightly different. Have a read about the various governors and try understand how they basically work. If you still have questions, there are links in Post #3 and recent thread to post your questions on the appropriate thread. ;)

According to my source changes here: https://github.com/UpInTheAir/P6800...mmit/dab91fdcac4bf43a5d22fcb8586febe16c862b0f, I have set ZZMoove wake up to SkyHigh level 13 (500). Just change it to level 12 (600). Edit: but the bug will unfortunately still ramp that to whatever I hard-code level 0 to (currently 1800) instead (on screen wake or launcher home button).

If you also took a look at my source changes you would see I have made no such "freq for responsiveness" changes to pegasusq governor. So how is it gone? :confused:

Changing governor and tweaking works fine for me using this method:

1. Just change your governor

2. APPLY (tap menu button and check)

3. Make your changes in "governor control"

4. APPLY

How that helps you now enjoy v3.5.0 :)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
! ! DEVELOPMENT IS CURRENTLY SUSPENDED. REAL LIFE IS TAKING PRIORITY !!

Was in the middle of another attempt to give P6800 users GPU Control.... Try again in a couple months.

Please enjoy the effort and time I've put in so far. Any problems, please read Posts #1-3 and especially Post #3 first.

Cheers,

UITA
[Galaxy Tab 7.7 Android Development] lomniom:
UITA, this is what I'm talking about Pegasusq governer control which I cannot change inside the 3.5 even if the pegasusq governer is well selected.

The value numbers are not the same as in the snapshot here.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Sounds like a app issue.

Read Post #3 for issues
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Max Level 0 cpu freq bug

REF: MAX Level 0 CPU FREQ BUG

Done some more digging into this bug and is present in stock kernel for P6810 ICS LPP. I have tried various adjustments and patches without success. I can probably assume it's in your stock MD3 kernel as well.

I test just stock by :

1. Using cool tool app to show live CPU freq

2. Use CPU control app to set max scaling freq to 1200 MHz

3. Tap home button or turn screen off/on

4. Observe the live CPU freq (very brief) of 1400 MHz

Conclusion : Whether you are using stock or SkyHigh kernels, for now, we just have to live with it :(

If I have time in the next day or so, I will do my best with a little update for you. Since I have no way to currently fix the stock bug, I will cap max L0 CPU freq at 1600 MHz (instead of 1800 MHz). Defaults will remain at 200-1400 MHz (unless user tweaked). I have already pushed the changes to my P6810 gitHub
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.6.0 update

>> v3.6.0 UPDATE <<

** 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. 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-1600 -or- 200-1400 MHz

5. Recommended governors etc = Read Post #3

Change-log v3.5.0 -> v3.6.0

* Revert to 16-step CPU scaling (max 1600 MHz to save battery & compatibilty).

Start-up defaults are still 200-1400 MHz (unless changed by user)

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

* Updated to ZZMoove governor 0.7c (thanks zanezam)

* Removed my tweaking from ZZMoove governor (

may

give slight lag, so removed it)

* Adjusted ZZMoove governor for SGT 7.7 SkyHigh kernel

* Set SkyHigh kernel default governor = pegagusq (think should keep some happy :) )

* UV motor -100 mV (3.1V → 3.0V)

* UV LED -100 mV (3.2V → 3.1V)

* Updated thread Posts #1-3

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] B4R7H:
Thanks UITA for new update with max freq 1600Mhz
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I did listen to users wishes. :)

Was hoping to find cause and fix the Level 0 bug, but once I realized that it's stock firmware related and no quick fix (did try many times), decided it was better to be a little more conservative such as my very light under-volting and other kernel mods/tweaks.
[Galaxy Tab 7.7 Android Development] lomniom:
Thank you for making pegasusq the default governor again! You did listen to the users! =)
[Galaxy Tab 7.7 Android Development] stenny:
Thanks for revert back to pegasusq, its now smooth and fast as before and no more cpu hot issue and also battery friendly, Good Job.
[Galaxy Tab 7.7 Android Development] schen:
Back to 1600mhz max, init.d working properly now. I guess I will give it ago again. I have no hesitation to thank you on 3.60 release. No Hard feeling?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Hey, your now off "ignore".

I do appreciate the good and bad feedback (as long as it's actually feedback and not telling me what to do or criticism). This project is done in my spare time as (one of) my hobbies. I don't have to, but I just like the challenge and to help out and share with the community where time permits.

Thanks is not expected, but always nice manners and gratitude for my time and effort put into this project (whether liked or not).

If anyone wants to ever donate instead, please make a contribution to a recognised charity, XDA or dev-hst for hosting my work and files for nothing ;) :)
[Galaxy Tab 7.7 Android Development] lomniom:
Good answer dev. =)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.7.0 update

>> v3.7.0 UPDATE <<

** 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. 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.6.0 -> v3.7.0

* Updated to ZZMoove governor 0.7d [zanezam]

* Adjusted ZZMoove governor for SGT 7.7 SkyHigh kernel

* Update to SuperSU v1.60 & su binary [Chainfire] - will not update if you have

any

previous version installed

* Dynamic management of dirty page writebacks [Christopher83]

* Lower vm swappiness from 60 to 20 (performance)

* Implement LZ4 compression/decompression [psndna88 & Yank555.lu]

* Change zRAM compression from Snappy (v4) →LZ4 (faster)

* Add sysfs interface to Enable / Disable Android Logger [AndiP]

- Switching done via /sys/kernel/logger_mode interface

- Default is 0 (off)

* Suspect initramfs power-saving tweaks causing wifi power switching issue with P6810: seems to be fixed now

- Disabled power saving tweak

[B]#[/B]/system/bin/setprop pm.sleep_mode 1

- Changed power collapse from 0 to 1

/system/bin/setprop ro.ril.disable.power.collapse 1

* Updated thread Posts #1-3

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] B4R7H:
wow another update...gr8 will load it asap :good:

btw UITA i have this some problem on v3.6 it seems i cant recharge my Tab with my power bank can u check what is the problem? theres an red X on batt icon like when we connect on PC (the red X)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I've made no recent changes that would affect the charging.

1. Do you have the "red X" with stock kernel?

If I'm not mistaken, stock ROM will show battery "red X" on USB power. The systemUI needs to be modded if you want charging animation.

2. Please observe for a good period of time with power bank connected and not using the tab (screen off). Recheck to see if the battery % has actually increased.

** EDIT - Changing the stock behaviour

might

be possible on our device without having to mod your own ROM.

sec_battery_px: some small fixes

ATM, I don't really feel like returning my tab back to stock ROM to test this, enjoying using it for once :) The change in the source code is for P2 board, not our P8.......

I know I can also make a small change to the code (same file) and the tab will think that any USB connected power is AC, and allow up to the max 1500mA (1.5A) charge current. I have no USB 3.0 ports (~1.0A) or high capacity A/C charger with USB port to test.

You can test this by also viewing /sys/class/power_supply/battery/batt_charging_source

0 = battery

1 = USB

2 = AC

** EDIT 2 : The above patch works for my device, needs more testing !
[Galaxy Tab 7.7 Android Development] UpInTheAir:
deleted, quoted instead of editing above post
[Galaxy Tab 7.7 Android Development] schen:
Yes....but I am not going to pretent that everything is perfect when I find something is not. I was right all along when I told you init.d not working properly 30 pages ago. I also asked you to remove any frequency above 1600mhz because I know Samsung actually cheats by using the highest cpu frequency available for certain app like touch wiz, and some other benchmark apps like Quadrant for example. So there is a chance you could actually get stuck at 1800mhz if there is something wrong while the apps are running regardless of your max cpu freq seting. This is not a bug. It is done purposely by samsung. For now you can opt to include 100mhz but I still think it is useles. It will drain more battery versus 200.

So now do you believe me that your version 3.6 still has inconsistent scheduler setting? You always use cfq for internal SD and SIO for Ext SD? what is the advantage of this. Why not use cfq or sio for both?

Lastly I am happy now that I can use simple scripts in initD to set cpu, voltage, scheduler, read ahead cache etc. I dont use any third party apps for this. I told you before. This way I can avoid green tint ptoblem. In fact I have never experience any green tint problem as long as I dont use third party apps to set the cpu related stuff.

Will use 3.6 for a while now....
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Firstly, this kernel will NEVER be perfect and couldn't care less if it's not. As long as it's useable for the majority of users. Some things are limited by source code, ability, time and "care factor". I won't pander to the needs of those users that are demanding or appear rude.

You never learn.......:confused: 're-hash old posts (shake head).....init.d was reported to work by others with NO issues. stenny didn't even have the courtesy to tell me what he was actually trying to do or provide his scripts etc. I asked on multiple occasions. Without real feedback, no one can help or try replicate any issue ! Myself and others tested successfully with what information we were given (or at our disposal). :)

I actually agree about 100 MHz setting, that's why I don't recommend it........ but option there if user have preference or disagree. But don't tell me what to do about it ! If user doesn't like it, don't use it ;)

What are you using to check the scheduler settings for both internal and external ? I've only made one change to the scheduler, SIO.

Edit : Your wrong about Quadrant. I double checked. (On my device) Doesn't use CPU L0 freq (1600) unless user has it enabled by control app or script. The only time it's used is very briefly when app is loaded. SO Samsung aren't cheating as you describe. To see for yourself, use the cool tool app. Your device should be same. (edit : same goes for Antutu)

For example: My max CPU freq is set at 1400 MHz (L2) and the only time I see the 1600 MHz is during intial app loading. Test max is only 1400 MHz

Ref tint issue : As I have previously said that it

could

be firmware related. It has been reported with stock kernel, although I'm not 100% sure if that user was using any control app at the time..... (don't know why if on stock)

EDIT 2 : If the CPU got "stuck" @ 1800 MHz, it wouldn't be for long. Protection mechanisims are in place to prevent hardware damage. Please read Post #3 on thermal limitng. For example, performing benchmark set at 1800 will surely heat up CPU and limit performance (temp) to 800 MHz and when it cools below the threshold, allow freq above that again. If the CPU can't handle the freq or required voltage (lack of it etc), will freeze or cause reboot. This is also part of the hardware "protection". But, 1800 is actually stable on my device during normal day to day use, as I described, bench-marking is a different story. But because i feel it's just a waste of battery, and some user request (not demand), I removed it, but not because I felt it would damage or device. ;)
[Galaxy Tab 7.7 Android Development] schen:
with regard to your scheduler setting I check the corresponding file directly in sys/block/mmcblk*

With regard to init.d I said it work but not properly. That is two different thing. Stenny nail it prefectly by suggesting you to move Init.d execution at the bottom. Lets just leave it at that. Others might not use init.d at all. So they might not have a clue on this subject.

with regard to L0...in OUR JB not your ICS it behaves like I reported. Anytime you are In lock screen, or touch wiz or in quadrant L0 is being use as the max freq regardless of our setting. Please ask others using jb to see. But as long as it is not enable now I am cool.

I do use cooltool!
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I

Without DECENT feedback I or others can't help. His suggestion was far down the track...... Other VERY experienced users reported in thread and PM init.d working fine..... we can't mind read if users with issues won't/refuse to give all the facts, can we?

Thanks for testing the cool tool app, good to know. Would like other confirmation though from others. One user response isn't a good cross-section, is it?

Anyway, will have a TEST version 3.7.1 in the next half hour !

Edit: I'll take a look into the scheduler thing later, think easy to do
[Galaxy Tab 7.7 Android Development] schen:
Oke here is for others to try,

use trickster to limit max freq to 1400

use touch wiz

Install quadrant

Install cool toll

Run cooltool

Run quadrant

It will use L0 which in version 3.6 will be 1600, anytime you are inside touch wiz it will use 1600 too as max

Now just leave quadrant open but not actually running benchmark. The cpu will stay at 1600 until temp become hot then it will trottle back to 800 for few sec then back to 1600 again. This will keep going as long as you are in quadrant.

Remember though if you are using other launcher other than touch wiz, quadrant will use the max 1400 that we set. This behaviour is similar to samsung cheats on benchmark reportedly with newer device like gal s4. Please google the subject. It is widely discussed.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I/O scheduler

@ Shen,

Ref I/O scheduler

My ICS is different, so can you please give me the full path to "scheduler" for both your internal & external SdCard ?

My ICS 4.0.4 init.d script would be this :

#!/system/bin/sh
# Set IO scheduler to sio
echo "sio" > /sys/block/mmcblk0/queue/scheduler

I need the pathway for your JB 4.1.2 to set it in the initramfs sbin/SkyHigh.sh

Thanks
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Have a I9500 and know all about the "cheating". (edit: I9500) is nothing to do with what you described above though, they only cheat because they raise the thermal limit (not CPU freq) for benchmarking app situations, so the higher clock can be

sustained

.