yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] UpInTheAir:
UKM doesn't offer different options. You would need to write a script to pull, read, determine asv group before synapse UCI is loaded and then set limitations. Not needed if frequency and voltage controls are in place though :p

I can only test on my own device asv 5. I don't have any issues using lowest frequencies (although I do notice very slight GPU sluggishness from 100 MHz). I've just woken up, but I only unlocked the A7 cores to 200 MHz (100). I can't remember exactly why I didn't lower A15 cores past stock (instability / sluggishness?). OK, just starting to wake up and get some sense (my head is in HMP mode :) .............. UC the big cores is really a waste as 5420 uses IKS (in-kernel-switching) and you need to adjust the swtich frequency level between A15/A7. It caused issues for me trying to implement something, so I didn''t bother with control for Max LITTLE cores or MIN big cores CPU freq control.

Instabilities would just lead to data loss and corruption and not affect hardware.

For those wondering, there are 15 asv_groups. 0-14. Double didgets is rare, but not unheard of, lucky bArSt*rD$

With my kernels, I try to build a "one size fits all" with options for users that desire and devices capable. That's why is so stable.

Sorry, I haven't play around HP etc. Just don't have time to devote to it. I just keep things relatively simple. :)

Edit: I must find time to put the asv_group info in my kernel thread Post #3. Doesn't make users read it though. ....and stop all those useless questions "what is best settings for. ...."

I'm going to update and adapt some code and clean out my synapse files for Tab S. Spent some time on my Note Edge and it's looking good, but, can't release kernel until Sammy releases newer source (no carrier connectivity)............

---------- Post added at 06:14 AM ---------- Previous post was at 06:13 AM ----------

How can you be confused. Didn't bother to read my two posts above? I even put it into maths. ...
[Galaxy Tab S Original Android Development] hurray:
[MENTION=4405529]nvertigo67[/MENTION]: the test kernel runs very good at my T800. I think it would even work with a cpu frequency of 2000MHz (as with the sky high kernel).

I run a few benchmarks and it was always stable and of course faster than stock. :thumbup:
[Galaxy Tab S Original Android Development] :
I'm sorry to hear 'bout too old sources for edge. I like the specs of your toy - thinking the same way, you think of people having double digit asv groups... ;)

I don't plan to mess with A15 cores. I found the mali gpu was able of 533 and enabled that. I started playing with kernel source to lower battery usage - and with Test kernel it seems to be minimal lower, but I havn't used it long enough to tell.

When it comes to real OC/UV and an interface to control I would always opt for SkyHigh - why shoild I do something that has been done and has been done better then I would do?

As for my UKM idea: I know that are "only" scripts. And I know you did nearly the same with your flashable kernel zip. As I have written a couple of weeks ago, if adjusting your scripts to use bb from cm doesn'nt work cleanly my next option is to put the bb your scripts are using somewhere outside the paths and making your scripts using them. That's what UKM.zip does. So I think, If I mess with each command executing line in your scripts, it is nearly no (ha, ha, ha...) additional effort to write a device directory of scripts like the ones in standard UKM.zip.

Back to roms kernel:

At the moment I see two options considering the UC is safe for everyone. Putting a cpu 100(200) to 1900 MHZ cpu and 100 to 480 MHz gpu kernel in the rom and providing addionally a kernel with 533 MHz enabled. - I don't like that, as I have never liked having around more then the rom kernel. The other option would be - depending on the test ressults of as much user as possble - to use the gpu 533 MHz enabled kernel as standard for the rom.

I would like to use your commits

ARM: implement KERNEL_MODE_NEON [halaszk]

arch/arm: compile with full -mfpu=neon-vfpv4 & hard float

Compile stock and Samsung MTPs together [AndreiLux]

if you don't mind.

OT: writing the asv group information in your thread is a good idea - if you find a way to make users read it, please, please, please let me know... ;)
[Galaxy Tab S Original Android Development] UpInTheAir:
Go for it mate. :) Use whatever you need.

Edit: personally i feel 177-533 would be ok at stock voltages. There would be very very few devices that should have issues. 100 might be OK, but sluggishness could be less pronounced in CM than TW (and depending on user eye). Thresholds can be tweaked though. .

Some take offense when directed there or Q&A. I just send them on their merry way. Yes, back to work on the Christmas kernel :) ho ho ho
[Galaxy Tab S Original Android Development] Offica:
Just tried a couple of ROMs.. CM 11 has been the best by far. Thanks keep up the good work:good:
[Galaxy Tab S Original Android Development] :
New test kernel

Thank you. Have taken some more commits.

Now, my secret plan ( ;) )to make a Christmas build is leaked I'm very happy about your feelings toward 533. I hope user tests will prove that is right.

My todays work:

lib: memcopy & string use glibc version [Miao Xie] UpInTheAir

add a runtime dependency checker [AndreiLux] UpInTheAir

CHROMIUM: clocksource: allow clocksources to be selected earlier during boot [Andrew Bresticker] UpInTheAir

gpu: ion: system_heap: add support for 2MB allocations [Mitchel Humpherys] UpInTheAir

arch/arm: compile with full -mfpu=neon-vfpv4 & hard float UpInTheAir

ARM: implement KERNEL_MODE_NEON [halaszk] UpInTheAir

Compile stock and Samsung MTPs together [AndreiLux] UpInTheAir

block: deadline: allow 0ms deadline latency, increase the read speed [tuxiaobing] UpInTheAir

block: deadline: Optimize for non-rotational [myfluxi] UpInTheAir

Thanx again for letting me use your commits. Especially aggregating the original NEON_KERNEL_MODE patches into one and make them work with our source base must have been a hell of work (I have looked at the 3 or 4 patches from Reioux some days ago...).

Further more I have fiddeld with the treshholds and belive there is no noticeable lag anymore:

mali gpu: lower treshold for 177 to 30 and for 266 to 50 to prevent lagging after idle. Nvertigo

Freqs itself are unchanged: cpu 100 to 1900 MHz; gpu 100 to 533 MHz. Again: Please test everything with different governours and schedulers (though I'm a real deadline fan, I feel taht cfq runs best on our device). Also test mtp with win (have no win handy).

Happy testing.
[Galaxy Tab S Original Android Development] reubenskelly1992:
Does this mean it a supports art! Awesome work! I will will try the deadline! Does it make any difference to battery life compared to interactive?
[Galaxy Tab S Original Android Development] UpInTheAir:
No problem. Most of my kernel patches are commited "clean", but in between took a lot of testing. Many I have not annotated anything additional in commit notes, sometimes I should have done though. I'm hopeless with git............

I'll have to get you out of the CPU "100 MHz" habit :) . There is no such 'actual' minimum ..............

https://raw.githubusercontent.com/UpInTheAir/Galaxy-Tab-S-Kernel/SkyHigh/arch/arm/mach-exynos/include/mach/asv-exynos5420.h

For real A7 core frequencies need to be doubled for correct output reading. ie.

(A7)

650 MHz ~ 1300 MHz

600 MHz ~ 1200 MHz

550 MHz ~ 1100 MHz

v

v

v

100 MHz ~ 200 MHz

A lot of (all I know of) apps don't ake this into account (CPUspy app for one), so output readings are incorrect because they don't take into account the need to double all A7 core freq (650 and below). The A15 cores min_support_idx_CA15 = L16; (800 MHz) where the kernel switches A7 (650~1300) > A15 (800).

On this note, I have implemented "time in state" for big.LITTLE into synapse app (and GPU) and showing the correct output states for A15 2100-800 and A7 1300-200 MHz for my SkyHigh kernel. Was simple in the end, but took a lot of time to figure it out. ;)
[Galaxy Tab S Original Android Development] :
Thanx for your patience wit my "habbit". To get this straight (btw: I took the readings from Settings->Performance->CPU; cm build in): The stock 250 MHZ are 500 MHz and SkyHighs 100 MHz are 200 MHz? And sammy has implemented it this way to avoid having overlaping freqs between A7 and A15 (sound like a statement, but is a question)?

I understand why all apps (including cm settings get this wrong, 'cause even the sys interface says 100 MHz... I really belive that it was difficult to figure out...

Your commits are nice and clean and fal in place like butter (phrase? English is not my native language: ;) ). I only get always warnongs about permissions (sammy has 0755 for most *\.[ch] ; for updating to 3.4.105 from kernel.org I changed that to the "normal" 0644 perms), on ssome hunks I get trailing whitespace warnings - both doesn't matter 'cause git warns, but applys.

Do you have an idea how to get rid of the oscilating between 200 (sysfs 100) and 400 (sysfs 200) MHz? Can it be tuned via governour settings? Or is this addressed by sched: LOAD_FREQ (4*HZ+122) avoids loadavg Moire [halaszk]?

I for my part I love git: in the beginning it was a difficult relationship. I started using git with vdr (VDR - The Video Disk Recorder (site is in english) and hated it. I was so complecated - today I would say it's powerfull. But from complecated to powerfull it had taken some time. If I hadn't fallen in love to git, when started my very first home builds of aokp two years ago, I think I wouldn't write this posting right now...

BTW: have a clone of your git on my disk - but not in the same dir I have the chagallwifi cm kernel sources. So how to get a commit in cm kernel sources keeping it's references, authorship and history (without fetching a branch temporary and cherrypicking FETCH-HEAD; which would be easier, but also more expensive if working over 3g)?

(cd ../sh; git format-patch -1 --stdout <put short hash of desired commit here>)|git am

Enough OT. (just realized I hadn't pushed yesterday night - did so know. Branch my-work is 20141220-b now.)

Thanx for your brilliant work on chagalls kernel, your patience and - most important for me personally - for your lessons in understanding exynos kernel (the ones in pm and postings as well as the ones I got while reading your sources)!!!

Today I will try to compile with 4.8 (not really an advatage - I think - but nice practice and usefull as prework for cm-12.0.

Question: is there a sysfs interface to know if A7 or

---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------

On my n10 deadline feels a bit faster and less battery intensive than cfq - on our device to me it feels cfq is a bit faster than deadline with no difference in battery. I don't give am**** on benchmarks, so this is just my experience and I may be wrong.

If you ask about art runtime environment: that's not about kernel, it's about rom. ART is included in cm but not official supported. So I don't use it. But you can try: Settings->Developer->Runtime (from memory).
[Galaxy Tab S Original Android Development] UpInTheAir:
All default frequencies in my kernel are stock values. Use has synapse options to UC/OC etc etc.

I have that patch in my kernel and also adjusted thresholds, so maybe take a look at my earlier commits. Also depends on what is running on background un/loading CPU using cycles etc. Every user device is setup different, let alone the difference between TW and CM.

There is no sysfs that I'm aware of. The real frequency needs to be calculated and output.

I'm releasing a new kernel late tonight. The ramdisk synapse has a few small changes here and there. It should be nice and clean now. You can see under the CPU tab how A7 and A15 are calculated for display.

Go to go, your welcome for the help

Edit: just did a tyre and wheel damage on the truck. Waiting for insurance. ...

Thanks for the git tips.
[Galaxy Tab S Original Android Development] :
Sorry for your car damage. I hope you have an old cars with a spare wheel, and not on of this new ones just with this broken tire spray.

I don't find commits with adjustable thresholds (other then for mali) - or do you set them in ramdisk?

The above commit (or better : the two of them) make oscolating a bit slower - but it's still there.

Do you have a pointer to documentation for the sammy enhanced interactive? [single|multi]_[enter|exit]_load i.e.? Seems I'm to dummy to google the right phrases...
[Galaxy Tab S Original Android Development] UpInTheAir:
Sorry for the "wild goose chase", that was for GPU, not CPU. Setting CPU to 200 MHz will not idle there as much as 500 MHz (stock) due to any small load fluctuation. 100 MHz could actually be less power efficient than higher min freq due to taking longer to complete a given task, so is possible to actually use more battery. I haven't really done any calculations or proper testing though.

OT: newish car. Big alloy wheel and tyre ahhhhhhhhhhh
[Galaxy Tab S Original Android Development] yeiyei0891:
Sorry for the question... Is it this ROM smoother than stock ROM? My nexus 5 is smoother that the fu... stock rom. Thanks
[Galaxy Tab S Original Android Development] Offica:
Thanks for working on a kernel for us, working goid sofar
[Galaxy Tab S Original Android Development] hurray:
Wow, that's cool! Now we have something to play with and test a little bit around. :D

That's something a liked with the sky high kernels. :)

Edit: my first test did not work :)

echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Galaxy Tab S Original Android Development] Sudbury78:
Fellas any work around to get the Samsung side sync or a similar spp to work? Loved using my tablet to use my note 4 remotely? Thx
[Galaxy Tab S Original Android Development] :
Of course not:

/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1900000 1800000 1700000 1600000 1500000 1400000 1300000 1200000 1100000 1000000 900000 800000 650000 600000 550000 500000 450000 400000 350000 300000 200000 100000

Read my lips: This is not an oc kernel. ;)

---------- Post added at 08:41 AM ---------- Previous post was at 08:31 AM ----------

For my it is quick enough to search for battery savings - and not for OC (sorry, [MENTION=3099085]hurray[/MENTION], but I could not resist... ;) )

I think it's snappy. Sammy deploated by hand with titanium, nova launcher and tw deinstalled and SkyHigh kernel is also ok (but for me slower then cm11).

---------- Post added at 09:11 AM ---------- Previous post was at 08:41 AM ----------

My plan has been to make the Christmas build today, but - there is this f#@!ing BUT again - I have an unsolved issue: http://xdaforums.com/showpost.php?p=57656003&postcount=30

Menu does not work. If you use capacitive keys and confogure MENU on a key (no matter if on short press or long press or dobble press on home) it just doesn't work. Keys work: if I map "open camera" on whatever, it opens up - but menu just doesn' work.

I works on my homebuilds for opo and s3. I have done a fast dirty build from a repo sync yesterday - to no advance. I have done a build with reintroducing the broken onscreen navbar - to no advance, either.

There is nothing in logcat - nothing, no warning, no error, no nothing (I know the last one is logicaly wrong). And I found nothing with google... :( So if someone has an idea or a pointer or something let me know.

Today I have no time. So my plan - if no one can enlighten me to look in the right place to fix this - is to publish a new build late today, or tomorrow early evening.

Back to kernels: I'm quite happy with the last testkeenel when setting min to 400 MHz (200 MHz in Settings->Performance->CPU). What do you think? For me the kernel from 21th was the most powerefficient - but I think that was due to usecase (I only used a black backgrounded ssh shell to access my development machine the whole day). So I would like to go with 22th kernel, if no one coplains 'bout stability or issues. But I'm open to your sugestions. If coding the whole day, I had to relay on your testing! Even if I had tested the whole day, I would relay on you, 'cause I don't see/use/test everything.
[Galaxy Tab S Original Android Development] hurray:
:) Everything is okay, it was only a quick test.

I will test as much as I am able. The next few days will be short in time because Christmas is coming. :D

Till now the newest kernel runs without any issues for me.
[Galaxy Tab S Original Android Development] :
Hey, relax, it's Christmas Eve. I've seen 28 downloads on the latest kernel - but no complains. Over the last 5 days there was no one claiming the new clocks on cpu/gpu were freezing his device. So I consider the changes (made possible only by the work and help of [MENTION=3511708]UpInTheAir[/MENTION], who - and really let this fact enter your mind - tought my kernel hacking in pre-Christmas-time while having a tyre-breakdown!) as stable.

I'be decided to go one step back and take out bfq and high efficient workques again:

In my usecase bfq has little more battery drain then cfq (should sammy have done a good job in adapting cfq to exynos?), but much more important (very egoistic, but I think on this I'm allowed to be...) I expirienved lagging in one single special usecase:

I use hackers keyboard 'cause it's the only keyboard I can work comfortable with vi and screen in a remote ssh connection (you guessed it: thats the way I access my development host). And hackers keyboard is laghing some times with these last patches - if I use bfq or not.

But don't worry, if you like bfq you can always flash chagallwifi-48-20141221-b.

cc (Christmas Compiler) is doing its thing. I would like to do a few quick tests after build has finished. So I think it will take me a couple of hours before I will publish the build.

ETA: 13:00 h. UTC - if tests work well.
[Galaxy Tab S Original Android Development] :
Christmas Build

I wish everybody in this forum a merry Christmas. May God (in whichever you belive) bless Yours Beloved and and You!

New build is seems to work: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141224-UNOFFICIAL-nvertigo-chagallwifi.zip

Changlog and announcment in #5 follpws later. Propably after Christmas.

Merry Chrismas!
[Galaxy Tab S Original Android Development] FormeriPhoney:
Any chance of a md5 just to be safe?
[Galaxy Tab S Original Android Development] :
It's already on the server: look in http://charlesingo.mine.nu/ftp/nvertigo// It's the filename of the rommwith .md5sum appended.
[Galaxy Tab S Original Android Development] FormeriPhoney:
Tried that
[Galaxy Tab S Original Android Development] :
...happens when typing and talking simultan...

http://charlesingo.mine.nu/ftp/nvertigo//
[Galaxy Tab S Original Android Development] FormeriPhoney:
Awesome! Just a question? How do I view that md5 file? Can't seem to view it anyway

Now go enjoy your holidays!
[Galaxy Tab S Original Android Development] :
It's a standard textfile. I'm the sh-guy, so:

cat /path/to/file/name

But any file explorer should work - if asked, answer: text.
[Galaxy Tab S Original Android Development] FormeriPhoney:
Hey fellas. Which gapps are you using?

Is this still valid?
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
I use the 4.4.4 gapps. Cm11 gapps should be the same as 4.4.4 I guess. When flashing it will check if its compatible then installs. Might as well go for it.
[Galaxy Tab S Original Android Development] Offica:
Thanks for the rom update hope you have a good xmas. Cant wait to see what you can do with the kernel :D
[Galaxy Tab S Original Android Development] FormeriPhoney:
First off happy holidays to all.

Had a sdcard question.

I was trying to copy a movie to my sdcard and it was telling me it was too large of a file (4.2gb). So I reformatted it to ntfs bc I remembered there is no limit for in that storage format.

Now I can't view my sdcard in twrp any longer? Is that the reason? Does it need to be formatted back to fat32?
[Galaxy Tab S Original Android Development] :
Change order of two first words in secound question... ;) Idon't know if twrp has ntfs support (our rom and kernel has), but you found out. I would try ext4 - I belibe twrp can read it - if twrp like it on sdcard1? Don't know, please report back.
[Galaxy Tab S Original Android Development] FormeriPhoney:
I don't mind using the fat32 but if I want to drop in a Blu-ray quality movie it won't take. When I have a chance I'll try again... Currently I'm working
[Galaxy Tab S Original Android Development] Narsil:
Sorry guys, I'm totally lost in your versioning, could someone help me !?

I'd like to flash this on my T800 (32Gb, but looks like it should work) and well ... OP and post #5 give links to files that don't exist on http://charlesingo.mine.nu/ftp and well ... I don't get it !

What's the actual latest build ? I bet on cm-11-20141224-UNOFFICIAL-nvertigo-chagallwifi.zip but I didn't find any link to that file nor changelog in the OP or post #5, right ?

Thx
[Galaxy Tab S Original Android Development] FormeriPhoney:
Here you go. . He just has not updated the OP yet.

Flashed it last night. It's all good to go.

I wish everybody in this forum a merry Christmas. May God (in whichever you belive) bless Yours Beloved and and You!<br />

<br />

New build is seems to work: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141224-UNOFFICIAL-nvertigo-chagallwifi.zip <br />

<br />

Changlog and announcment in #5 follpws later. Propably after Christmas.<br />

<br />

Merry Chrismas!<br/>
[Galaxy Tab S Original Android Development] Narsil:
Thanks [MENTION=3526654]FormeriPhoney[/MENTION], almost everything's ok ;)

Only issue : no SD card, is this a known bug ?
[Galaxy Tab S Original Android Development] FormeriPhoney:
Are you having that issue? I was but my card is not properly formatted. I'm going to reformat to exfat when I'm back home. Otherwise sd was never a problem for me.
[Galaxy Tab S Original Android Development] Narsil:
Yep, I do. The SD was ok with my previous ROM (ThunderRom800, stock based).
[Galaxy Tab S Original Android Development] FormeriPhoney:
Hmm. That would be a big issue for me. Maybe someone else or the dev can chime in. I know on the previous build it worked fine.
[Galaxy Tab S Original Android Development] Narsil:
After some tests : SD card formatted in NTFS is ok, FAT32 isn't.
[Galaxy Tab S Original Android Development] Retiredfinally:
Anyone having trouble with Chromecast? Not sure if it is the router, rom or what.
[Galaxy Tab S Original Android Development] Narsil:
No chromecast problem here
[Galaxy Tab S Original Android Development] Retiredfinally:
Thanks, it is not new but for some reason is not working all of a sudden and says it is working but will not stream anything.

Thanks!
[Galaxy Tab S Original Android Development] :
No problem with fat32:

/ # fdisk /dev/block/platform/dw_mmc.2/mmcblk1

The number of cylinders for this disk is set to 7614.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/block/platform/dw_mmc.2/mmcblk1: 62.8 GB, 62881005568 bytes
256 heads, 63 sectors/track, 7614 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/block/platform/dw_mmc.2/mmcblk1p1 * 1 7615 61406208 c Win95 FAT32 (LBA)

Command (m for help): q

/ # mount |grep mmcblk1
/ # mount |grep sdcard1
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type fuseblk (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/fuse on /storage/sdcard1 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/ #

I've just viewed a vdr recording via cast screen on a chromecast stick. Had some lags due to bad wlan signal, but thats all.

I suggest clean flash and providing logcats.