yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] schen:
#!/system/bin/sh

##################################################

## Voltage Control boot script by xan and nitr8 ##

##################################################

LOG_FILE=/data/volt_scheduler.log

rm -Rf $LOG_FILE

echo "Starting Insanity Volt Scheduler $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

echo "Sleeping for 5 seconds to workaround oc not setting properly on stock derivatve roms..."

sleep 5

echo "Ok lets start working"

echo "Set MIN Scaling Frequency" | tee -a $LOG_FILE;

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

echo ""

echo "---------------"

echo "Set MAX Scaling Frequency" | tee -a $LOG_FILE;

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

echo ""

echo "---------------"

echo "Set Scheduler for stl, bml and mmc" | tee -a $LOG_FILE;

for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk* /sys/block/mtdblock* ; do

echo "cfq" > $i/queue/scheduler;

echo "$i/queue/scheduler";

done;

echo "---------------";

echo "Set governor" | tee -a $LOG_FILE;

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

echo ""

echo "---------------"

#UV_BEGIN#

echo "Set UV" | tee -a $LOG_FILE;

echo "1375 1350 1325 1275 1225 1175 1125 1100 1050 1000 975 950 950 950 925 925 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo ""

echo "---------------"

#UV_END#

This is my init.d script to set the cpu and scheduler stuff so that both internal and ext sd use the same scheduler.

For internal it is mmcblk0 and for ext it is mmcblk1
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.7.1 TEST

TEST VERSION ONLY

>> v3.7.1 TEST <<

* Implemented kenel to report usb trickle charge (currently just reports discharging)

Those with unmoddified systemUI.apk (no USB battery charging animation mod), should now have the battery charging icon when connected by USB (no red X)

gitHub source change : https://github.com/UpInTheAir/P6800_JB_SkyHigh_Kernel/commit/3aa5d6bce467d63b0453b53e064a11d2f3d5dbc2

* Force USB charging souce as AC

gitHub source change : https://github.com/UpInTheAir/P6800_JB_SkyHigh_Kernel/commit/6edc748ff1f4dd56ae3b08681578ffa2cd55f1c4

AC max = 1500mA (1.5A)

USB max = AC using same circuitry (Limited by charging source max output

up to

1500mA)

You can test the source change by viewing /sys/class/power_supply/battery/batt_charging_source

0 = battery

1 = USB

2 = AC

Real life testing :

- Can be done by plugging tab into a wall charging source with USB output that was previously recognised as USB and kernel limited to max 450 mA (SkyHigh 650).

- Also can test using USB 3.0 port which outputs approx 1.0A

I have none of the above to test, so testing and feedback will be appreciated. Don't forget, as much detail as possible. Thanks !

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks, just confirmed your JB pathway is not diifferent to mine. After study your script, I understand your

now. Just means all startings with that.

I don't know why CFQ is set for int and SIO is set for ext. My P6810 is ok, but I will take a look at the JB source changes when I get a chance, until then, I can just echo "sio" for both. edit : if user wishes to change, can use app or init.d script app :D
[Galaxy Tab 7.7 Android Development] B4R7H:
just load v3.7.1 now the recharge icon working also the charging now showing on lock screen...btw v3.7.0 pretty stable...faster responsive no lag...everything just smooth on 3.7.0...

I will give feedback about 3.7.1 after ur kernel get stable on my device...thanks again UITA:good::laugh:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for testing :thumbup:

Hopefully the tab will charge (accept input) from high power USB source at MAX supply current (up to 1.5A), instead of 450 mA.

Look forward to hearing from you or other users regarding this. :)
[Galaxy Tab 7.7 Android Development] lomniom:
No problem anymore with power banks! USB charging fine on USB 2.0 and 3.0.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I'm not 100% sure the meaning of "no problem". Can you please be more specific ?

Can you please confirm that there is a measured increase in charging rate with the USB 3.0 port (up to 1.0A) and power bank (up to max 1.5A) from v3.7.0 to v3.7.1 ?

To really check, there are a number of free "charging current" apps available. I just use the cool tool app and set up a "custom label" in advanced section with the pathway :

/sys/class/power_supply/battery/current_now

In labels section, go to "advanced tuning and give your custom label a name, and then enable it in overlay in "labels" section.

Some of the free apps require manually refresh, but setting up the cool tool puts all things in one place and update is "live".

Thanks :)

Edit: Don't forget, the charging rate displayed is not the actual input current. Display = max input current (kernel & source limited) minus current drawn by the tab.

Hopefully you can see a difference between kernels. :fingers-crossed:

I do suggest to disable the app it when not in use, it does use a tiny little bit of memory and CPU to keep the overlay update. Nice for testing though.
[Galaxy Tab 7.7 Android Development] sas_sas:
I fully agree....

Ths UITA...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks, still room for improvement. Will just keep working at it bit by bit. Want to lighten the kernel with Aroma installer option to for user needed modules (maybe some tweaks too), but that's on hold for now. Can't do everything at once. ;)
[Galaxy Tab 7.7 Android Development] sas_sas:
Despide having read many explanation regarding governers and schedulers I am ashamed to tell that it is hard for me to choose the correct ones.

I kindly request here (I am sure it will enlighten to many persons) if someone can give the order of governors and schedulers (used in Skyhigh kernel only )in battery consumtion and performance wise...

Such as;

Govs from less performance to more;

powersave

conservative

....

.....

Govs from less battery cons to more

.....

.....

Schedulers the same manner...

Ths a Lot lot to whom makes this...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I have already given my observed opinion in Post #3 "recommendations"....

Many other governors haven't been tuned to our device yet and are erratic in freq scaling etc or possibly aren't suitable.......

Edit: Post #3 also has a link to droidphile thread explaining a lot, and if you search there hard enough, will find his informed opinion on some governors and schedulers (amongst other things)

This is why I have a Post #3 FAQ ;)

Edit 2 : io schedulers seem to be quite subjective. You just need to test a few combo out for your own use. Playing games is different to multi-tasking etc. Benchmarking may be different to real life use.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.8.0 has been compiled for the last day and ready.........

Still waiting previous requested feedback on v3.7.1 TEST VERSION

I (WE) can't progress unless we know what works and what doesn't ;)

Appreciate anyone who can spare the time to check, please do so. THANKS
[Galaxy Tab 7.7 Android Development] A-wen:
I need old version like V3.5.0~~

because I want 1.8Ghz :p

but I can't find it~~ :crying:

anyone have a backup? please send it to me~~

Thanks~~
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Sorry,

This thread will not be supporting any previous SkyHigh kernel versions. Only the latest (stable) release and test versions.

I can't replicate any JB bugs that come up, so we all need to be on the "same page". :)
[Galaxy Tab 7.7 Android Development] stenny:
Original wall charger

Output = 2A

Charging current = 13xxmA ~ 19xxmA

Original Sony car charger

Output = 1.2A

Charging current = 8xxmA ~ 11xxmA

PC USB 2.0

Output = 500mA

Charging current = 3xxmA ~ 6xxmA
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Did the Sony charger previously charge at a lower rate on v3.7.0 or stock ?

We are looking for those charging sources that would only charge at USB 2.0 rate, but now charge at max source output (up to AC rate) with v3.7.1

Cheers :)
[Galaxy Tab 7.7 Android Development] stenny:
Yes, last time it was around 5xxmA ~ 8xxmA

I guess it work properly with v. 3.70-test. And for the original wall charger, before 3.70 it most of the time charging at 6xxmA ~ 10xxmA, very less time can go up to 13xxmA.

Hope this help. Again, thanks for building this great kernel for us.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for your testing and feedback.

Not quite conclusive with the Sony. Yes, it's faster on 3.7.1 , but should be lower than 600-1000. My guess it's already detected as AC, and already allows up to 1.2A

Just need someone to test on a USB 3.0 .

Also, do the users with power banks have a HUGE charge rate increase from 3.7.0 to 3.7.1 and what were your rate before and after?

Cheers :)
[Galaxy Tab 7.7 Android Development] partola1:
Hi, UITA

Couple refs from me.

1. Charging from AC seems a bit slowly on version 3.7.1 for me.

2. GPS not working on 3.7.1 completely. No one sattelite not found. After reverting to 3.7.0 without any wipes tab founfd 16 sattelites very fast.

May be another users can confirm this?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
1. With regard to what exactly? More details, hardware and method of testing etc

2. Does the GPS actually power up ? I haven't touched anything here, maybe bad flash or bad compile ?
[Galaxy Tab 7.7 Android Development] partola1:
1. This is not measured, only subjective observation, sorry. Slowly compare to 3.7.0 and below.

2. Yes, GPS was power up. I try on/off/on - not results. 3.7.0 instead working very fine with GPS. We need messages from another users, may be problem isn't common and only for me...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
1. This is a development thread, so you'll need to please post further info. I know it will take some of your time, but it's the only way to help yourself. Without it, any perceived issue may not get fixed.

What is the charger source and V A capacity ?

Have you tried other sources, and what are their ratings ?

Is your device off or on ?

Like stenny did, please try and get some hard data using some approx (not exact) current measuring app. I briefly explained about cool tool app in previous posts. There are other free current apps in Google Play, some may not work, others may not show live data or need manually refresh. stenny data showed normal behaviour for standard USB 2.0 & AC charging.

2. Did you try reflash v3.7.1 ?

As you suggest, need others to check GPS
[Galaxy Tab 7.7 Android Development] stenny:
For me, GPS working properly with v3.7.1. I get in locked within 10sec even indoor. Try using FasterGPS from market.
[Galaxy Tab 7.7 Android Development] lomniom:
Me too.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
OK, having some major issues with my build environment, and wasted a lot of time trying to get it up and running again. Still not up :crying:

Anyway, my build environment could be a start from scratch job, but that will have to wait.

Real life is taking priority again, so I must stop development for the next couple months.

Please enjoy v3.7.0. :)

Ref: TEST v3.7.1. Still waiting on that final feedback about USB 3.0 and USB chargers charging rate. Although have v3.8.0 ready, not going to officially release it due to lack of required feedback on v3.7.1. No time to worry about that now. :cool:
[Galaxy Tab 7.7 Android Development] lomniom:
Charging rate is OK for me with 3.7.1 using USB 3.0, faster than USB 2.0. but I'm not too technical to test it with proper apps. I just can confirm that it's faster to go from around 50% to 100% charged.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for that.

I will try and post v3.8.0 tonight or before I leave tomorrow. v3.8.0 is v3.7.1 plus some Thunderbolt tweaks.

I'll also include download for v3.7.1 as we know it works fine.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.8.0 update

>> v3.8.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.7.0 -> v3.8.0

* Implemented kernel to report USB trickle charge (previously just reports discharging).

- Those devices without moddified SystemUI.apk will now show battery charging animation whilst on USB power source

* Force USB charging souce to be detected as AC

- faster USB charge using same circuitry

- limited by:

1. charging source max output

2. kernel - up to max 1500 mA (same is actual AC)​

* Thunderbolt scheduler IO Tweaks [pikachu01]

* Update ZZMoove governor to 0.7d [zanezam]

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

TO-DO

* Update thread Post #3

++ v3.7.1 will be included in the download section for those having any issues and need to revert - THANKS FOR THOSE TESTING v3.7.1 & FEEDBACK !! ++

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] sas_sas:
Our respective Kernel developer UITA surprised us again and released the new version 3.8.0. at the same day after declaring 'to stop development and need some personal life etc' .

Thanks mate for your efforts and kidings...

I think you dislike to be pressured...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks, but will be working away for a while, so will be a couple months before I can continue. Besides, need new PC and build environment to setup when I return home. :)

There are a few unfinished mods still for this kernel, such as GPU control and Aroma installer for some various features and modules etc. Next time though ;)
[Galaxy Tab 7.7 Android Development] lomniom:
I'm staying with 3.7.1 as Thunderbolt tweaks are too agressive for the battery.
[Galaxy Tab 7.7 Android Development] schen:
Had spare time today, decided to load 3.8, perform a clean boot and notice that scheduler for inteernal mmcblk0 is still cfq, mmcblk1 is SIO. Someyhing might change it back to cfq I guess. Doesnt matter for me though as I always have to change cpu freq, governor, scheduler, cpu voltage and read a head cache all with one init.d script file.
[Galaxy Tab 7.7 Android Development] deani77:
I was on v3.7 of your kernel. What I noticed was cpu frequency not fully utilizing maximum frequency even though I'm using ondemand governor.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Governors only scale to what is actually needed.....

Don't support legacy versions, so please only report on the latest 3.8.0 or 3.7.1. ;)

On-demand hasn't been touched, so should be ok. Have you cleared all CPU control app defaults, deleted scripts and rebooted?

Any other user reports after following said advice?

Edit: maybe also clear data from the CPU spy app (rather than reset)
[Galaxy Tab 7.7 Android Development] frogeed79:
hi

Randomly moderm crash from cfq schedul....row seem ok....v3.80...just to report....sorry my bad english
[Galaxy Tab 7.7 Android Development] deani77:
Thanks for the reply. Will try out your latest kernel and see how it goes...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Modem nothing to do with kernel
[Galaxy Tab 7.7 Android Development] deani77:
Get almost same result with latest kernel. I was on Ondemand with 200-1600mhz
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I don't really know. As I said, on-demand remains untouched.

Try using a resource intensive app (any CPU benchmark app will do) to load the CPU's and see what actual "live" values are with cool tool app.
[Galaxy Tab 7.7 Android Development] frogeed79:
Ok.....thanks
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Could someone please post your v3.8.0 init.rc for me to look at. May lead to nothing, but just have an idea about something......

I'm away for quite a long time and no access to my PC.

Thanks
[Galaxy Tab 7.7 Android Development] sas_sas:
Here it is,
[Galaxy Tab 7.7 Android Development] lomniom:
Here it is. Hope it helps.
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
I'm having some problems when using my tab connected to my hdtv using the samsung hdtv adapter. Screen is unresponsive and a little bit laggy when connected to the tv. Currently using stock 4.1.2 and this kernel.

••••• | Sent from GT-P6800 using Tapatalk 4 | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Please flash stock kernel and report back your results.

Edit: ensure you using SkyHigh kernel in "default" config with no other "tweaks", scripts, or control type apps

Anyone else with this issue using under same circumstances? Please test with SkyHigh and stock kernels. Thanks.
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
No other mods done . I Just flashed the stock one and it runs perfectly.

••••• | Sent from GT-P6800 using Tapatalk 4 | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Unfortunately, we will need other P6800 users to give feedback on this. Sorry, I can't think of anything right now.

Edit: please try v3.7.1....
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
No problem bro. I'm Just letting you know that this occurs.

••••• | Sent from GT-P6800 using Tapatalk 4 | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Please check v3.7.1 first.

I am sure it was reported to be working ok in earlier versions. Maybe by PM...

If you still have no luck, could you please spare the time to try some legacy kernel versions and test to see if any work for you? If any do, maybe we can narrow down which version and subsequent changes made cause a problem?

Please let me know, I can PM you with the download links.
[Galaxy Tab 7.7 Android Development] lomniom:
No problem for me. 3.8.0 pegasusq.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks.

Very strange though. Maybe it's the adapter type?
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
What adapter type?

••••• | Sent from GT-P6800 using Tapatalk 4 | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
MHL - HDMI adapter
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
It might be the port of my tv which uses the new Mobile High Definition Link (MHL) that does not requires external charger when connected. Still the 7.7 is not MHL ready device so it does require power thru its own charger. I will try this one on my plasma which uses non MHL hdmi ports.

••••• | Sent from GT-P6800 using Tapatalk 4 | •••••
[Galaxy Tab 7.7 Android Development] lomniom:
I use this one, and never had problem with any version of this kernel. Of course adaptor should be connected to power supply.

http://www.expansys.com/samsung-hdm...ible-with-first-gentab-and-tab-2-7-10-219890/
[Galaxy Tab 7.7 Android Development] Fulaeetoy:
I used that one too. Stock beta kernel provided by UITS runs fine on my tab. Still waiting for the links of v3.71 to troubleshoot more.

••••• | Sent from GT-P6800 using Tapatalk 4 | •••••
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v3.7.1 is in Post #2 Download section. :)

The others as per PM when I get a chance
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Working CWM officially released legacy versions now in Post #2 for troubleshooting purposes only. :)

For any users wishing to flash for reasons other than I stated above, they are unsupported in this thread. All users need to "be on the same page" to help each other out with debugging and troubleshooting. :)

Change-logs found by searching the thread. I'll add them to Post #2 eventually.... ;)
[Galaxy Tab 7.7 Android Development] lomniom:
Dear UITA, the WIFI connection is sometimes blocked (tablet still connected to the wifi modem, but no internet connection) with the kernel 3.7, 3.71 and 3.8. If disable and re-enable wifi via status bar of the tablet, the internet connection works again. Could you troubleshoot this please?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
I'm sorry, I'm still away for a long time and unable to take a look at things easily/properly until I return.

The "sometimes" (intermittent) problems are always hard to sort out, particularly when I don't have Android version or device model. May need others to comment.

Make sure you're not using any build.prop "power saving tweaks" using deeper sleep, or anything else (init.d script, mods, tweaks or related app)

If not, please try stock kernel for a while and some other legacy versions to compare.

It could also be a ROM or router issue....
[Galaxy Tab 7.7 Android Development] schen:
Has been playing with 3.5 and 3.6 for a while now. Just would like to share that if your tab can handle these voltage:

1800mhz: 1300 mV

1700mhz: 1275 mV

1600mhz: 1275 mV

1500mhz: 1250 mV

1400mhz: 1225 mV

1300mhz: 1200 mV

1200mhz: 1150 mV

1100mhz: 1100 mV

1000mhz: 1050 mV

900mhz: 1000 mV

800mhz: 975 mV

700mhz: 950 mV

600mhz: 925 mV

500mhz: 900 mV

400mhz: 900 mV

300mhz: 875 mV

200mhz: 875 mV

100mhz: 875 mV

with min and max frequency 300mhz to 1600 or 1800mhz (depends on which version you used)

Scheduler: cfq

Governor: pegasusq

Frequency for responsiveness: 600mhz

then even the 1800 v 3.5 could be usable. Fyi I have 256 and 1024 read ahead cahe for int and ext sd.

Running extensive stability test using antutu benchmark. It passed without crashing or reboot. That means ot can run a 10-20 minutes at 1800 with occasional thermal throttle with no problem. No overheat with undervoltage seting.

Benchmark test with antutu I notice only one thermal throttle occured and can score quite high 14500s. I guess lower voltage help preventing cpu temp reaching 65degreeC. Less thermal throttle. Thus allowing better score.

Extreme uv also means batt performance actually better than stock kernel despite enablin 1600 or 1800 freq.Tab actually run below 40 on normal use reaching 60 or cpu extensive games. Gpu intensive games no problem at all.

Please keep in mind that your tab may not be able to handle these extreme uv. Mine can. so try it if you like but be carefull. If you are already with 3.7 or 3.8 you can still try. I stay with 3.6 because I think charging voltage booster increase batt temp when charging which is not good long term wise for batt life.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for sharing your settings.

BTW, I haven't "boosted" any charging voltage.....

I only make USB charging recognised as AC. This will then charge up to max AC rate (unchanged @ max 1500mA).

Meaning;

1. You can charge up to 900mA using a USB3.0 source

2. You can charge up to 1500mA using a USB wall type charger up to 1500mA

3. (Edit) You can charge up to 1500mA using a power bank

- All were previously limited to USB2.0 rate 450mA

- The device will only pull what the source can supply, up to an unchanged max AC rate of 1500mA

++ You cannot damage your device or battery. Because you are using the same circuitry and device will only pull current from charging source up to stock max A.C.(1500mA). ++
[Galaxy Tab 7.7 Android Development] schen:
Good to hear that. Maybe I will update later as I dont usually update often. I think I only flash 4 version of your kernel from the beginning.