yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Probably a way. In the mean time, take a look at this thread for SGS4 and see if it's applicable to your device....

Maybe with just a few minor adjustments, you can tweak from within your own ROM. Worth a look.

http://xdaforums.com/showthread.php...Modifications for i9500 (i9505 incompatible)!
[Galaxy Tab 7.7 Android Development] partola1:
Hi, how about NTFS filesystem support? I put via OTG usb flash drive 32gb formated as NTFS and tab can't recognize drive.

ROM is eRobot v1.0 and kernel is SkyHigh Kernel v0.7. May be i don't make some settings?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Firstly, does it work with your external sdcard formatted as NTFS ?

Secondly, Try USB OTG Helper app from Google Play and see if you have any luck mounting the USB stick.

Third, does it work with the stock kernel? You haven't said as I requested in OP...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Source : GitHub

I am now complying with the GPL and have managed to make the source/changes available for everyone to see.

Took a while, but eventually managed to upload and commit to GitHub.

Link now in OP

Now back to developing............ :D

Edit: having a few git issues......:eek:

Edit2: Have gitHub back and correct. Just learning the basics and now lost some dev time because of it............. off to bed, always tomorrow ;)

.
[Galaxy Tab 7.7 Android Development] theerachai:
my uv setting

erobot rom
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Sweet ! :D

Have you stress test each step to ensure stability?

You will need to lock the max frequency to that of each step, make sure it is NOT "set on boot" (during testing), so you can recover easily if device freeze or reboot occurs. ;)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
As a previous user didn't bother to give any further feedback on the NTFS, could someone using this kernel please check this:

1. Run Android Terminal Emulator app

2. su

3. Allow Superuser permission

4. lsmod

( the "l" is a lower case "L" )

What do you have? Please post a screenshot.

Also, check system/lib/modules for ntfs.ko

Cheers
[Galaxy Tab 7.7 Android Development] skycruzer:
Just happened to me... since UITA said not kernel related. I'm just wondering what ROM you're on? I'm using eRobot v1.1

Sory for off topic...
[Galaxy Tab 7.7 Android Development] sas_sas:
I have erobots rom v1.0. and your kernel v2.80

Lulzactiveq has been my favorite governor.. I/O scheduler issue is not clear for me but mostly select noob or sio.

I do not play games etc. My usage mostly is Intensive internet browsing and movie watching. and book reading. Screen brightness is around 60 %.

Performance wise I am happy, no lag etc..

Battery consumtion does not make me happy.. I wish I can reach up to 7- 8 hours..

I wonder under my usage preference What options may give the best battery performance.

If I let my 6800 wifi on at night it consumes 4-5 % otherwise 1% only.

I am not sure but 3G data is on (but no phone call) it does not consume much maybe 2-3% at night..

My setting is that, keep wifi during sleep is 'always'..
[Galaxy Tab 7.7 Android Development] UpInTheAir:
The kernel CPU is slightly UV and GPU already UV & UC. Watching media (mxplayer), lulzactiveq maintains CPU freq between 100-300 MHz (some other governors higher or erratic). The GPU idle @ 100 MHz / 900mV (stock 160 / 950), better scaling with added CPU & GPU steps, so there should be battery savings compared to stock.

MX player can adjust screen brightness, I turn it down (if you can handle a slightly darker image) and get great battery life.

I would suggest CPU 100-1400 MHz and limiting screen brightness, which consumes by far the most mW. I will attempt to slightly UV screen in a future kernel release to help out there.

You could also try experimenting with lulzactiveq governor tweaks. Use SetCPU or NSTools app to tweak governor. Edit: best not to touch any min screen off freq, default is set to step 13 (500 MHz), or otherwise risk SOD or lag on wake, you will still have deep sleep. I think L5 on stock kernel is same 500MHz, not near PC to check though, so could be wrong.

Below quote from droidphile thread, link in Post #3

2. Second Version:-

[ PARAMETERS ]

i) inc_cpu_load - In previous version, this was 'hard-coded' to 60. Now it's user-configurable. The frequency at which governor scales CPU up/down. Load < inc_cpu_load: cpu scaled down. Load >= inc_cpu_load: cpu scaled up

ii) pump_up_step - No of scale up steps when load >= inc_cpu_load

iii) pump_down_step - No of scale down steps when load < inc_cpu_load

iv) screen_off_min_step - Steps in frequency table to be used when screen-off. Example: If available freqs are 1600 1400 1200 1000 800 500 200 100 (L0 to L7) and screen_off_min_step=5 then 100,200 and 500 (L5 to L7) will be used during screen-off depending on the demand.

v) up_sample_time - same as initial version. (Allowed values 10,000 to 50,000)

vi) down_sample_time - same as older version. (Allowed values 10,000 to 100,000)​

[ SAMPLE TWEAKS ]

i) For battery:-

echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "2" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step

This tweak cause lulzactive gradually scale up CPU and rapidly scale down on low load.
[Galaxy Tab 7.7 Android Development] deani77:
After nearly a day usage. Most of the time surfing and playing kid game (my daughter love playing Subway Surfer and Temple Run 2)

100-1400mhz

Lulactive/Sio
[Galaxy Tab 7.7 Android Development] UpInTheAir:
For BIG kid too :)
[Galaxy Tab 7.7 Android Development] abima80:
im using standard rom without any mod,
[Galaxy Tab 7.7 Android Development] abima80:
Im trying to use lukzactiveq and sio and end up most of the time like my attachment. Change back to pegasusq nd cfq. Im using v2.70.
[Galaxy Tab 7.7 Android Development] abima80:
Supposedly the color not like that, the screen lack 1 based color, I do screen capture while it happen but then need to restart so that the screen have all the based color,
[Galaxy Tab 7.7 Android Development] UpInTheAir:
If I understand you correctly, somehow background changes to white from another colour??

governor/scheduler shouldn't have anything to do with it. There is nothing there that messes with screen colour/gamma etc.

What ROM and any other mods you using?

Anyone else?
[Galaxy Tab 7.7 Android Development] sas_sas:
I made the suggested tweaks for battery. Using now 50% brightness.

While playing BSplayer brigtness is 80-90%.

As result, I may say it extended the battery life.

Thanks a lot..
[Galaxy Tab 7.7 Android Development] UpInTheAir:
No problem :)

Edit: I think I'll tweak the lulzactiveq governor a little more towards battery/balanced (as "default"), rather than balanced in next release.

Still away at work ATM though.....
[Galaxy Tab 7.7 Android Development] abima80:
my tab using standard rom, download from sammobile and i use kernel version 2.70.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
You say "most of the time".

You will have to determine the steps you take to (reproduce the effect) make it happen, and what is different when it doesn't happen.

No apps? Screen filters, brightness control or LCD density control etc etc?

Can you restore your background from settings menu?

Is it just home screen or app drawer too?
[Galaxy Tab 7.7 Android Development] abima80:
i just change the setting inside NST tools, now its ok already when i change back to original kernal setting.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
User induced error. Just for info, what "setting" were you changing?

Glad it's fixed :)
[Galaxy Tab 7.7 Android Development] abima80:
I change io scheduler from cfq tp sio and governor from Pegasusq to lulzactiveq. Then it happen.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
As you said "most of the time". So with lulzactiveq & SIO set, when does it NOT?

Also, have you wiped the NSTools data and tried another app? SetCPU is free download in XDA (paid from market).

I cannot see how your issue is kernel related, no-one else has commented. The governor / scheduler has nothing to do with the screen, gamma etc etc.

You also never bothered to answer some questions I asked....What other apps, mods etc do you have installed that could affect screen, display, dpi, brightness etc? Can you restore your home screen background from device settings? Is there a problem when viewing the app drawer?

Users here would like to help, but aren't mind readers. ;)
[Galaxy Tab 7.7 Android Development] abima80:
Most of the time when I used lukzacrativeq and SIO it happen and when I use pegasusq and cfq it does not happen even once.

I donno how to wipe NST tools and I dont answer ur question becos im using standard rom download from sammobile without any mod just use your kernal.

Everything original just the kernal, but then using standard parameter for the kernal no problem,
[Galaxy Tab 7.7 Android Development] schen:
I experience the same problem as abima80. It only happened if you change the governor to something else using setcpu, voltage control or nstool. Tried it all. I even tried to change governor and scheduler using script manually. The problem with the screen also happened. And it happened since kernel v1.2. Tried all scheduler and governer combination with the same problem. SO I just left it untouch. The only thing I change is the minimum frequency from 100 to 500 using init.d script. All cpu control app disabled and it is steady. Looks like it is not user error. It is kernel problem not customizable or it is the problem with the custom governor and scheduler you included.

Right now I already rverted back to original kernel. The only thing I miss is the slower 3D graphics. Overclocked processor dont help to much for general use. This is the only feedback I can give you.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for reporting, but last line of your comment wasn't needed, was it ?!

If you still have 1.2, can you please retest? Don't forget to clear any CPU control app settings and scripts first.

I'll have a look through the change-log and see what differs between the two tomorrow. But hard to nail anything without device.

Ref. OC : I do see a slight difference with OC @ 1600. Apps load faster, and device boot faster too. If your CPU can handle it, UV your freq will offset any CPU OC 'drain'. Not just the GPU features your missing, the CPU has many added steps from stock for better scaling and potentially battery life.

Why not stick with 200-1400 on-demand, or does (changing) to that give issues too?

Edit: have you wiped all data from your control apps and tried with just one?

Edit 2: BTW, I will be re-introducing internal sdcard read ahead again. It will be set to 256. You will be able to change without issue. I will make the changes within kernel instead of initramfs. End of story.

Any others with this issue?
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Sorry, last time I will bother with the above unanswered questions....(3x now).

"Most of the time", that's the part I don't get. Then sometimes it's ok....

Wipe app data by going to device settings/applications/all/NSTools (or whatever)/clear data and reboot.
[Galaxy Tab 7.7 Android Development] schen:
Sorry....I will edit my last statement.

Dont get me wrong I love any extra speed on the cpu or the gpu for our not so speedy but unique looking tabs. But I have been strungling with customization from the beginning and watching my screen turns pale with color mixup kind of scary as I have no waranty and currently no 7.7 kind of tab from samsung or any manufacture yet. So I flash back to origi al while keeping my eye on ypur thread. once I can customize to my liking without any issue then I can probably use it. Sorry right now I cannot do more testing as my tab is in the middle of doing something rather important.

To be more precise on how I handle the screen issue last time were:

1. clear all 'set at boot' on all cpu control apps then use autostart manager to disable the apps from autostart. Let it boot with default setting and all going ok.

2. Clear data and uninstall all the control apps. The problem goes away.

EDIT: I think i notice the screen issue from v2.2. after I bug you with the init.d issue.
[Galaxy Tab 7.7 Android Development] abima80:
How do i restore the setting? i dont touch any screen or back ground setting,

no problem when viewing app drawer.

so far no problem occur since im not using that setting but i will try to wipe app data like u suggest and report back to you.
[Galaxy Tab 7.7 Android Development] abima80:
I done clean data like u suggest and when I reboot n run back nst tool, I cannot select any governor. Refer to my attachment.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
1. Open SuperSU app/settings/full unroot

2. Reboot into CWM recovery or DL mode

3. Re-flash SkyHigh kernel
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Shen / abima80

See if you get the problem by changing just the scheduler only. If ok, try changing governor only. Maybe we can determine if it's the governor, scheduler, or the 'switching' (any type) is the cause.

If you can please test the above first, then (edit: if needed) this week, I will compile a SkyHigh kernel for you two to test. It will just contain the stock governors/schedulers + other customizations. I might then have somewhere to start.

We will work from there. I will send a link by PM.
[Galaxy Tab 7.7 Android Development] abima80:
Done,

Still the same, no governor available.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Uninstall, wipe cache and dalvik in recovery, reboot and install from market.
[Galaxy Tab 7.7 Android Development] abima80:
Done, no governor available. List of governor still available in setcpu but not with nst tool.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
1. Open SuperSU app

2. Find NSTools

3. Long tap "forget"

4. Open NSTools

5. Grant su access when asked

If this doesn't work, I don't know
[Galaxy Tab 7.7 Android Development] abima80:
Done, no change, still the same.
[Galaxy Tab 7.7 Android Development] sas_sas:
Forget NSTools. Thou it is a good app but it does not work in my case too despite several tries. Other apps such as SetCpu and Kernel Tuner are fine and usable..

My case; Erobots rom v1.0 +SkyhighKernel v2.80.. Device is P6800..
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Hi SkyHigh users,

Back home for a few days, so will try and get a little development done on this project.

Have just UNsuccessfully UV Bus -25mV & -50mV (edit; display crashes), so unfortunately, this won't be included in any future release.

Now looking into light screen UV and touch sensitivity..... hopefully better luck here :)

Need more feedback and testing from users for the governor/scheduler switching bug.
[Galaxy Tab 7.7 Android Development] deani77:
Try trickster.... better option

https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
[Galaxy Tab 7.7 Android Development] edan1979:
nice... how can i miss the awesome tools
[Galaxy Tab 7.7 Android Development] UpInTheAir:
That's one I keep forgetting to tell users about. Have it installed, but rarely used because of SetCPU.

Thanks.
[Galaxy Tab 7.7 Android Development] abima80:
after all attempts to make governor available again fails, i encounter another problem, if i swich off tab, its really hard to get it on again, even we do restart function on power button.

last night i let the tab drain 100% and when it shutdown, i plugin the charger and i can see the battery indicator moving but it show no increment in battery level as it show normally and sometimes it makes me feel that the tab gone for good and suddenly it on by itself.

this morning i made my mind to reflash back the original rom that i download from sammobile.

S**t happen, 1st attempt using odin, fail, then i try to use cwm and manage to format from there but still fail, the last attempt i try again odin and successfully flash the rom.

the the tab restart and it go back to boot loop, the samsung logo keep on coming back, then last attempt i restart and hold button up and it go boot loader and i format again.

then i restart and wait for a very long time and pray, thank god the tab come back to life and now i just root the tab.

now all the problem solved, no problem to shut down n on back or restart the tab.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Did you read any of the previous suggestions regarding alternatives to NSTools?

Adviser to never discharge your battery completely. This can damage your battery.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v2.9.0

Any experienced SkyHigh Kernel user want to initial test 2.9.0 ??

First to volunteer in this thread will get PM link and changelog.

Offer is now CLOSED. Thanks :)
[Galaxy Tab 7.7 Android Development] deani77:
Never been an experienced user but can I tried your test kernel? :confused:
[Galaxy Tab 7.7 Android Development] UpInTheAir:
PM sent. Thanks.
[Galaxy Tab 7.7 Android Development] abima80:
i dont see trying another apps will help to solve problem of hard to switch on and restart that im facing after me trying steps that you suggested as i face the problem while performing steps that you suggested so i dont try.

about the battery, thats how i practice to make my battery long lasting and for me, my practice do prove itself.

ive been doing that since we use nickel cadmium battery and it helps to eliminate battery memory effect and my practice never give me chances to buy another battery until i trade my phone for a new one.

So hows ure v2.90 going? looking forward to try.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
"Hard to turn" on should have nothing to do with any advice I gave you..... The subsequent advice was to forget NSTools and use another app. :)

I suggest you research the subject regarding your battery type a little better......... it's your device to ruin though :D

2.9.0 will have no changes regarding any screen issue you might have. I haven't received any feedback from 2.7.0/2.8.0 as requested, so I have no idea even where to start.... "Most of the time" doesn't help with eliminating things. ;)

So if you have a screen issue, either;

1. Don't change governor/scheduler

2. Just turn display off and back on - easy way

3. Provide further testing to find out when it exactly occurs. I have asked in previous posts.... maybe we can find a cause and fix it.
[Galaxy Tab 7.7 Android Development] deani77:
When I use my Nexus S with ns tool, I always get that problem. Fix permission will fix that problem. But you need to fix permission using only CWM. Fix permission using TWRP will not fix that problem
[Galaxy Tab 7.7 Android Development] sir_wesley:
usb otg

hi guys, can you somebody help me with app who can drive usb otg on our p6800? I have original rooted rom DXMD3 4.1.2 and skyhigh kernel 2.7 with which should be possible use otg at least UpInTheAir did write it into working things. I tried many apps but none of them was working. actually I bought 2nd otg cable coz I thought it was broken. Still no success even with new one. Before on ICS it was working flawesly. When I plug in it doesnt even notify I something plug in.... does anybody have same issue? Or I manage to destroy 30pin connector in 7.7 .... but 7.7 is working when i plug in into computer as MTP. Thanks
[Galaxy Tab 7.7 Android Development] edan1979:
currently testing the 2.9 build... haven't see any problem yet.. even with the screen issue that previously being reported by others... device still working well but dont OC your device to 1800... not all device can accept it... it not that stable... testing around 5 combination of of govern+schedule... btw... my otg work fine...
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Don't really have many suggestion....

Try format USB sick to fat32, ntfs etc and try again

Try different USB stick (s)

Try paragon app to mount with ntfs

All else fails,...

FULL wipe (factory reset, format system, wipe dalvik & cache)

Flash stock firmware with Odin

Flash SkyHigh kernel.tar with Odin to root

Try mount again

Sorry, can't come up with anything else right now. Otherwise maybe hardware issue.
[Galaxy Tab 7.7 Android Development] sas_sas:
[MENTION=4244529]sir_wesley[/MENTION],

I have erobot's rom v1.0 and int lang pack v1.1 plus SkyhighKernel v2.80 and I have no problem OTG connected USB mem formatted Fat32..

What size is your Mem stick?
[Galaxy Tab 7.7 Android Development] sir_wesley:
usb otg

Thanks all of you guys for ideas. I have 32GB flash drive and FAT32. I tried unroot device than flash sky kernel again wipe cash and dalvik but no change. I have to make factory reset and flash original rom + sky kernel trough odin as UpInTheAir recommended, but cant do it now in work (no admin pwd), so evening I will let you know. Thanks :fingers-crossed:
[Galaxy Tab 7.7 Android Development] abima80:
When i use ics 4.0.4 last time, i faced this kind of problem as well, have to hold very long time to switch on the tab or if use restart function also it wont restart just shut down, then more worse if my tab battery flat also really hard to turn on as well. then when i flash new rom 4.1.2 all this problem gone, so how u explain this scenario?

about the battery practice somehow i feel comfortable about it and not even once my older phone have battery problem. so thats is not the main issue here.

i just share with you the problem that i face, if other users dont have this kind of problem then good for them but im just sharing with u guys the problem that i face instead taking a solution by reflash the rom and i share with you the problem that i face when i change the governor.

since that my tab is the only tab that kind of problem then i have to face it. The reason why i share my problem is for me to look for antoher alternative instead reflash using odin.

when first time i use that problematic combination of governor and IO thingy setting, i did face that color problem so i just restart the tab and its gone, then it becomes more frequent every time i go to home page.

i post up my problem just to know weather i missed some step of what. thanks for your advice on how to try to overcome that problem. i dont say that your kernal setting is bad, infact after reflash back the original rom i use back your kernal, in other way your kernal rocks.

so i think better for me to stick to what i have now, tired of reflash and setting all by the way that i use to set, actually its more on looks, nothing serius, just wanted the tab look alittle bit different from others.

well again thanks for the advice given. :good: to all