yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S General] UpInTheAir:
I have flashed this T700 ROM onto my T705 for kernel testing purposes only.

I am unable connect via MTP or PTP to my Windows 8.1 on Ubuntu 14.04 or 12.04 PCs. I have tried with "stock" and my own SkyHigh kernels

Drivers should be ok, as they were just working with my stock ROM on all PCs.

Is this problem experienced by any other T700 or T705 user ?

I'm going to flash back to Stock to just re-confirm..........
[Galaxy Tab S General] suzook:
Its not your kernel, its a problem with the ROM.
[Galaxy Tab S General] UpInTheAir:
Thanks for the quick reply :)

If you can make your 10.5 ROM Port GPL and XDA compliant, I'd like to help you by building a kernel for your users. I just need some more testing on the T700 version first ;) All going well so far :) Synapse is in full flight !
[Galaxy Tab S General] suzook:
I'm not a developer. All I did to get 10.5 working was replace the WiFi folder, and the boot.IMG on eousphoros ROM. I would love to compile a kernel, but sure its way out of my league. Thanks anyway.
[Galaxy Tab S General] UpInTheAir:
I meant that I'll do it for you ;)

Well.

1. All you need is permission of the Dev to officially redistribute his ROM port as a 10.5 version and link the sources etc to his.

2. As for the kernel, same with where you got the kernel. Just ask for permission and if it's compiled from source, well need the link to it.

3. Start your thread in GENERAL section or confirm with moderator that is in the right place.
[Galaxy Tab S General] killall:
I'm at work at the moment so can't check, but are you sure it doesn't work, I'm using a T700 and I could swear MTP was working the other day.
[Galaxy Tab S General] suzook:
Oh, OK. I misunderstood about the kernel. I'm positive eousphoros has no issues with me making the 10.5 port of his ROM, but the boot was from lonespeaker who hasn't been around in a while. I was just trying to help some 10.5 users out, but i do now understand there are rules.
[Galaxy Tab S General] UpInTheAir:
Mtp & ptp mounting fixed

MTP & PTP mount are both fixed !!!!!! :victory:

Kernel source needed patching. Will share and upload commits to github when I release SkyHigh T700 CM Port kernel :good:

---------- Post added at 08:18 PM ---------- Previous post was at 07:46 PM ----------

I've started a seperate SkyHigh kernel thread for CM Ports here:

[KERNEL] [CM PORT] [07 Sept] SkyHigh TW Kernel [R3_vXX] [Synapse ++]

I might have something for release tomorrow, had enough for today ;)
[Galaxy Tab S General] Turbojugend:
This is exciting news. Does this mean Suzook you can post the rom with the stock kernel for now?
[Galaxy Tab S General] lonespeaker:
The kernel I compiled is a stock samsung one with no modifications bundled with the ramdisk from eousphoros to make a boot.img. What I want to do is compile CM11 for the 10.5 natively so to fix the various issues we have native to the 10.5 and also to contribute to help [MENTION=2346758]eousphoros[/MENTION] move forward with the build for both devices. But time is not something I have a great deal of time of and I don't want to promise things or put myself under pressure.

I'm going to do it anyway in my spare time and if I get a 10.5 build running before anyone else does, I'll speak to [MENTION=2346758]eousphoros[/MENTION] about starting a 10.5 thread. first I need to find a good guide to setup android cm dev system on osx to save me some time.
[Galaxy Tab S General] Turbojugend:
I have a PC rig that I only use for gaming, so if anybody wanted to give me a quick rundown of compiling, I would be more than happy to give it a shot for us 10.5 users.
[Galaxy Tab S General] bruiselee:
does this work for T705?
[Galaxy Tab S General] jodvova:
Has anyone tried to build a kernel with Linaro 4.9.2 toolchain ?

I tried to build a stock Samsung one but the tablet doesn't boot.

If I build a kernel with android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 toolchain, it boots ok.
[Galaxy Tab S General] jball:
Linaro or Franco would definitely be nice

Nexus 5 via Tapatalk
[Galaxy Tab S General] UpInTheAir:
Yes, but device won't have mobile network connectivity.
[Galaxy Tab S General] UpInTheAir:
SkyHigh kernel UP :)

SkyHigh kernel is now released for T700 WIFI CM Port ROM :)

http://xdaforums.com/galaxy-tab-s/orig-development/kernel-skyhigh-kernel-t2870143
[Galaxy Tab S General] ggreenw:
I was able to get CM working on my 10.5 by simply taking the boot.img and system/etc/wifi folder from the r10.1 port released several days ago and using 7zip to replace them into the new CM11 rom. I also had to change the updater-script to reflect chagallwifi instead of klimtwifi to get it to install. I also modified the build.prop but not sure if that was really necessary. Everything seems to be working great except for 5ghz wifi, still can't figure that one out...
[Galaxy Tab S General] jodvova:
I have its building fine with Linaro (had to fix some warnings in the code), but the kernel won't boot :( not sure how debug it.
[Galaxy Tab S General] touchee:
Does your microphone work please? I have same setup as yours (thanks to suzook) but microphone still dead on my T800.
[Galaxy Tab S General] jodvova:
It doesn't work.
[Galaxy Tab S General] pegasus21:
It seems like I'm almost done with building the rom from source. I had to figure out a couple of things that prevented building it.

Right now I'm stuck with trying to get the kernel to build inline. I can build the kernel standalone but it seems like an Android.mk is required to build it inline.

[MENTION=2346758]eousphoros[/MENTION], is the Android.mk file in the kernel directory the way to go with your source because it isn't in the Git so I'm wondering if you are building your kernel inline or via prebuilt.

*Edit* I guess the other way instead of an Android.mk inside the kernel directory is to use a core/task/kernel.mk (Which is probably what you were telling me about in the earlier post) to build it inline. But if that's the case, I shouldn't be building the rom against the AOSP Android sources but the Cyanogenmod sources (ie git://github.com/CyanogenMod/android.git)?
[Galaxy Tab S General] ggreenw:
Nope sorry mic is not working i forgot about that one. I don't really use it but one day I might want it for Skype or hangouts so hopefully we can figure it out but for now I don't know if it's a deal breaker because this is just SO MUCH FASTER and smoother than TW.
[Galaxy Tab S General] eousphoros:
Just to be clear, the mic works fine on the t700, I've said this before, you probably need to update mixerpaths.XML for your device. As for the lkernel if you are doing aosp do a prebuilt.
[Galaxy Tab S General] touchee:
Can you be a bit more specific please? Previously I have looked at other TW roms hoping to get an idea as to what needs editing for a working T800 mixer_paths.xml but found nothing. Not sure what needs updating in the file?
[Galaxy Tab S General] eousphoros:
This is already covered in the thread. People need to be more self-sufficient. I don't own a t800 but on the t700 there is a /system/etc/tinyucm.conf you need to compare against the mixer_paths.xml
[Galaxy Tab S General] moreroid:
Hi eousphoros

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

used

$Attribute Section: aeabi
File Attributes
Tag_CPU_name: "ARM v7"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch: VFPv3
Tag_Advanced_SIMD_arch: NEONv1
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: SP and DP
Tag_ABI_optimization_goals: Aggressive Debug
Tag_CPU_unaligned_access: v6
Tag_MPextension_use: Allowed
Tag_DIV_use: Allowed in v7-A with integer division extension
Tag_Virtualization_use: TrustZone and Virtualization Extensions

why not using

Attribute Section: aeabi
File Attributes
Tag_CPU_name: "ARM v7"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch: VFPv4
Tag_Advanced_SIMD_arch: NEONv1 with Fused-MAC
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: SP and DP
Tag_ABI_optimization_goals: Aggressive Speed
Tag_CPU_unaligned_access: v6
Tag_MPextension_use: Allowed
Tag_DIV_use: Allowed in v7-A with integer division extension
Tag_Virtualization_use: TrustZone and Virtualization Extensions

We have support for VFPv4 or is there something I miss?

$ grep Features /proc/cpuinfo
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
[Galaxy Tab S General] eousphoros:
Oops, forgot to modify the arch build prop file so just ended up building it with the stock armv7-a-neon profile. Good catch, btw what tool did you use to get that information?

EDIT: Cutting a new release now with the slightly more optimized build flags (Should help floating point performance). Also took a quick stab at a hwcomposer fix. No promises though.
[Galaxy Tab S General] moreroid:
(This post should belong to development section, but I have a low post count, so can't post there)

To your question:

$ readelf -A <binary>

Don't know if armv7a-neon is enough because VFPv3(neon) vs VFPv4(newer) [see android-ndk/sources/android/cpufeatures/cpu-features.h]

taken from Android NDK r10 (may changed with newer release), default flags for armeabi-v7a:

$ mkdir -p /tmp/jni && \
echo '$(info TARGET_CFLAGS=$(TARGET_CFLAGS)) $(info TARGET_CXXFLAGS=$(TARGET_CXXFLAGS)) $(info TARGET_LDFLAGS=$(TARGET_LDFLAGS))' >/tmp/jni/Android.mk && \
ndk-build NDK_TOOLCHAIN_VERSION=4.9 NDK_PROJECT_PATH=/tmp APP_ABI=armeabi-v7a
TARGET_CFLAGS=-fpic -ffunction-sections -funwind-tables -fstack-protector -no-canonical-prefixes -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
TARGET_CXXFLAGS=-fpic -ffunction-sections -funwind-tables -fstack-protector -no-canonical-prefixes -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp -fno-exceptions -fno-rtti
TARGET_LDFLAGS=-no-canonical-prefixes -march=armv7-a -Wl,--fix-cortex-a8

This is not perfect for UNIVERSAL5420, better these according to /proc/cpuinfo

TARGET_CFLAGS=-fpic -ffunction-sections -funwind-tables -fstack-protector -no-canonical-prefixes -mcpu=cortex-a15 -mtune=cortex-a15.cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=softfp -mthumb
TARGET_CXXFLAGS=-fpic -ffunction-sections -funwind-tables -fstack-protector -no-canonical-prefixes -mcpu=cortex-a15 -mtune=cortex-a15.cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=softfp -mthumb -fno-exceptions -fno-rtti
TARGET_LDFLAGS=-no-canonical-prefixes -mcpu=cortex-a15 -mtune=cortex-a15.cortex-a7 -mfpu=neon-vfpv4 -Wl,--fix-cortex-a8

Options overriding possible by direct definition like $ ndk-build TARGET_CFLAGS=...

Yet no benchmarks to see if GCC4.9 is in a good shape.
[Galaxy Tab S General] eousphoros:
You wouldn't want to compile everything as thumb, some things are faster as -marm vs -mthumb. Though the flags I am using are

// conditionals removed

ARCH_ARM_HAVE_ARMV7A := true

ARCH_ARM_HAVE_VFP := true

ARCH_ARM_HAVE_VFP_D32 := true

ARCH_ARM_HAVE_NEON := true

arch_variant_cflags := -mcpu=cortex-a15 -mtune=cortex-a15

arch_variant_cflags += \

-mfloat-abi=softfp \

-mfpu=neon-vfpv4 \

-DHAVE_NEON=1 \

-DHAVE_VFP=1 \

-DHAVE_VFP_D32=1 \

-DHAVE_ARMV7A=1

arch_variant_ldflags := \

-Wl,--fix-cortex-a8

(The other flags are stock cm flags (-O2, -marm for arm, -mthumb for thumb, etc)

As for gcc4.9 I tried that earlier and I ran into way too many weird bugs and definitely don't have the time anymore to work thru them. (also I didn't see any performance benefit using the big.little mtune options in the 4.9 testing)

Here is the new build. Testing it now

Attribute Section: aeabi

File Attributes

Tag_CPU_name: "ARM v7"

Tag_CPU_arch: v7

Tag_CPU_arch_profile: Application

Tag_ARM_ISA_use: Yes

Tag_THUMB_ISA_use: Thumb-2

Tag_FP_arch: VFPv4

Tag_Advanced_SIMD_arch: NEONv1 with Fused-MAC

Tag_ABI_PCS_wchar_t: 4

Tag_ABI_FP_denormal: Needed

Tag_ABI_FP_exceptions: Needed

Tag_ABI_FP_number_model: IEEE 754

Tag_ABI_align_needed: 8-byte

Tag_ABI_enum_size: int

Tag_ABI_HardFP_use: SP and DP

Tag_ABI_optimization_goals: Aggressive Debug

Tag_CPU_unaligned_access: v6

Tag_FP_HP_extension: Allowed

Tag_MPextension_use: Allowed

Tag_DIV_use: Allowed in v7-A with integer division extension

Tag_Virtualization_use: TrustZone and Virtualization Extensions

Well it boots, running it thru its paces now. If it looks good I'll share this build. (I am not picking this back up as a project but this was a quick fix and something I meant to do originally). Last thing I will do is post a manifest.xml file for those looking to build and get the last few things into git. (Probably this weekend)

HWComposer still not happy, oh well. Uploading build now.

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

Assuming no one finds any new major bugs I'll update the other thread as well tonight.
[Galaxy Tab S General] suzook:
[MENTION=2346758]eousphoros[/MENTION]...could you point me in the direction of the 90degree off camera on the 10.5??? I would like to try and fix it for us 10.5 users. Thanks
[Galaxy Tab S General] eousphoros:
Unfortunately I don't remember where I saw this now. I spent a few minutes going thru my notes but it doesn't look like I ever wrote it down. I'm sorry :(
[Galaxy Tab S General] moreroid:
I expected that gcc4.9 is too newish. Ok, gcc4.9 source shows no much difference for -mtune=cortex-a15.cortex-a7

$ egrep '(CORE_NAME,|-a15)' gcc-4.9.1/gcc/config/arm/arm-cores.def
ARM_CORE(CORE_NAME, INTERNAL_IDENT, TUNE_IDENT, ARCH, FLAGS, COSTS)
ARM_CORE("cortex-a15", cortexa15, cortexa15, 7A, FL_LDSCHED | FL_THUMB_DIV | FL_ARM_DIV, cortex_a15)
ARM_CORE("cortex-a15.cortex-a7", cortexa15cortexa7, cortexa7, 7A, FL_LDSCHED | FL_THUMB_DIV | FL_ARM_DIV, cortex_a15)

Regarding -mthumb aka Thumb-2 for 5240. Let's look at outdated benchmark https://wiki.linaro.org/MichaelHope/Sandbox/CoreMark1.

Yes -marm is faster (in term of performance) but who says that performance per watt is also greater than in -mthumb mode?

For a mobile device I prefer better performance per watt over raw performance.

Maybe in the end of the day, interested users can run long-term comparison between both modes.

Anyway, no complains from my side, keep going with your time intensive work. gogogo :laugh:
[Galaxy Tab S General] eousphoros:
Like I said before my time to work on this has come to an end (At least for a couple months). You are welcome to pick up where I left off though I suggest you spend a little time understanding the code you are compiling instead of just throwing random flags across the board.
[Galaxy Tab S General] eousphoros:
https://blck.io/cm-11-20140912-UNOFFICIAL-klimtwifi.zip

Here is a build with the hwcomposer issue fixed.

Short version is I went back to the 1.1 code base which doesn't have the feature set of the hwcomposer 1.3 but now realizing I probably wont get back to this for awhile those missing features don't matter. So enjoy your hw overlays.
[Galaxy Tab S General] Turbojugend:
If anybody is still running blck_r10.1_t800 can you try Netflix and see if it works for you please?
[Galaxy Tab S General] eousphoros:
The current version of Netflix uses a DRM that doesn't play well with others. Try tracking down an older version and you might have better luck. Amazon prime should work just fine.
[Galaxy Tab S General] jball:
Try an older version Netflix and turn off auto update in your playstore settings so it won't override it after you install it.

Google for old versions

Nexus 5 via Tapatalk
[Galaxy Tab S General] palaiouras:
Hello pegasus21,

Have you any breakthrough regarding the 705 version?

Regards from Greece
[Galaxy Tab S General] jodvova:
It does not.
[Galaxy Tab S General] Turbojugend:
Grabbed this off of a link here, it works!! :D
[Galaxy Tab S General] eousphoros:
Your audio.primary library is crashing. If you are using mine that's usually the result of a bad mixer paths XML file.
[Galaxy Tab S General] pegasus21:
I see. I just ran a compare with your rom and yes the mixer_paths.xml is different. Based on that, I'm supposed to build the rom based on the aosp branch. I'll give it another go and see what happens.

Can you share which branch should I be using for your repositories in order to make the cm releases that you've been sharing lately? Thanks
[Galaxy Tab S General] eousphoros:
When we get out of the hospital and have had a chance to get some sleep I'll share the manifest.xml file I'm using. There are a couple hacks in the code base that I don't have commited like the inv_FD call the stock gralloc linked against that isn't standard. I'll try to track those down as well. Probably be next week. As for a general rule of them aosp is for device repo, cm11 or master for everything else.
[Galaxy Tab S General] pegasus21:
No problem. Take your time. Also, congrats on your wife's delivery!
[Galaxy Tab S General] suzook:
Op did amazing work, just can't believe another Dev hasn't taken it to the next level. The Dev support on this tab is horrible. I can only blame Samsung for releasing so many damn tabs. This truly is the best one though.
[Galaxy Tab S General] Turbojugend:
I am starting to notice video playback streaming issues on this tab too that are flawless on my Z2. I blame the chipset for the awful performance and complete lack of development.
[Galaxy Tab S General] Laykun:
So disappointing that this tablet doesn't get any love. Mind you I could take up the rom but who really wants to put up with nagging users or even really has the time?
[Galaxy Tab S General] killall:
Really? What is the point of this post?
[Galaxy Tab S General] brando56894:
Exactly, he's whining that there's "no love" for it, but then is like "I could do it but I don't want to put up with all of you..."

I may start to tinker around with it in a few weeks, my birthday is coming up and I'm going to tell my girl to get me 12 GB of RAM to throw in my system (for a total of 24 GB) so I can start compiling Android.
[Galaxy Tab S General] suzook:
Huh???? Wtf???
[Galaxy Tab S General] Laykun:
I interpret some of the posts by users as nagging. By no means is it the majority of users, but there is a subset of users that just nag for features and support. I couldn't deal with that, it just turns me right away. I have the skill set but not the tolerance or time commitment and I'm fine admitting that instead of starting a new thread for a ROM and never finishing it. Coming from the ASUS Transformer and Galaxy Note I know there are developers that possess these qualities and I'm surprised and also disappointed this tablet doesn't have more of their attention given the fantastic hardware potential. Time may change this, but extrapolating from the growth rate of development on this tablet it just doesn't seem likely in my opinion and this is where my disappointment stems from. It's not uncommon for this to happen to Samsung tablets as I also had the Galaxy Tab 8.9 for developing android apps at work. It was just too under-loved and barely received any custom ROMs due to it's popularity problems. Mind you I may not be privy to all development efforts for said tablet so I could very well be wrong, in fact I'd rather be wrong than right.

Eousphoros has all the qualities of an ideal developer and is a real stand out. I really appreciate the hard work he's put into his rom efforts.
[Galaxy Tab S General] brando56894:
That's all fine and dandy, but why something like that in the first place?
[Galaxy Tab S General] jball:
Yes but wouldn't the payoff be worth all the bug reports/complaints .how about all those that appreciate and still use this ROM as a daily driver regardless of the bugs just to have AOSP.if you have the skills and the skin than take the positive with the negative.

Nexus 5 via Tapatalk
[Galaxy Tab S General] mtdoughty:
Help building from source

Hi,

I've been trying to build this from source but I've got stuck!

make: *** No rule to make target `/home/mark/android/cm11/out/target/product/klimtwifi/obj/SHARED_LIBRARIES/libexynosutils_intermediates/export_includes', needed by `/home/mark/android/cm11/out/target/product/klimtwifi/obj/SHARED_LIBRARIES/libhwjpeg_intermediates/import_includes'. Stop.

Can anyone give me any pointers?

Many Thanks
[Galaxy Tab S General] jball:
Great job man.all is good
[Galaxy Tab S General] stoehner:
Do we need to flash GAPPS w/ this ROM?
[Galaxy Tab S General] PewPewK:
Love that we're getting development for the Tab S line. I was worried for a while we might never get a custom ROM.

Since we've now seemed to drop CM in favor of a more pure AOSP experience, I'm wondering if it'd still be possible to implement the CM Theme Engine? Well, I mean, I'm sure it's possible, but is it something you'd be willing to look into eousphoros, at some point? Obviously, there's a lot of stuff that comes ahead of that, but down the road?

Thanks for the great work!
[Galaxy Tab S General] stoehner:
+1 the CM11 theme engine is great, would love a port.
[Galaxy Tab S General] eousphoros:
No promises, right now I'm just focused on getting an MVP version of asop built with all the core functionality of the device in place. Then I can start thinking about shinys :)
[Galaxy Tab S General] stoehner:
Tried flashing this with TWRP...froze up. Is this cwm only? Thanks
[Galaxy Tab S General] eousphoros:
I only test with cwm
[Galaxy Tab S General] stoehner:
Ty
[Galaxy Tab S General] moseskim:
I installed it with the latest version of twrp and didn't have problems. It took a while though, but it finished.

Also, anyone have any Netflix workarounds? In saw on CM thread that using old versions might help - tried 3.4 and 3.6 with the same issues, which is stuck at loading screen.
[Galaxy Tab S General] Enddo:
Paranoid Android has ported the CM Theme engine to AOSP for Paranoid Android(it's running on my Nexus 5). I imagine they have the code on gerrit or something. I would think that most of the work is done, but I'm just assuming
[Galaxy Tab S General] PewPewK:
Right, which is why I'm not sure if it'd be that hard, but then again, I know very little about Android development.
[Galaxy Tab S General] jeffreycentex:
Or why not use the XPosed XThemeEngine module which supports AOSP.... I haven't tried it because I like the default theme, but it should work...
[Galaxy Tab S General] PewPewK:
Didn't realize there was an Xposed module for that. In that case, I'm good if it works.
[Galaxy Tab S General] jball:
Yes,Google pa gapps 4.4.4

---------- Post added at 07:50 AM ---------- Previous post was at 07:49 AM ----------

@eousphoros

You rock man
[Galaxy Tab S General] eousphoros:
Release 3

https://blck.io/blckasop_r3.zip

Camera (front/back) now partially functional. Photos work, but videos crash due to

E/audio_hw_primary( 2253): pcm_open() failed: cannot open device '/dev/snd/pcmC0D3c': Invalid argument

(Guess it's time to finally tackle the mono sound/mic issues)

Busybox is now included

Recovery script has been commented out
[Galaxy Tab S General] suzook:
WOW! Thats awesome. I know your VERY busy with this build, but is there any way you could make us a 10.5 build???
[Galaxy Tab S General] xda0996:
I have good news for 10.5 owners!!! :) ....and some information that will make the dev's life easier!

As per the devs suggestions, I've rebuilt the boot.img with the 10.5 kernel, patched in the 10.5 wifi drivers and I have a booting device! Wifi works (didnt need the permissions fix this time), sound and video playback seem OK. I've only tested it for about 5 minutes so far, i'll test some more and then report back.
[Galaxy Tab S General] suzook:
WOOHOO!!!!!!!!!!!!!!!!! Can i have?? Can I? Please?????????????? Camera too???:D
[Galaxy Tab S General] thakrage:
Once you sort out the stereo sound I'll give it a spin. I can't wait!
[Galaxy Tab S General] doga.ozkaraca:
i'm having same problems with my samsung galaxy s4(i9500), how did you solved mates?

i'm deleting audio.policy etc. for seeing if device is booting..

but of course device's ringtones etc doesn'n work

i would really appreciate if you can help :)

Regards,

Doga Ozkaracaabatlioglu