yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S General] jeffreycentex:
This is a "is it just me questions", but does the volume get very distorted for anyone else? I know it is mono only, but playing music on anything over 30% sounds like it wants to break the speakers. I tried different EQ's to no avail. Anyone else see anything like this...

Headphone/BT is fine.

Only other issues are lingering crashes in GPS (already posted about - gpsd segfaults) and Spotify wanting to crash after running for more than a hour..
[Galaxy Tab S General] eousphoros:
Fwiw, the t800 image is using the stock kernel

Also of note I have CM compiling now with gcc 4.9 and booting to the same point I was at with release 6. Going forward all builds will be using 4.9 with specific BIG.little optimizations.
[Galaxy Tab S General] Enddo:
I'm excited
[Galaxy Tab S General] suzook:
Thats awesome! I think???? LOL. So what does this mean in english?:o
[Galaxy Tab S General] xda0996:
Excellent, i've been pretty extensively testing your current build (10.5) with a bunch of different games, apps etc and been pretty impressed how stable it is. I've only had crashes in one game (and i'm not convinced the ROM is to blame) and overall performance has been pretty good.

Just some useful feedback:

There was another user posting about distorted sound - I haven't had any noticable issues (Well not any worse then stock)

I did notice the auto-brightness wasnt working and i think it did in the earlier build?

The screen "glitching" when going from portrait to landscape mode is often visible when switching between apps (The preview images)

It has actually worked properly with a number of apps that the stock rom has issues with! (Afew games weren't scaling/detecting the right screen res/dpi with the stock rom)

and just for the record my (obviously unsupported!) TWRP is still flashing fine.

(Only posting this here as i still cant post in the development section)
[Galaxy Tab S General] Enddo:
I think it means...tablet = faster
[Galaxy Tab S General] qcjulle:
I just finished installing CM11 milestone 9 to my girlfriend's Tab Pro 8.4 and the difference in smoothness and responsiveness is night and day when compared to my own Tab S 8.4. Apart from a few quirky crashes with Google Play no major issues. The Tab S truly needs some CM love to realize it's potential so please keep up the good work. If someone can get CM11 working for the 8.4 LTE there is surely $20 in it from me :)
[Galaxy Tab S General] kenkiller:
Yeah.....T705 soon we hope? :D
[Galaxy Tab S General] eousphoros:
I'm sorry, after my limited experience porting my build to the t800 I doubt that will come from me. However if someone else wanted to pick up that port, I would be happy to answer questions. It would also be great if someone could pick up the t800/805 as well.

Unfortunately for me the reality of the situation is without these devices in hand it just takes too much time and peoples expectations are a bit, high, for my personal level of expertise. Cm11 is the first ROM I have ported, and the first ROM I've done. I just wanted to share my work since I have used many ROMs from this site on previous devices and figured it was time I contributed back.

As for my background I am just a lowly systems administrator. So this whole process has been a wonderful learning experience and provided a great opportunity to work on something technical that isn't related to serving web pages.

To wrap this up release 7 has been posted. This is primarily a performance build where I am seeing 7% gains over stock and about 15% gains over release 6 in 3dmark. Camera has made some progress but unfortunately it is causing a crash in mediaserver that I still need to nail down.
[Galaxy Tab S General] Enddo:
Very cool. I can't wait to try out the latest update. Thank you again for all your effort :highfive:
[Galaxy Tab S General] kenkiller:
No worries. I understand how being a chef here can be a PITA at times. :D Keep up the good work!

Now we need a multi rom solution so that I can see how fast this 2nd rate hardware can run CM. :(
[Galaxy Tab S General] eousphoros:
D/WVCdm ( 2256): Instantiating CDM.

I/WVCdm ( 2256): Level3 Library Nov 20 2013 18:09:31

E/wv_dash ( 2256): s5p-smem open error!!. errno(13)

E/wv_drm ( 2256): Fail to open secmem.

E/wv_drm ( 2256): Fail to allocate buffer.

E/wv_dash ( 2256): crypto mem init fail

W/WVCdm ( 2256): Could not initialize L1. Falling Back to L3.

I/WVCdm ( 2256): CdmEngine::QueryStatus

I/OMXClient( 5438): Using client-side OMX mux.

Poking a little bit at widevine drm tonight. Unfortunately this is the black box of black boxes.
[Galaxy Tab S General] Enddo:
I dunno what that means xD but
[Galaxy Tab S General] eousphoros:
Its OK, its like pretty much every other issue I've encountered at first. I have no idea what it means. Finding out what it means is half the fun. :)
[Galaxy Tab S General] Laykun:
Hey man, I'd be happy to pick up the SM-T800 port if you like. I assume there's a git repo for this?
[Galaxy Tab S General] suzook:
Awesome! Anxiously awaiting!
[Galaxy Tab S General] eousphoros:
I added two more repos

https://github.com/eousphoros/android_vendor_samsung_klimtwifi.git

https://github.com/eousphoros/android_hardware_samsung_slsi_exynos5-insignal.git
[Galaxy Tab S General] thakrage:
Are you still developing this ROM for T700? :)
[Galaxy Tab S General] eousphoros:
I'm not sure. After diving into the depths of cyanogenmod and seeing what monsters lay there I have been toying around with some other ideas that don't revolve around CM. Again if anyone wants to contribute/take over/etc I am willing to cede the reigns.

Ultimately I will have a rom I end up maintaining. It may very well be CM but in order for me to be happy I will have to rip out a good chunk of the foundation and replace it.

In that vein I have AOSP building and booting. Though I am going to hold off releasing it until iIve decided thats the direction I want to go. Since I may end up not maintaining it. Thanks to jball for providing the motivation to try it out.
[Galaxy Tab S General] Enddo:
It's like music to my ears

AOSP > CM

:D

Either way, thank you for the time you have put into this project
[Galaxy Tab S General] eousphoros:
It's a fun project that's for sure and thank you for being patient. Grumble build.prop grumble.

Ooh, the more I am poking at AOSP, the more I am getting a feeling this is where I am going to head. I have everything pretty much working now compared to where I was at with release 6. Haven't tested performance yet but it seems just as quick as release 7.

Antutu comes on par with release 7. Video seems to be working. (MX player included). And the rest, wifi/sound/etc.
[Galaxy Tab S General] Enddo:
Do you think this AOSP has been quicker to build because it's easier than CM or is all the work you put into the CM build helping out with getting the AOSP features working

edit - just saw your edit. do you have stereo sound working or mono sound again?
[Galaxy Tab S General] eousphoros:
Aosp lacks a lot of the candy cm has in the build system and definitely found a few bugs that cm has fixed for me. So that being said only reason I was able to get it up so fast is the majority of work I did for cm was able to be translated without much effort to aosp.

Sound is still mono thru the builtin speakers, everything else is stereo. Oops bluetooth is busted in AOSP. So not quite the same.

Now to consider my options. Continue working on cyanogenmod, ripping out a bunch of the underlying libraries (Including bionic) or work with AOSP fixing bugs that are already fixed in CM.
[Galaxy Tab S General] thakrage:
For me it doesnt matter which one you end up maintaining. Im just happy to get rid of touchwiz!
[Galaxy Tab S General] qcjulle:
I don't think many people would have problems with either, just as long as we get rid of Touchwiz :) Please keep up the good work.
[Galaxy Tab S General] kenkiller:
My vote is for CM. Their themes system is nice. :D

AOSP is just too bland imho.
[Galaxy Tab S General] xda0996:
Personally I like CM but which ever way you go - it's better than stock and I hope you can port it to the 10.5! Even on the 10.5 with your current build, it fixes some app compatibilty issues i had and its more usable than stock. Thanks again for all your hard work!
[Galaxy Tab S General] eousphoros:
From a functionality standpoint I agree. CM definitely has more bells and whistles out of the box. Though now that I know about the beasts laying underneath the pretty skin (Ancient libraries, weird optimizations that don't work well on exynos, etc) I think I have settled on AOSP and will build in the customization I like.
[Galaxy Tab S General] revthanki:
Great!

And we shouldn't underestimate the power of Xposed + Gravitybox either. (A nice property of that system is the natural evolutionary process of Android updates that weed out the out-of-date modules - whereas the problem with CM and Touchwiz seems to be that they bend the Android framework to accommodate their prized modules)
[Galaxy Tab S General] stoehner:
Anyone have luck using TWRP yet?
[Galaxy Tab S General] eousphoros:
Here is release 1 of BLCKASOP. Has a few things working that release 7 was missing (Netflix is the big one). I think I finally nailed the DRM issue. This is build from 4.4.4r2 aosp and very early, but I have had a few very excited individuals and I hate to disappoint.

Most of the major things seems to be working but again. No promises. This will cause your tablet to break.

Oh and disable recovery update or this will update your recovery with the stock one. Still need to track that little bugger down.

https://blck.io/blckasop_r1.zip
[Galaxy Tab S General] jball:
Awesomeness !!!!!

Edit : Flash SuperSU before you reboot

Nexus 5 via Tapatalk
[Galaxy Tab S General] revthanki:
Look forward to trying this, but how do I disable recovery update? There's no such option in TWRP at least...
[Galaxy Tab S General] jball:
This is how its meant to run.these cores are loving this light system

Nexus 5 via Tapatalk
[Galaxy Tab S General] revthanki:
Some notes:

- To prevent recovery flash I unzipped, found the file install-recovery.sh in recovery/etc and removed the line starting:

applypatch -b /system/etc/recovery-resource.dat...

The good

- 1440p YouTube plays perfectly

- smooth UI

- default screen calibration looks excellent

- no random force closes at all

- initial batch of apps tried function great

- system goes into deep sleep well

The bad

- the not-unpleasant rotation glitches are still here!

- location services (both GPS and Wi-Fi) borked

- Bluetooth seems to connect, but music comes monaurally from the top tablet speaker

- long-press recents isn't mapped to the menu key (no easy way of getting into the menu in apps such as TB - the simplest thing to fix here probably :) )

- auto brightness not working

- camera frazzled (so no photographs during lectures/presentations)

- compass not working

- capacitive keys wake device from sleep!

Such a fantastic start [MENTION=2346758]eousphoros[/MENTION] , thank you!
[Galaxy Tab S General] suzook:
What's the possibility of flashing this to my t800 with the stock t800 boot.IMG? Any thoughts?
[Galaxy Tab S General] lonespeaker:
I'd be interested in knowing this too. I've build asop a few times for personal use but I'm no developer like [MENTION=2346758]eousphoros[/MENTION] though. Maybe once everything is on git I might give it a go for the t800 and see if I can get it to work or not.

Thanks to [MENTION=2346758]eousphoros[/MENTION] for doing all this great work!
[Galaxy Tab S General] xda0996:
Thought i'd give this ago seeing as people were curious!- Tried afew different things, removed the auto recovery update, changed the boot.img and had play with the installer but i couldnt get it to install - got a symlink error in the end. Abit short on time today so didnt get a chance to look into it any further so hopefully someone else can have a play with it. This was with TWRP so not sure if this makes any difference.
[Galaxy Tab S General] eousphoros:
You would probably have better luck taking the kernel out of the release 6 I did for the t800.. extracting this release 1.. replacing the zImage and mkbootimg boot.img zip blah.zip.. etc. etc.
[Galaxy Tab S General] suzook:
Gonna give this a shot later. I will keep you guys updated.
[Galaxy Tab S General] xda0996:
yeah let me know how you go, it's a shame that T700 and T800 are just different enough that the ROMs don't work... I was stupid/adventurous enough to play with some T700 roms a week ago just to try and figure out what the difference was - at one stage the tablet was responding like it had booted but I had no display.
[Galaxy Tab S General] jball:
DPI maybe? Between T700 to T800

Nexus 5 via Tapatalk
[Galaxy Tab S General] eousphoros:
DPI is the same. Its something in the kernel. Haven't bothered tracking it down yet.
[Galaxy Tab S General] xda0996:
Yeah definately, i dont really know enough about the kernel side of things to investigate further myself.

If anyone is curious, I got a garbled the boot screen about a second after power up, then the soft buttons went dim and the screen went black. Tab was responding to power/volume controls and vibrating but couldnt get much else happening.
[Galaxy Tab S General] svardman:
Iḿ trying to build cm11 from eousphoros sources and it always stops here:

/home/christer/android/external/busybox/applets/applet_tables.c:144:9: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]

fgets(line_old, sizeof(line_old), fp);

^

GEN include/usage_compressed.h

GEN include/applet_tables.h

HOSTCC applets/usage_pod

CC applets/applets.o

LD applets/built-in.o

make[1]: Lämnar katalogen "/home/christer/android/external/busybox"

christer@AspireV5:~/android$

Does someone have any suggestion what it can be?
[Galaxy Tab S General] bunnyy:
Brother did you find the solution for this?? I'm facing the same problem. Please help
[Galaxy Tab S General] eousphoros:
A little more good news, http://hardkernel.com/main/products/prdt_info.php?g_code=G140448267127&tab_idx=3. Looks like there is an ODROID coming out based on the 5422 (Which shares the mali gpu, vs the 5410 which uses a powervr gpu) and which is where some of the code for the samsung galaxy s4 i9500 (5410) comes from (http://hardkernel.com/main/products/prdt_info.php?g_code=G137510300620)

The bad news is the code isn't scheduled to be released till middle of october so in the near term doesn't provide any benefit.

EDIT: Just found this http://www.arndaleboard.org/wiki/index.php/O_resource#Installing_Repo which uses the same soc. Checking it out now.
[Galaxy Tab S General] eousphoros:
I/SurfaceFlinger( 3041): SurfaceFlinger is starting

I/SurfaceFlinger( 3041): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

D/libEGL ( 3041): loaded /vendor/lib/egl/libGLES_mali.so

I/gralloc ( 3041): using (id=)

I/gralloc ( 3041): xres = 1600 px

I/gralloc ( 3041): yres = 2560 px

I/gralloc ( 3041): width = 113 mm (359.646027 dpi)

I/gralloc ( 3041): height = 180 mm (361.244446 dpi)

I/gralloc ( 3041): refresh rate = 60.22 Hz

D/libexynosv4l2-subdev( 3041): try node: /dev/v4l-subdev0, minor: 0

D/libexynosv4l2-subdev( 3041): try node: /dev/v4l-subdev1, minor: 1

D/libexynosv4l2-subdev( 3041): try node: /dev/v4l-subdev2, minor: 2

D/libexynosv4l2-subdev( 3041): try node: /dev/v4l-subdev3, minor: 3

D/libexynosv4l2-subdev( 3041): try node: /dev/v4l-subdev4, minor: 4

D/libexynosv4l2-subdev( 3041): try node: /dev/v4l-subdev5, minor: 5

I/libexynosv4l2-subdev( 3041): node found for device s5p-mixer0: /dev/v4l-subdev5

I/libexynosv4l2-subdev( 3041): open subdev device /dev/v4l-subdev5

D/HWCService( 3041): static android::ExynosHWCService* android::ExynosHWCService::getExynosHWCService()::

D/HWCService( 3041): ExynosHWCService Constructor is called

D/HWCService( 3041): int android::ExynosHWCService::createServiceLocked()::

EDIT:

I/hwcomposer(12506): unblank ioctl failed (display already unblanked)

E/hwcomposer(12506): ioctl S3CFB_WIN_CONFIG failed: Not a typewriter

F/hwcomposer(12506): ioctl S3CFB_WIN_CONFIG failed to clear screen: Not a typewriter

Looks like I am doing something bad in hwcomposer (Verified the problem exists in both my custom kernel and the official one). Though I am fully booting now other then the display so thats exciting. :)
[Galaxy Tab S General] diegosolor:
you are my hero
[Galaxy Tab S General] jeffreycentex:
I would hope that the sensor setup would be similar to the Pro line...
[Galaxy Tab S General] eousphoros:
CM has been ported to a couple exynos devices already (even some 5 series) including the galaxy s4.

https://github.com/CyanogenMod/android_device_samsung_i9500/
[Galaxy Tab S General] mitchellvii:
Excellent. That's great news.
[Galaxy Tab S General] Freakstyler:
The link you give is for the S4 Exynos 5410 with a PowerVR GPU, the Exynos 5420 etc, uses the Mali T628 MP4 GPU, and thus completely different and not compatible sources unfortunately.
[Galaxy Tab S General] Poser:
Part of the problem is the 5410 used a power vr graphics solution....our 5420 uses a Mali t628 solution. Otherwise a lot of the work would be more straightforward (though no easier)
[Galaxy Tab S General] eousphoros:
Yes, we covered this a couple pages back. I was just highlighting for the audience who have not read the entire thread that this is not the first port of cm to an exynos soc.

EDIT: In other news I tracked down an ioctl error that had been plaguing me to bionic. Progress!
[Galaxy Tab S General] eousphoros:
~/android/system/bootable/recovery/etc/init.rc <append to end of file>. Useful for debugging without having to reboot

----

on property:eous.enable=0

stop healthd

stop zygote

stop media

stop surfaceflinger

stop drm

stop servicemanager

on property:eous.enable=1

export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

export LD_LIBRARY_PATH /vendor/lib:/system/lib

export ANDROID_BOOTLOGO 1

export ANDROID_ROOT /system

export ANDROID_ASSETS /system/app

export ANDROID_DATA /data

export ANDROID_STORAGE /storage

export ASEC_MOUNTPOINT /mnt/asec

export LOOP_MOUNTPOINT /mnt/obb

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/telephony-msim.jar

start healthd

start zygote

start media

start surfaceflinger

start drm

start servicemanager

service servicemanager /system/bin/servicemanager

class core

user system

group system

critical

onrestart restart healthd

onrestart restart zygote

onrestart restart media

onrestart restart surfaceflinger

onrestart restart drm

service healthd /sbin/healthd

class core

critical

seclabel u:r:healthd:s0

service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server

class main

socket zygote stream 660 root system

onrestart write /sys/android_power/request_state wake

onrestart write /sys/power/state on

onrestart restart media

onrestart restart netd

service surfaceflinger /system/bin/surfaceflinger

class main

user system

group graphics drmrpc

onrestart restart zygote

service drm /system/bin/drmserver

class main

user drm

group drm system inet drmrpc
[Galaxy Tab S General] stamatis:
Thread cleaned.

[MENTION=2346758]eousphoros[/MENTION] if you still want the thread to be closed let me know. Otherwise update the first post.

Thanks.
[Galaxy Tab S General] eousphoros:
Bad news, this was a bit premature. Bionic was using an older set of cleaned kernel headers that were missing a few things but it didn't end up resolving the ioctl issue I am having with /dev/graphics/fb0. Has samsung released the libhwc 1.3 stuff or is 1.1 current?

EDIT: need more coffee
[Galaxy Tab S General] jeffreycentex:
Does this help?

http://code.metager.de/source/xref/android/4.4/hardware/samsung_slsi/exynos5/libhwc/

I'm a sofware dev, but never have done hardware side work, but I'll take a look at things and see what I can figure out...
[Galaxy Tab S General] eousphoros:
2161 dev->base.common.version = HWC_DEVICE_API_VERSION_1_1;

Unfortunately that is 1.1

And thank you. Glad to have someone else joining the cause. :)
[Galaxy Tab S General] jeffreycentex:
Doesn't look like there is a 1.3.... :(
[Galaxy Tab S General] eousphoros:
Yeh, that was my result as well. If anyone has experience requesting code from Samsung or has contacts, an updated dump for the 5420 (including libhwc and gralloc) would be a huge win.

EDIT: Interesting writeup on hwcomposer from linaro. https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/HwcKms
[Galaxy Tab S General] mitchellvii:
You might want to try www.experts-exchange.com for a free trial and ask there. I have found this to be a very helpful community of IT experts. Helped me with coding issues countless times.

---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------

PM [MENTION=309990]freeza[/MENTION]. If anyone knows he does.
[Galaxy Tab S General] jeffreycentex:
I'm noting that MIUI support the Galaxy Note 3 Exynos version, which is very similar to ours (Mali GPU, Exynos 5422). Does anyone know where to find their device setup files?
[Galaxy Tab S General] eousphoros:
https://github.com/MiCode?page=1

Not seeing much here though
[Galaxy Tab S General] jeffreycentex:
Yeah.. They have it hidden...

This is the thread referencing it: http://xdaforums.com/galaxy-note-3/.../rom-miui-rom-v5-4-7-11-kitkat-4-4-2-t2813177

It's closer to AOSP than TW...
[Galaxy Tab S General] jeffreycentex:
Here is the device tree for the Note 3. I don't know if it works...

https://github.com/flashka07/android_device_samsung_ha3g

But nothing new on libhwc...
[Galaxy Tab S General] eousphoros:
Potentially good find. I'll dig thru the repo and see what I can scavenge. Is this guy on XDA?
[Galaxy Tab S General] jeffreycentex:
I think this is him. Not much recent history...

http://xdaforums.com/member.php?u=4345368
[Galaxy Tab S General] eousphoros:
Did some more hacking to isolate this ioctl issue. The biggest thing that I tried was moving to androids pixelflinger gles (software rendering) driver instead of the mali.

01-03 02:18:28.750 5796 5796 E hwcomposer: ioctl S3CFB_WIN_CONFIG failed: Not a typewriter

01-03 02:18:28.750 5796 5796 F hwcomposer: ioctl S3CFB_WIN_CONFIG failed to clear screen: Not a typewriter

So its really screaming hwcomposer atm. Though I am waiting for my build with that other repo you found, hopefully that will shed some light on this.

EDIT just to clarify those ioctls are happening against /dev/graphics/fb0. Confirmed by strace.
[Galaxy Tab S General] eousphoros:
http://pastebin.com/n4ixn78J

The link above is the full strace. The important bit is

open("/dev/mali0", O_RDWR) = 13

open("/dev/graphics/fb0", O_RDWR) = 22

ioctl(13, 0xc0288201, 0xbec93920) = 0

ioctl(13, 0xc0288200, 0xbec93850) = 0

mmap2(NULL, 258048, PROT_READ|PROT_WRITE, MAP_SHARED, 13, 0x106ac9) = 0xb22e2000

clock_gettime(CLOCK_MONOTONIC, {843, 393553654}) = 0

ioctl(22, 0x40e046d1, 0xbec93a50) = -1 ENOTTY (Not a typewriter)

writev(16, [{"\6", 1}, {"hwcomposer\0", 11}, {"ioctl S3CFB_WIN_CONFIG failed: N"..., 48}], 3) = 60

ioctl(22, 0x40e046d1, 0xbec93a50) = -1 ENOTTY (Not a typewriter)

writev(16, [{"\7", 1}, {"hwcomposer\0", 11}, {"ioctl S3CFB_WIN_CONFIG failed to"..., 64}], 3) = 76