yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] :
Thank you for answering. The next is not sddressed to you:

Why you guys use a unofficial rom from android original development, but are not willing to read through the thread and ask all over the same questions again.

This special question is very annoying. I answered it at least three times this answer is at least the forth time! And not only that, you just say it's an issue...

Folks: read. Read again. Read a third time. Use the search function in thread. Use google search. Think of all you have read. And then after following these six simple steps ask your question. And always remember: asking a question and getting an answer is an issue of please and thankx. So use the thanx button.

Being to lazy to read and telling here there is an issue is sometihng completly different. To be honest I think it's lazy stupidity and a waste of bandwith and time (at least for all other members)!
[Galaxy Tab S Original Android Development] Barracuda77777:
for anyone who want to give lollipop a go, I have posted a build in this thread

issues, graphical glitches in recent and screen shots, apart from that the rom is really fast!!!!!
[Galaxy Tab S Original Android Development] hurray:
Thank you very much, I will take a look. :)

I am interested in the look & feel and if I miss my xposed modules that much. :D
[Galaxy Tab S Original Android Development] hannomag:
Got the lollipop installed and it's running great so far. Thank you all for your great work on this peace of hardware!

I realised graphical glitches in the multitasking list. I guess you mentioned that.

I know, it's a first build and you said it's prpably not for daily use I want to report what I realised. Maybe it helps on your development. I hope so.

what I realised:

I had to switch on the virtual key because the "recent apps" capacitive button does not work. Home and back do work.

When booted I get a popup message twice, that google sound search had to be closed. After confirming that messages the rom runs fine (did not test google sound search because I don't use it).

Bluetooth-keyboard works great. That's pretty much what I can say so far. I will do some more testing and let you know if I realise anything else.

Thanks again!

Sent from my SM-T800

edit: it's "sound search for google play" not "google sound search"
[Galaxy Tab S Original Android Development] :
New Buid up in posting #5

Build 1206 Santa Claus

Maintainance release. Kernel updated to 3.4.105. repo synced.

MD5: d5fb397ee8fb48b7937ebcf3b9c691ea

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20141206-UNOFFICIAL-nvertigo-chagallwifi.zip

---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------

To avoid confusion: wrong thread! This is cm11. Please don't mix in cm12 statements, 'cause users who don't read very carefully could be confused.
[Galaxy Tab S Original Android Development] hannomag:
My fault. Won't mix it anymore. Thank you for your work on CM11 too (this thread). Itliberated my tab from this tuch wiz crab. Guess I'll move on now (to the other tread ;)) because it allready works for me.

Keep on doing what you do. Seems you'regood at it. Two thumbs up!

Sent from my SM-T800
[Galaxy Tab S Original Android Development] FormeriPhoney:
Damnnnnnnn.. I thought wee weren't gonna get a build for a few weeks? [emoji1] [emoji106] [emoji106]
[Galaxy Tab S Original Android Development] :
Thought so, too... But there was a small timeframe. Thanx to [MENTION=4193974]Barracuda77777[/MENTION] I could access my development machine, and so....

But you are right - so: excuse me for building... ;)
[Galaxy Tab S Original Android Development] hurray:
Thanks for the new build! It runs good without any new issues.

For a daily driver I went back to CM11 as I do miss the xposed modules (xprivacy, YouTube adblocker, app settings (for forcing apps to the correct rotating) and so on) :)
[Galaxy Tab S Original Android Development] biogon:
Installed 1128 last night on mine.

It is a whole new tablet! That is amazing work. Thank you nvertigo67!
[Galaxy Tab S Original Android Development] FormeriPhoney:
Dirty flash OK from 11-28?
[Galaxy Tab S Original Android Development] hurray:
A dirty flash coming from 1128 works for me without any problems.
[Galaxy Tab S Original Android Development] FormeriPhoney:
Just did the same. All is good
[Galaxy Tab S Original Android Development] cappa662:
Same, this rom + nova = butter :good::good::good:
[Galaxy Tab S Original Android Development] Sudbury78:
I'm waiting for my new tablet to come in from bestbuy and then j be back on this rom. :)

Sent from my t mobile note 4 or Tab s
[Galaxy Tab S Original Android Development] hurtz777:
Is there any way to make a cpu/gpu over clock kernel for CM11 and CM12? I would use this rom as my dd but I play 8 ball pool and it is a little choppy, but on TW NK1 build it plays smooth as butter.
[Galaxy Tab S Original Android Development] :
Have you tried disabling app-profiles and setting profile to performance? Perhaps governor ondemand helps, too.

No OC in kernel.
[Galaxy Tab S Original Android Development] hurtz777:
Setting the profile to performance doesn't save after reboot and I have disabled app-profiles. I will try On Demand governor though. Thanks!
[Galaxy Tab S Original Android Development] DanB85:
I apologize if is has been asked...

My battery is dropping in large increments, then jumping up after a reboot. Has anyone else experienced this? Is there a fix?

Thanks everyone. Its great to not have touchwiz!
[Galaxy Tab S Original Android Development] :
I have read about that. But not with our rom. Search in general or q&a.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Recalibarte. Do a couple of charging and draining cycles and JT should get you 8 hours screen on time.

Sent from SMT800 using Tapatalk.

-Helper around Tab S forums√

Active Everyday√
[Galaxy Tab S Original Android Development] maxrdlf95:
Could anyone upload latest version to mirror its going like 10 kb/s here don't know why used to be super super fast
[Galaxy Tab S Original Android Development] Barracuda77777:
https://www.androidfilehost.com/?fid=95855108297851322
[Galaxy Tab S Original Android Development] Zootopia:
Would've loved to try this on my T800 if it wasn't for the lack of XBMC support. :rolleyes:

Beautiful dark UI, and guess it's fast as hell, as CM usually is.

I have the 32 Gb model, is there any incompatibility issue? Suppose not, but it doesn't hurt to ask...

(there isn't a dedicated Q&A thread...)
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
On the latest build, I can't seem to get ir blaster to work. Also It won't let me open apks from unknown sources. I checked the box for unknown sources and nothing. It just sales can't open file. Tryed downloading other apps like YouTube apk and nothing.
[Galaxy Tab S Original Android Development] FormeriPhoney:
That's odd. I'm not having that issue. How about wiping both caches only and dirty flashing the rom
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
I just did like right now. Same thing! It not the site either! Just went on apk mirror and try downloaded YouTube app. Keeps saying can't open file. Even in file manager. Unknown sources is checked. I'm on the December build

Edit reflashed and downloaded doesn't work on December build. Works fine when I'm on stock. I did a clean flash also.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Edit2: The problem appears to be the download manager app. I did some reasearch and tried installing from file manager and it works OK. The latest ROMs are fine, but there is a problem from installing apps from broswer and trying to open them from the downloads manager. File manager fixes this problem!!
[Galaxy Tab S Original Android Development] sku||:
Work pretty AWESOME on my t805 !!! except for no mobile data :v Can you add this function :>
[Galaxy Tab S Original Android Development] :
You shouldn't have any problems running this rom on 32gb device. Some useres have done without issues.

As for xbmc: adding some specials to synaptics_dsx drivers is out of my abillities. Some pages back I have explained that and asked for help. No one showed up so far.

---------- Post added at 08:16 AM ---------- Previous post was at 08:12 AM ----------

For the fith or sixth time: No. I won't build for devices that I don't hold in my hands. That was never discussable nor will be.

[MENTION=886370]New User[/MENTION]s: read the thread befre asking already answered questions. Thank you.
[Galaxy Tab S Original Android Development] :
I have tried to understsnd what ir blaster apk is good for. But I don't have itach devices (what ever taht could be). IR to control my tv works just fine. With what build IR Blaster has stoped working? Please send a logcat and an detailed error description.

Your second issue description is confusing me: you write, you can't open the file even not in filemanager, a post later you write it's just downloafmanager it is working in filemanager... Please describe step by step with complete urls, what you are doing, give exact error messages occuring in this process and supply a logcat.
[Galaxy Tab S Original Android Development] Zootopia:
It's too bad about that XBMC issue

.

Thank you very much for the feedback nvertigo67, I'll certainly stay sharp on what's to come on this project.
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Fixed the second issue with installing 3rd party apps with file manager instead of the downloads manager. Download manager just saids (can't open file). I downloaded a youtube app to test http://www.apkmirror.com/apk/google-inc/youtube/youtube-6-0-13-apk/ link to apk. As long as you use file manager, it should be fine. For the IR it might be the app I'm using. Will try to find one that works. I'm on the December build also. Sorry for any confusion.
[Galaxy Tab S Original Android Development] Barracuda77777:
let's start with a 3g enabled kernel,

please flash this and let me know:

sorry I realised I linked the wrong file and also you mentioned that your tablet is lte, making a new kernel now

when I do make the rom you should be able to dirty flash, first though if with this kernel 3g does not work, that means that we have missing blobs needed by 3g model.

and will have to research further before building you a rom.

now regarding the bluetooth keyboard, I do have one but did not have the chance to try it, I will look into it soon :)

cheers
[Galaxy Tab S Original Android Development] Gilg@mesh:
I flashed it, but is there anything else I need to do? still no network :)

EDIT: I just saw your edited post :D
[Galaxy Tab S Original Android Development] Barracuda77777:
sorry I linked you with the wifi kernel, please give me 10 more minutes please
[Galaxy Tab S Original Android Development] Gilg@mesh:
no problem, take your time, no hurry. :D

btw, [MENTION=3511708]UpInTheAir[/MENTION], SkyHigh Kernel for this would be lovely! :)
[Galaxy Tab S Original Android Development] Barracuda77777:
try this kernel,

warning this is for the LTE model T805 only wifi users please don't flast this

https://drive.google.com/file/d/0B8L3WJtLbJOBYUVwTGZZa2oyQjg/view?usp=sharing

warning this is for the LTE model T805 only wifi users please don't flast this
[Galaxy Tab S Original Android Development] Gilg@mesh:
thank you, but still no network, maybe there is something thats need to be done with the ROM too?
[Galaxy Tab S Original Android Development] Barracuda77777:
yes there is, please give me some more time, I will make a build and pm you so that way we don't confuse users between 800 and the 805
[Galaxy Tab S Original Android Development] Gilg@mesh:
take your time, as I said before, I can experiment on this as I only use it for playing videos :D

will you get the build soon? I thought of going to bed soon :)
[Galaxy Tab S Original Android Development] Barracuda77777:
I am not sure if I can today, as I have other life issues I have to deal with :)
[Galaxy Tab S Original Android Development] Gilg@mesh:
ok no problem, just PM me when it's ready, good luck! :)
[Galaxy Tab S Original Android Development] jodeltje:
I'm on this build and its running fast and smooth, good work!

On a side note, Netflix isn't working, just like the camera.
[Galaxy Tab S Original Android Development] Barracuda77777:
just flashed the above link, netflix working for me, I am on 3.7.0 Build 1672, also camera video and photo taking is working.

can you please try this for me:

in twrp

wipe the following:

system, cache and delvik, then flash in this order please:

1: cm-11-20141028-UNOFFICIAL-chagallwifi-enabled-capactivie-buttons.zip

2: your gapps

3: optional = supersu.

4: restart

cheers
[Galaxy Tab S Original Android Development] jodeltje:
Thanks for your reply, I did that and Netflix is working now. Still get the "can't connect to camera" message though.

Now that Netflix works I'm happy, the rest is of less of an importance to me personally.
[Galaxy Tab S Original Android Development] Barracuda77777:
have you tried this app:

https://play.google.com/store/apps/details?id=com.billgbennett.camerafix
[Galaxy Tab S Original Android Development] jodeltje:
It doesn't give me the error message, but hangs before you can take a picture.

Edit: It kinda works when you switch to front camera, force close, start camera app again, switch to back camera and take a picture.

Edit 2: afterwards of running cm camera fix, the camera works just fine (until reboot) :)
[Galaxy Tab S Original Android Development] ares.:
hello, may i ask you one more question, can i use the skyhigh kernel with this rom???
[Galaxy Tab S Original Android Development] :
No. Ramdisks differ; additionally we have at least one kernel-patch we need to have ir running.

---------- Post added at 05:47 AM ---------- Previous post was at 05:25 AM ----------

Please try this, when camera stays black after reboot:

1. Make sure camera2 isn't running.

2. Use "RestartCamera" (IMPORTENT:don't use "CameraFIX (CM)", 'causr we don't want to start camera at this point!)

3. Delete /data/CameraID.txt

4. Start "GoogleCamera" and make sure BackCam (the one pointing away from you) is activated.

5. Start camera2 again.

Good luck. Works for me with nvertigo-build.
[Galaxy Tab S Original Android Development] Barracuda77777:
New build up

New build is up, please check first post.

bluetooth keyboard not disabling software keyboard is now fixed
[Galaxy Tab S Original Android Development] drei666:
Hi,

I am interested in flashing the 805 build.

Please let us know..

Thanks

dREI
[Galaxy Tab S Original Android Development] Barracuda77777:
I am sorry but I decided not to ahead, reason being I don't have the tablet neither does nvertigo67.

our apologies
[Galaxy Tab S Original Android Development] :
Just tested:

Downloaded with Browser.

Tabed on donwload in. Notification pulldown.

Got asked to choose app for openening file (have two unzip tools).

Basicaly thats ok, 'cause apk is zipped content, but you want installer app to be opened, don't you?

Did same test on my n10 and opo: same result: archive apps wants to be selected. What I don't get on either devices is: "can't open file"-error., but perhaps that's 'cause I have archivers installed. So it's a bug/feature introduced upstream in cm...

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

While playing with underclocking CPU/GPU I realized sammy has restricted our wunderful SOC to 480MHz. I'm not sure if this is a bug or a feature. I know from SkyHigh-tw-kernel, that my device runs stable at 2000/600 MHz without increasing voltage, so I think we can savely go to 533 MHz on GPU.

Can you (if someone still on sammy stock rom and kernel reads this, please, please, please do the same) issue the following command on a shell (terminal app or adb):

cat /sys/devices/platform/mali.0/time_in_state
533 0
480 4932
420 6874
350 6883
266 425295
177 21247

(only the first line is command; next 6 lines are output given as an example)

...and post the output. Thanx in advance.

I think I will make a kernel with 533 enabled...:confused:
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Your lucky! I am on stock useing skyhigh tw kernel. Exactly what does this do? Does it change the clockspeed or lower it? Can it be undone? I can do it right now if you want. So when i put this in the terminal just screenshot what happens after i type it in? Thanks in advance.
[Galaxy Tab S Original Android Development] UpInTheAir:
Yes, 177-480 is stock. Stability depends on your ASV Group.

/sys/kernel/debug/asv_group

The higher the better. Higher = able to use higher frequencies and or less voltage for any given frequency.

You can find the voltage tables in source.

So, not all devices are equal (not same group) and not all have same stock voltages for any given frequency. Thats why Sammy capped it at 480. If you have ASV 0, 480 would possibly be the limit. Same could be said with regard to CPU and internal frequencies/voltages too.

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

As it says. Only shows the total time in ms for any given allowable GPU frequency
[Galaxy Tab S Original Android Development] :
Test kernel

Forget it. If you are using [MENTION=3511708]UpInTheAir[/MENTION] kernel I KNOW, that it uses 533 MHz. I want a reading from stock kernel.

The command just reads the time gpu is used at the specified MHz. As you can see in my example standard sammy kernel source does not use 533 MHz at all. I just want to know, if this is the same in sammy stock kernel, or if this results from error(?!?) in sammys opensource support.

But it's not important any longer. I did the following:

mali gpu: lowered min freq to 100 MHz, enabled 533MHz, optimized up/down stepping.

exynos cpu: disabled 250 MHz, enabled 200 and 100 MHz.

Please test this kernel thoroughly, 'cause I plan to use it as standard in next build.

Before you ask:

This is NOT! a overclocking kernel: I just wanted to lower the min freqs to save some battery. I tried the last days to get the kernel to unplig cpus earlier - to no advance. I had adopted all the commits from exynos5420 kernel based on chagalls source: battery drained faster. I tried to implement intelliplug, but run into a wall of changes sammy did to the t800 source. So I decided to go the minimal invasive way of lowering min MHz to values (more or less ;) ) already build in the sammy source. On that way I realized that malis 533MHz was never used with kernels based on the sourcecode sammy relesed to community (if I wouldn't be busy doing this cm-11.0 build I would go and kill some sammy managers... ;) ). I do not intend to overclock this kernel nor do I plan to implement over-/undervoltage nor an interface to control it. Not discussable - I want to stay as close as possible to stock. The only reason why I enabled 533 MHz on mali is: I consider this an error.

If some one has plenty of time, she/he can implement intelliplug. If running stable and unplugs cores early I would be glad to put it in the roms kernel - 'cause I consider sammys implementation of core hotplugging an error (did I tell you, what I would do, if I wouldn't be so busy with [MENTION=4193974]Barracuda77777[/MENTION] and my rom... ;) ).

OK. Enough wining. Build from https://github.com/nvertigo/android_kernel_samsung_chagallwifi/tree/my-work Happy flashing for everyone!

BTW: only flash over santa edition (20141206 nvertigo)
[Galaxy Tab S Original Android Development] DUHAsianSKILLZ:
Here you go?!

u0_a99@chagallwifi:/ $ cat /sys/devices/platform/mali.0/time_in_state

667 0

600 0

533 0

480 243145

420 15069

350 63246

266 315767

177 2319446

100 400

u0_a99@chagallwifi:/ $

Edit jist saw your post.
[Galaxy Tab S Original Android Development] :
Wow. Thanx for that explanation! Overlaped with my posting. Then I will stay on rom builds with standard source, and provide the posted kernel as addition. My device is asv group 3 and runs just fine with the Test kernel:

/ #cat /sys/kernel/debug/asv_group
VDD_ARM ASV group is 3
VDD_KFC ASV group is 3
VDD_INT ASV group is 3
VDD_MIF ASV group is 3
VDD_G3D ASV group is 3

As for the SkyHigh cm Kernel project: I have started to make a UKM zip for SkyHigh Kernel, to have rom.zip, kernel.zip and UKM.zip with prefered busybox. Everything cleanly seperated. In a coombined Kernel & UKM zip I can't get rid of side effects either to UKM or to rom... :(

Again: I will not implement ov/uv & oc/uc with interface in this rom.

---------- Post added at 05:28 PM ---------- Previous post was at 05:25 PM ----------

Thanx, but I know this is working in SkyHigh...

Run some egl intensive app (antutu or windmill i.e.) and you will see, that all MHz steps, that you congiguered in synapse will be used.
[Galaxy Tab S Original Android Development] UpInTheAir:
Don't forget the 5420 LITTLE cores table need to double for actual frequency. Ie min 100 MHz (unlocked) is actually 200 MHz.

As I explained why Sammy limit the frequency is because of QA testing > asv_group. This is NOT an "error".

This is same for all device 5420 source and implemented in all device 5433 as well. Lower asv_group devices simply can't handle higher frequencies. Same could be said why some can use 2100 MHz CPU and others can't.

"One size fits all"
[Galaxy Tab S Original Android Development] :
To my understanding it is just the other around (or I misread your post - most propably we mean the same):

Sammy min:

L11 ~ 500 ~ 250 MHz

Test Kernel min:

L14 ~ 200 ~ 100 MHz

Have to look in the scripts UKM scripts again - do they offer different options for different ASV groups? Is it possible (of course it is - I mean with reasonable effort) to test asv group in kernel in exynos/mali drivers?

Are the lower freqs (100 MHz for cpu and gpu) save for all asv groups?

And if you are around - I have to use your knowledge:

/ # cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
1900000 115978
1800000 62558
1700000 11282
1600000 21045
1500000 8475
1400000 2584
1300000 2807
1200000 4648
1100000 2224
1000000 5006
900000 2840
800000 9083
650000 48746
600000 4087
550000 3646
500000 8033
450000 4698
400000 10349
350000 6109
300000 34849
200000 128510
100000 1372

Are there any adjustables to force to step up to 200 or 300 MHz later (perhaps also for earlier unplug and later replig cores)? Like mali_dvfs_infotbl in drivers/gpu/arm/t6xx/kbase/src/platform/5420/mali_kbase_dvfs.c?

Thanx for your lessons in kernel hacking!!! (You saved some sammy managers... ;) ) I really, really apriciate!
[Galaxy Tab S Original Android Development] hurray:
I just shoot the command in a shell:

root@chagallwifi:/ # cat /sys/kernel/debug/asv_group

VDD_ARM ASV group is 2

VDD_KFC ASV group is 2

VDD_INT ASV group is 2

VDD_MIF ASV group is 2

VDD_G3D ASV group is 2

At Sammy Rom with the Skyhigh Kernel I am able to clock to 2000MHz CPU and 533-600MHz GPU.

[MENTION=3511708]UpInTheAir[/MENTION]: Thank you very much for the informations! :)

@ nvertigo67 & barracuda77777: Thanks for making the Rom even better!
[Galaxy Tab S Original Android Development] :
;) Sun Microsystems some decades ago had a poster saying: who stoped getting better had stoped being good... ;) Time is limited, so some things will take it's time.

If gpu 100-533 MHz on SkyHigh works for you, you should be save to flash Test kernel.

So I consider avs group 2 is good enough for my adjustments.

OT: I'm so happy with my opo - thanx for your advice!
[Galaxy Tab S Original Android Development] Buckster76:
considering rooting my 10.5

just checked the ASV groups - and mine all seem to be 7s

I'm bit confused to whether thats good or bad - I'm an avid overclocker etc on my pc -but never messed around wtih it on my tablets
[Galaxy Tab S Original Android Development] :
Higher is better. Mine is 3 and Test Kernel works.

BUT: don't flash Test kernel on sammy rom!!!!!! First root - then read thread (to be sure reread #1 to #5 ;) ) - then try our rom - and then flash Test Kernel.