yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S General] jasonfxp:
Do you have any theories on why the IOCTL would be failing? Kernel driver is the same as stock right, so it kind of implies that it must be a vendor lib /userspace prior IOCTL is failing to setup the FB device or get it in the correct state, hence the ENOTTY maybe? I'm going to do some work porting CM for the 10.5 this weekend so i will try and get up to speed with where you are :)

---------- Post added at 03:46 AM ---------- Previous post was at 03:41 AM ----------

Notice on fd 22, before the ENOTTY you have

ioctl(22, FBIOBLANK, 0) = -1 EBUSY (Device or resource busy)

writev(16, [{"\4", 1}, {"hwcomposer\0", 11}, {"unblank ioctl failed (display al"..., 49}], 3) = 61

I wonder why fb0 is stuck as busy...
[Galaxy Tab S General] eousphoros:
The only working theory I have at the moment is ExynosHWC that we have is 1.1 and the device ships with 1.3. I'm digging thru kernel/drivers/video/s3c-fb.c right now trying to understand what's happening a little better.

#ifdef CONFIG_ION_EXYNOS

case S3CFB_WIN_CONFIG:

if (copy_from_user(&p.win_data,

(struct s3c_fb_win_config_data __user *)arg,

sizeof(p.win_data))) {

ret = -EFAULT;

break;

}

#ifdef CONFIG_S5P_DP_PSR

if ((sfb->psr_enter_state == PSR_PRE_ENTER ||

sfb->psr_enter_state == PSR_ENTER_DONE) &&

sfb->psr_exit_state != PSR_PRE_EXIT) {

s3c_fb_psr_exit(sfb);

}

if (sfb->psr_exit_called) {

flush_kthread_worker(&sfb->psr_exit_worker);

sfb->psr_exit_called = 0;

}

#endif

ret = s3c_fb_set_win_config(sfb, &p.win_data);

if (ret)

break;

if (copy_to_user((struct s3c_fb_win_config_data __user *)arg,

&p.win_data,

sizeof(p.win_data))) {

ret = -EFAULT;

break;

}

break;

...

...

...

default:

ret = -ENOTTY;

}

$ cat klimtwifi_01_defconfig | grep CONFIG_ION_EXYNOS

CONFIG_ION_EXYNOS=y

CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE=6144

# CONFIG_ION_EXYNOS_DEBUG_VERBOSE is not set

CONFIG_ION_EXYNOS_DRM_MFC_SH=y

CONFIG_ION_EXYNOS_DRM_MSGBOX_SH=y

CONFIG_ION_EXYNOS_DRM_MFC_FW=y

CONFIG_ION_EXYNOS_DRM_SECTBL=y

CONFIG_ION_EXYNOS_DRM_VIDEO=210944

CONFIG_ION_EXYNOS_DRM_MEMSIZE_FIMD_VIDEO=0

CONFIG_ION_EXYNOS_DRM_MEMSIZE_MFC_OUTPUT=0

CONFIG_ION_EXYNOS_DRM_MEMSIZE_MFC_INPUT=16384

CONFIG_ION_EXYNOS_DRM_MEMSIZE_G2D_WFD=8192

CONFIG_ION_EXYNOS_MEMSIZE_SECDMA=128
[Galaxy Tab S General] jasonfxp:
Maybe some libs missing in your tree?

access("/vendor/lib/hw/power.universal5420.so", R_OK) = -1 ENOENT (No such file or directory)

access("/system/lib/hw/power.universal5420.so", R_OK) = -1 ENOENT (No such file or directory)

access("/vendor/lib/hw/power.universal5420.so", R_OK) = -1 ENOENT (No such file or directory)

access("/system/lib/hw/power.universal5420.so", R_OK) = -1 ENOENT (No such file or directory)

access("/vendor/lib/hw/power.exynos5.so", R_OK) = -1 ENOENT (No such file or directory)

access("/system/lib/hw/power.exynos5.so", R_OK) = -1 ENOENT (No such file or directory)

access("/vendor/lib/hw/power.default.so", R_OK) = -1 ENOENT (No such file or directory)

I have power.exynos5.so on my 10.5, that could be the reason the fb isn't coming up.
[Galaxy Tab S General] eousphoros:
Not related, tried pushing that over earlier but it didn't have any effect on the issue. I am trying out a kernel patch to the s3c-fb driver now.
[Galaxy Tab S General] eousphoros:
/happydance does not properly express the glee I am feeling at the moment.

struct s3c_fb_win_config {

enum {

S3C_FB_WIN_STATE_DISABLED = 0,

S3C_FB_WIN_STATE_COLOR,

S3C_FB_WIN_STATE_BUFFER,

} state;

union {

__u32 color;

struct {

int	fd;

__u32	offset;

__u32	stride;

enum s3c_fb_pixel_format	format;

enum s3c_fb_blending	blending;

int	fence_fd;

int	plane_alpha;

};

};

int	x;

int	y;

__u32	w;

__u32	h;

};

This is from the fixed header that has been causing me so much grief.

I now have CM 11 up and running with custom kernel, hwcomposer/gralloc/etc. This is beautiful. Stil some bugs to work out but I think I will have a rom to release by this weekend.
[Galaxy Tab S General] eousphoros:
Apologies for the ****ty image, I really need to upgrade my phone. Anyways heres a little love for the naysayers.

[IMG="cm11-tabs"]https://blck.io/cm11-tabs.jpg[/IMG]
[Galaxy Tab S General] dw1ght:
That is just a lovely sight. Well done! :highfive:
[Galaxy Tab S General] eousphoros:
Ok, just because I am sleep deprived + excited to share.

https://blck.io/recovery.img

https://blck.io/cm-11-20140731-UNOFFICIAL-klimtwifi.zip

WARNING THIS IS NOT EVEN AN ALPHA. YOUR TABLET WILL NOT BE FUNCTIONAL OTHER THEN TOUCHSCREEN AND BUTTONS.

but if you want to play with it and not cause me too much grief because feature x doesn't work. Please do.
[Galaxy Tab S General] suzook:
Damn why did I think you had a 10.5???? I'm a little sad right now. Do you think when you get it running stable, you can port it to the 10.5????
[Galaxy Tab S General] MariozPOC:
Anyway it is a VERY good news!!! Thnks a lot for your hard work.

I really cannot wait to put a real Android on my nice tablet!
[Galaxy Tab S General] mitchellvii:
Read that [MENTION=4167023]AndreiLux[/MENTION] is a major Exynos Android stud. Might be worth reaching out to him on your project.
[Galaxy Tab S General] rey_1178:
Good job eousphoros :highfive:
[Galaxy Tab S General] diegosolor:
Congratulations and thank you for the good work!

I will try it as soon as the wifi is working

Is the direct rendering already working with the mali's binary or is just software rendering?
[Galaxy Tab S General] enaybee:
wow ... this is awesome. Thank you very much. You Sir are amazing.
[Galaxy Tab S General] eousphoros:
Mali is working in this build. Its pretty much the only thing that is, though that's a bit intentional. I disabled everything else to minimize the interactions during dev. Now to start adding that stuff back.
[Galaxy Tab S General] eousphoros:
If you send me a 10.5 ;) Though really I am just focused on getting my device running 8.4. I'll think about it though, it shouldnt be too difficult once I have this running.
[Galaxy Tab S General] eousphoros:
And one last thing before I head to work. This tablet is FAAAST, almost too fast. I am sitting here flinging windows around thinking, "Slow down tablet! I am not as young as I used to be".
[Galaxy Tab S General] enaybee:
so none of the lag that is present in TW? Because currently its unbearable.
[Galaxy Tab S General] eousphoros:
Not yet at least. In fact I am tempted to slow down the animations a little bit just because I am old and nothing should be this fast.
[Galaxy Tab S General] suzook:
Lol. I wish I had the $ to get you one. Well I guess us with 10.5's will hope you have the time to port it.
[Galaxy Tab S General] mitchellvii:
Is it time to move this to Original Development?

Congratulations. If you don't want to develop for the 10.5 we'll probably get someone who will now that you've cracked the code. Maybe even an AOSP or two. :) Excellent work and thanks for your assistance in the TW rom development too.

If you decide to give the 10.5 a shot I'm sure you'll find willing testers.
[Galaxy Tab S General] harshkolli:
Wowww!! Greaaat Job!!...Thats great news!!!....Hope SideSync works on this build!!...That is the last thing I want to loose!!...Leave the sammy crap! :cool:
[Galaxy Tab S General] eousphoros:
Sorry, sidesync wont be in this rom. IMO that is sammy crap as you call it. ;)
[Galaxy Tab S General] suzook:
Ugh...I really hope someone ports this to the 10.5....I need me some cm!
[Galaxy Tab S General] Shaheer:
Yeah I hope this gets spread over on the Tab Pro 10.1 and the Tab S 10.5. That would be awesome! :victory:
[Galaxy Tab S General] eousphoros:
Once I get WiFi working I'll do an official unofficial thread in od. Thank you all for the support. This would not have happened so fast without the awesome community.
[Galaxy Tab S General] mitchellvii:
Yep looks like in a few days we've gone from nothing for the Tab S to being on the brink of both a CM and a TW rom (thanks for your help on that too). Nothing succeeds quite like success.
[Galaxy Tab S General] suzook:
Damn...I might have to sell my 10.5 to get a 8.4....I'm dying.
[Galaxy Tab S General] eousphoros:
What is the current release of the official firmware? Right now I am pulling binary blobs from /T700XXU1ANF7. If there is a newer release where can I find it?
[Galaxy Tab S General] ukael:
Wow, this is awesome!

I spent the day checking in stores for every recent Samsung tabs. All of them were suffering from stuttering when opening/closing apps, which ruins the experience for me after playing with my perfectly smooth Note 8.0 and N7 2013.

Since hopes were little to see Cyanogen ported on an Exynos device, I was about to return my Tab S 8.4 and wondering what better replacement I could get. Well, I guess the very same tab running Cyanogenmod will make my year. I can't wait for a stable release, thanks eousphoros for the hard work!
[Galaxy Tab S General] mitchellvii:
Up to date firmware for Tab S tablets can be found at www.sammobile.com. They will be listed under Cellular South for USA versions.
[Galaxy Tab S General] UpInTheAir:
Although I don't use CM on any of my devices, I still appreciate the effort you've put in to this.

Nice work and glad too see you didn't " throw in the towel " ;)

Keep it up ! :)
[Galaxy Tab S General] eousphoros:
Thank you, downloading Release 9 now
[Galaxy Tab S General] mitchellvii:
Cool :)
[Galaxy Tab S General] suzook:
You should download the 10.5 version too;)
[Galaxy Tab S General] dw1ght:
It's pretty wild that the 8.4 has CM incoming thanks to OP :)

After thinking about how I use my own Tab S day-to-day I just had some questions. Would we still have the ability to unlock the device with a fingerprint swipe? Seems unlikely but it would be cool to have full use of the hardware functionality. Does the multitasking or "recent apps" function in CM black out the whole screen instead of just sliding out a pane to close apps like in stock? Last question, does a multiwindow service exist in CM11? Touchwiz, for all its faults, has robust tablet - oriented features and I guess my concern here is that CM11 is more phone-oriented.
[Galaxy Tab S General] suzook:
No, you will loose all those features. BTW [MENTION=2346758]eousphoros[/MENTION] i wish I could get you a 10.5, but financially I can't swing it, but $100 is waiting for you if you get it ported soon. Its all I can afford. Thanks.
[Galaxy Tab S General] kenkiller:
You can still use XposedxHalo/MultiSidebarWindow app to get some multiwindow going on, but it isn't as robust as Samsung's implementation.

Basically ALL of Samsung's software features are gone.....you gotta weigh the pros and cons. And it will be pretty buggy initially.
[Galaxy Tab S General] eousphoros:
No promises for what will be available as this ROM progresses. As far as the Samsung software being gone, thatvwas my main drive in this project. Awesome hardware, evil software. I have also recovered about 1.5 GB of space compared to stock.
[Galaxy Tab S General] jeffreycentex:
Yep. I like the hardware and have done my best to rid all of the Samsung software that I could... I like this device over the Nexus 7 because it has the microSD card slot and the nice screen..

Have you got the cameras working?
[Galaxy Tab S General] eousphoros:
Not yet and its low on the list. My current priorities are

Clean up code base ensuring repeatable builds and commuting to github

WiFi - Fixed

Fix touchscreen with custom kernel - fixed

Audio

Camera

Bluetooth

I'm still shooting to have an alpha build out this weekend.
[Galaxy Tab S General] enaybee:
[MENTION=5682130]dw1ght[/MENTION] ^This and the fact that device would be smooth is enough for me to leave TW behind. Like its been said you have to weigh your pros and cons, for me smoothness is everything and I don't really use fingerprint scanner or multi-window. Reason I bought it to replace my LG G Pad 8.3 is because of the hardware specs but I was so disappointed to see TW lagging so badly on a device with twice the horsepower as GPAD 8.3.

Can't wait for this to become a full fledged daily driver.
[Galaxy Tab S General] sku||:
if someone could port CM to t805 , i would be sooooooooo happy
[Galaxy Tab S General] eousphoros:
Interesting bit, of the files I curretly care about.

vendor/lib/egl/libGLES_mali.so

15903472

15907568

Is the only one that changed between R7 and R9. I wonder what changes are hidden in there. Don't notice any difference and everything that used to work still works. I miss the old days when we used to get actual changelogs for this stuff.
[Galaxy Tab S General] eousphoros:
> status

p2p_device_address=b4:3a:28:f6:61:f2

p2p_state=LISTEN_ONLY

wifi_display=1

ifname=p2p0

address=b6:3a:28:f6:61:f2

ifname=wlan0

address=b4:3a:28:f6:61:f2
[Galaxy Tab S General] diegosolor:
so you already have the wifi working?

Slow down a bit! hehe

you are doing an amazing work
[Galaxy Tab S General] eousphoros:
Not quite, I have the device drivers loaded but having issues with wpa_supplicant that I am working on tracking down.

<6>[ 409.488901] [L1: wl_event_handle: 1473] CFG80211-TRACE) wl_escan_handler : SCAN COMPLETED: scanned AP count=15

Now if only I could get the damn android service to talk to the supplicant life would be good.

"E/WifiHW ( 2675): Unable to open connection to supplicant on "@android:wpa_sta": No such file or directory" (sta should be wlan0, something is creating /data/misc/wifi/wpa_supplicant.conf. Need to track that down.)

Reading: http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html

#define WIFI_TEST_INTERFACE "sta"

libhardware_legacy/wifi
[Galaxy Tab S General] eousphoros:
And I have WiFi working, making this post from the tablet! I'll post the new image as soon n as it finishes uploading.

https://blck.io/cm-11-20140801-UNOFFICIAL-klimtwifi.zip (Now with working wifi)

Though now I have to run to a company party so unfortunately I will have to stop playing for a bit.
[Galaxy Tab S General] mitchellvii:
Congrats! Getting wifi working for the first time is always a big moment.
[Galaxy Tab S General] Enddo:
As someone that just received this tablet yesterday, this is exciting. Keep up the great work. If this works out I would be happy to donate
[Galaxy Tab S General] diegosolor:
Installed!

wifi and screen is working OK (also the vibration works :P)

may I suggest make the sound your next target?

thank you very much!!
[Galaxy Tab S General] eousphoros:
Vibration was working before the screen.

When I get home tonight I plan on fixing a few bugs like the sdcard symlink is pointing to the wrong directory, then I'll start poking the sound. The issue is due to a 48000/44100 sample rate mismatch.
[Galaxy Tab S General] diegosolor:
BTW, you were right sir, now it's fast as hell
[Galaxy Tab S General] Enddo:
I'm so jealous and incredibly excited to hear this
[Galaxy Tab S General] mitchellvii:
Out of curiosity, do you feel that Web pages load faster even with Javascript enabled?
[Galaxy Tab S General] diegosolor:
I do, it feels faster. And most of all, smoother

by other hand maybe it's hotter
[Galaxy Tab S General] eousphoros:
Hotter as in the physical temp of the device? If so could you send me a dump of dmesg and also go into settings -} performance -) processor -) CPU. And tell me what it says at idle (should be 250). Then tap the screen in an empty space quickly. You should see it jump up to 1900.

Edit, been doing some battery testing while at the picnic. After four hours of pretty constant use I'm at 75%
[Galaxy Tab S General] diegosolor:
CPU frequency seems fine, 250 MHz when idle, 1900 if I'm browsing big webs. I attach my dmesg log, as you can see there are episodes of temperature over 70ºC while I was browsing. The temperature down fast when I stop.

If I can help you with any kind of test, or whatever, plz tell me
[Galaxy Tab S General] eousphoros:
Hrmm, that's a little warm. I can't get mine past 59. I'll post a build with the stock kernel to see if it makes any difference when I get the sound working.
[Galaxy Tab S General] mitchellvii:
Thanks. I had a theory that TW was doing something with javascript that was making it laggier than on a non-TW device. Javascript is a lag beast anyway but worse on the Tab S with TW as a base.

If it does not lag as badly with it enabled in CM that would at least hint at agreeing with my theory.

---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------

Remember that CM won't have DVFS implemented so the CPU won't throttle at the lower temps meaning it will get hotter overall than in TW.
[Galaxy Tab S General] Laykun:
What do you mean that TW does something with java script? Is tw implemented in java script? I would have thought it'd be native c or java. Otherwise I don't see how touch wiz has anything to do with the java script compilers/interpreters of the browsers. I get the feeling that the tw compositor has something to do with the huge amount of lag on the tab s and I can't wait to put cm on my 10.5.
[Galaxy Tab S General] mitchellvii:
Well I don't want to get OT. It's a subject for another thread on another day. :)
[Galaxy Tab S General] eousphoros:
Some good news + bad news.

Got brightness, and some of the sensor stuff like rotation working.

Still tracking down the issues with sound.

Updated build with the brightness and sensor fix. Don't think I am going to get the sound up tonight.

http://xdaforums.com/galaxy-tab-s/orig-development/unofficial-cyanogenmod-11-android-4-4-4-t2835170
[Galaxy Tab S General] diegosolor:
Screen orientation working! Also, the physical buttons are now iluminated. But the light sensor doesnt work :S
[Galaxy Tab S General] eousphoros:
Great news everyone! Uploading a build now with working sound. Will update the OD thread after it finishes. (Will be release 3)

Now, when I say working sound.

Codec outputs a different number of channels than the input stream contains (contains 2 channels, codec outputs 1 channels).

Though that will have to be a problem for another evening.
[Galaxy Tab S General] win81-64:
I tried your build without the sound working installing CWM using Flashify. When I got into CWM there was no option to install from a external SD card so I installed the zip file of the build on the internal and flashed it. I wiped data/factory reset, cache partition and Dalvik Cache first and then installed the zip. It appeared to be working great, fast and smooth once installed but I noticed that I could not access any folders on the tablet or install anything using the tablet and while windows recognized the device I could not transfer any files over to try to install that way. Is that normal with this build or have I done something wrong in the installation method. Thanks.
[Galaxy Tab S General] jeffreycentex:
External SD doesn't work in Recovery or the ROM. I think it just isn't being mounted, but I don't know what the mount point should be and I don't see it in the dmesg output...

Since this is Cyanogenmod, make sure you also download a GAPPS package that will give you the Google Apps (including market).
[Galaxy Tab S General] eousphoros:
To expand on this a little bit neither the internal sd nor the external are currently mounting automatically. I just bought a sd card today to test that out. It is next on my list.
[Galaxy Tab S General] enaybee:
I have been following the progress on this thread and this is the first time I have realized how much effort and time goes into porting a ROM to a new hardware. Previously for more popular devices, I would go to the device forum and see a plethora of roms already available for flash with guide and tuts. This time around I have been following the forums of this brand new device and can see how the things are built and developed bit by bit by developers like you. I commend all developers' efforts and hard work wholeheartedly. [MENTION=2346758]eousphoros[/MENTION] major props to you sir and I can't thank you enough.
[Galaxy Tab S General] eousphoros:
Internal/external sdcard is now mounting automagically. Uploaded release 4.1 to the OD thread.
[Galaxy Tab S General] edan1979:
the dedication to make it work are marvellous :good::good::good::good:
[Galaxy Tab S General] Lostatsea23:
Just got this tablet, reading all of this is so exciting !
[Galaxy Tab S General] zelduy:
Is it possible to turn of the soft/capacitive button when I'm in cyanomogen? Because i came from nexus 7 2013.. and the soft button really annoys me.. since i always accidentally pressed the button in landscape mode...
[Galaxy Tab S General] Enddo:
[IMG="Feels"]http://x1.fjcdn.com/comments/Damn+that+s+sad+man+_128e0cad8f1416f87ec8f2a4dda1103f.png[/IMG]
[Galaxy Tab S General] eousphoros:
D/GpsLocationProvider( 2662): NTP server returned: 1407135279726 (Sun Aug 03 23:54:39 PDT 2014) reference: 20649 certainty: 194 system time offset: -1658 (Needed to add the gps package and configuration files to the build, nothing special)

GPS is looking good and I have all the keys functioning now (Previously the app switching key was non-functional). The CM build process was ignoring the copy_file I was doing for Generic.kl so I moved those to sec_touchkey.kl and the issue was resolved.

I'll wait till I have bluetooth working for the next release unless someone really wants me to cut one off these changes.
[Galaxy Tab S General] Enddo:
I think most of us are waiting patiently so you can focus on what you think is best
[Galaxy Tab S General] eousphoros:
Release 5 is going up now. Unfortunately no bluetooth (It is getting further along in the init process but its getting a TIMEOUT in the final bringup)

This also was completely built out of repo sync. All of the little hacks I was doing initially have been removed and able to successfully build from a clean checkout.
[Galaxy Tab S General] Guitarfreak26:
Is there any chance of porting this to the 10.5 lte model? Love the tab but really dislike TW

congratulations on the great work though
[Galaxy Tab S General] eousphoros:
Unfortunately due to the wife losing patience with all the time I have dumped into this combined with not having the 10.5 LTE its unlikely. If someone were to send me one, I could give it to the wife and probably make that justification. ;)

Also of note, I got the 3.10 android kernel booting with display. A ton of stuff is broken so I will probably hold off till I have the current dev track done and moved to official, then start a separate 3.10 project.
[Galaxy Tab S General] acasserole:
eousphoros - Firstly great job on the CM on the Tab S 8.4 and it is the main reason I am considering getting one (I'd like to be able to remove TW if I dislike it and have performance issues) and sole reason I signed up to xda .

I was wondering if at any stage in the development you were going to add the figure print scanner unlock feature as this does seem like a useful thing and not TW clutter?
[Galaxy Tab S General] eousphoros:
Damn, samsung should hook me up with how many galaxy tab s's I am helping them sell. ;)

Anyways the fingerprint scanner is a possibility but its really low on my list of things I personally want to get working. No promises but it might happen.
[Galaxy Tab S General] mitchellvii:
I hope the missus will be patient just long enough for you to pop out the 10.5 wifi though :)
[Galaxy Tab S General] eousphoros:
The new 10.5 build will basically just be the same as the 8.4 but with a different kernel def file which I already have setup. No promises it will be any better then the last build though.
[Galaxy Tab S General] mitchellvii:
Well hopefully all the cool 8.4 stuff will work on the 10.5. :)
[Galaxy Tab S General] eousphoros:
You will have to let me know :)
[Galaxy Tab S General] mitchellvii:
Just let me know when its ready and I'll give er a flourish :)
[Galaxy Tab S General] PewPewK:
I'd love to see it, too, but I totally understand its low priority. Please keep up the great work!