yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] WuNgUn:
How 'bout some improvements like, I dunno, power option other than just "power off", for example....

Not trying to be a douche but all I see is vanilla 6.0.

Where are the change logs?

Thanks
[Galaxy Tab S Android Development] wy1d:
QYB and use Xposed
[Galaxy Tab S Android Development] WuNgUn:
Xposed... Cool. Thanks

Dunno what qyb is though....?
[Galaxy Tab S Android Development] BallCity:
Use GravityBox MM along with Xposed and you can tweak all that stuff.

The point of this ROM is to be an AOSP clone and the features you request are not in AOSP.......
[Galaxy Tab S Android Development] dsreyes1014:
Don't care about features at this point if gapps can't be installed at all. For some reason I just cant flash gapps on my t700.
[Galaxy Tab S Android Development] Kholargol:
Did you try my tip for your Google App installation ? (look my previous posts)
[Galaxy Tab S Android Development] behzad.bz:
Hi. What version of Xposed can i use? Is there any modified apk for this rom or i should use official one?
[Galaxy Tab S Android Development] chazey2:
I just upgraded to the official V79 this morning working fine T800 here.
[Galaxy Tab S Android Development] kipue:
I used to have troubles too.

Apply the OP's steps (even put the little file in the same folder with open gapps), and it should be good.
[Galaxy Tab S Android Development] sto7:
This ROM is great, thank you!

I own a Japanese SM-T700, and Samsung didn't even bother releasing their 5.0.1 update here, so I'm stuck in 4.4.2 official (although it's a pure SM-T700, Wifi only, not phone company version, Kies and OTA updates do not show).

I tried to install this ROM today, and although it took me longer than documented, and I felt multiple times it wouldn't work, I finally managed to get it working. The installation of the GApps seems particularly capricious, and multiple times they ended failing when reaching Android's home screen. In the end, I went to settings > restore, restored to "factory", and stayed patient on reboot, which took about 10 minutes.

Now it works as advertised (no camera or fingerprint), plus two other issues that I guess were just not spotted yet: the "camera flash/flashlight" does not work (because it's linked to the camera maybe?), and the ambient light sensor seems off (if I enable adaptive brightness, it is always super bright, even in a dark room).

Everything else, sound, mic, WiFi, bluetooth, seem to be working well, awesome.

Oh I read about "Now on tap" not working, and although I don't really use that feature yet, I gave it a try: after enabling the option in the Google application's settings, a long press on the menu hard key does not trigger "Now on tap", but then I tried enabling the soft keys (still the same old trick), and confirmed that "Now on tap" works on a long press of the round middle soft key.

Thanks again for this ROM! Can't wait to be able to use the camera again (not taking pictures with such a big device honestly, but it's great for video chats!).
[Galaxy Tab S Android Development] Fragnatic_89:
Thanks for the workaround with the soft keys. Tried it and it works on my T705 as well.

I use the Now on Tap feature occasionally on my Nexus 5x, and i found it really useful. Hopefully this issue can be fixed soon as it doesnt really make sense to use soft keys when the hardware keys are available..

T705 user
[Galaxy Tab S Android Development] Khar00f:
Finally installed this rom, works great, couldn't care less for camera or fingerprint sensor (never used them).

I came across one issue that could be a deal breaker for me.

The game Hearthstone doesn't work, crashes to home screen every time.

Anyone else can test?

Also every time the tablet is booted, I get an error

View attachment 3581640

Anyone else can confirm?

Thank you,

Using t800
[Galaxy Tab S Android Development] wy1d:
It's mentioned a few times in this thread that Hearthstone doesn't work with this ROM. Something about the game engine not compatible.
[Galaxy Tab S Android Development] steamrollerpark:
Thank you for a great Rom, Schischu. Forgive my ignorance, but can the Camera be made workable with files from Samsung stock MM?
[Galaxy Tab S Android Development] Raod:
Hello, I'd updated via last OTA and I'm also having this message on every boot. Other problem after this update on my device also launcher3 stopped working frequently. Did you flash with the rom last version or updated it via OTA later?
[Galaxy Tab S Android Development] Yo_MaMa:
If you find stock MM for our devices, let us all know....
[Galaxy Tab S Android Development] Khar00f:
Hi, I flashed straight to the latest (I believe it was Dec 12th update).

No OTA's done yet.
[Galaxy Tab S Android Development] steamrollerpark:
I was thinking of Camera files from other Samsung devices that get MM.
[Galaxy Tab S Android Development] Klaus20:
*** error executing updater binary in zip ***

I am trying to flash Marshmellow

And after wiping Dalvin Cache, System, Cache and Data I get always the same Error:

*** error executing updater binary in zip ***

I am coming from [ROM][STABLE][TW][5.0.2][08.11.15][SM-T800][SM-T805]IronRom Vers. 2.5

Any ideas what is wrong ??

Regards Klaus
[Galaxy Tab S Android Development] suviralu:
Was the file's checksum valid?

sent from my sm-t805
[Galaxy Tab S Android Development] Klaus20:
I dont know (How can I check it ??) - this is the checksum: 861f76a63542b147910df79d4688e052
[Galaxy Tab S Android Development] suviralu:
The corect checksum is displayed on the download page.

sent from my sm-t805
[Galaxy Tab S Android Development] Klaus20:
OK the checksum is valid.
[Galaxy Tab S Android Development] suviralu:
You got the checksum of the file on your computr on your tablet? Asking this because I already saw file corupted during transfer to the tablet (perhaps flash card errors)

sent from my sm-t805
[Galaxy Tab S Android Development] Klaus20:
Checksum on PC and Tablet is OK
[Galaxy Tab S Android Development] Khar00f:
I would recommend you flash back.original samsung ROM and start the process from there.

Flash original samsung ROM through ODIN, make sure to update your tablet to the latest software version through kies.

Then flash tarp through ODIN and follow the steps from there.
[Galaxy Tab S Android Development] Snow000man:
No need to flash stock rom again. I also came from IronROM 2.5. I just did what was mentioned in OP and it worked. Just follow steps in OP. Be sure to have the right TWRP version. Get it from here: http://xdaforums.com/galaxy-tab-s/development/twrp-2-8-6-1-unofficial-sm-t800-805-807-t3074633
[Galaxy Tab S Android Development] Khar00f:
Has anyone tested these to see if they work?

If not, I'm going to give them a try, but I wanted to know if anyone knows if they're already integrated in the newest room version (Dec 12th)?

As that would make it pointless to try.
[Galaxy Tab S Android Development] Yo_MaMa:
Yes, they're already included
[Galaxy Tab S Android Development] ankjain:
Double Tap to wake is a hit or miss

Friends

I successfully installed this ROM and everything works as written in OP. but double tap to wake ( in my T805) is not consistent. If i wake it within 1-2 minutes after screen is off then it will work but if i try to use it after a gap of more than 2-3 minutes then it does not work .

kindly let me know any workaround if possible.

regards

ankjain
[Galaxy Tab S Android Development] Jezz_X:
* First off Really nice seems to work as expected so far.

* Second I had a few troubles actually getting it to boot but turns out that I didn't have the updated bootloader like said in the original post instructions but I was using an unofficial cm 12.1 version and though I already had it, turns out I didn't

* Third would be nice if you could put the install Super User as an optional thing in the install instructions. Unlike most people here I come for updated builds not super user stuff and from my testing that part is purely optional and doesn't seem to effect anything by not having it and a lot of people would be installing it just because the instructions say so not because they want or need it
[Galaxy Tab S Android Development] ghost141:
Is there any chance to move obbsfile to SDCARD 'without' using SDCARd as internal?

LINK2SD and xposed module ''obb to sd'' ain't working at all.
[Galaxy Tab S Android Development] schrodinger56:
Flashed the ROM etc. with no bother but the external SD is unsupported and when I connect the T705 to the computer no Folders are visible. :crying:
[Galaxy Tab S Android Development] suviralu:
If you're a Linux user, then you could give `kdeconnect` a try.

sent from my sm-t805
[Galaxy Tab S Android Development] schrodinger56:
I'm not I'm a Mac and a Windows user and both systems don't display the T705's folders
[Galaxy Tab S Android Development] marcham:
Really enjoying the 6.0 ROM on the SM-700 so far. A few things I've noticed:

- You tube videos can be very choppy at times, other times they work great ... still trying to narrow it down.

- Some games fail to launch ex: FPV Freerider

- Google play videos don't work "Playback isn't supported on this device", Play Movie app lists the device as "samsung, SM-T700", maybe it should be reported as "SM-T700" ?

- T700 Battery capacity is listed as 2100mAh, should it not be 4900mAh?

The good:

- USB game pads works, so does wireless Xbox controller dongle

- Battery life seems to have improved from the Nov build, a lot less heat build up

- Bluetooth keyboards work

My main reason for moving over from the stock 5.0 was the lack of support from Samsung for bluetooth keyboards. I'm really glad to see that my MS Universal Fordable Keyboard is working great.

For the Google Play Videos, I tried removing root, deleted cache + Dalvik and that didn't work. I've tried the latest GApps and that didn't help either.
[Galaxy Tab S Android Development] schybiorz:
Remember that MM set USB in Chargingmode by default and not enable MTP. u may swipe down to notification center and click at the usb charging and set it manual to mtp mode, or u can use :

http://xdaforums.com/android/apps-games/app-mtp-enbaler-t3263467

wich is working like charm thx [MENTION=2981094]bitstra[/MENTION] for that
[Galaxy Tab S Android Development] Khar00f:
I never used link2sd nor xposed framework, I only used "folder mount [ROOT]" and that worked very well for me.

I never understood the difference between link2sd and folder mount.
[Galaxy Tab S Android Development] ghost141:
FOldermount ain't working for me too...

Maybe i should formate it to fat32 or?
[Galaxy Tab S Android Development] ghost141:
Ater 3 weeks using beloved AOSP Pure Vanilla ROM,

I decided, to SWITCH back, to IRON ROM, which is Touchwiz based...

Why? Due to some reaosn,

- Apps can't move to sd card, it's a big deal for me because 16gb storage ain't good for me. Especially some obb apps.

- No Camera / LED / Front Camera, sounds dumb, but yeah... sometime i use skype on this tab.

- No MultiWindow, for a 10inch tablet, it's really waste of screen size wihtout multi tasking apps.

- Annoying removing apps on sd card warning.

Other than that, i absolutely enjoy the PURE android experience on this tablet, it's so freaking smooooooooth from the top to the end line. Love it since i ain't see any bloat.

But still, i can't live anymore with those issues,, i will return maybe 1-2month to check some updates.

Huge thanks for the Dev who have spent his lifetime and still continue to creating a better ROM for us.

*Android M 6.0 MultiWindow ain't good enough. It still got some bug.
[Galaxy Tab S Android Development] Yo_MaMa:
We do have multiwindow
[Galaxy Tab S Android Development] edan1979:
yup... we do have multi window... you just need to activate it....
[Galaxy Tab S Android Development] wy1d:
Also wouldn't formatting SD as internal fix the storage issue?
[Galaxy Tab S Android Development] Khar00f:
I believe he started he didn't want to use the sd exclusively for internal storage
[Galaxy Tab S Android Development] Schischu:
Camera is extremely annoying.

After hundreds of hours (well at least > 100) of debugging, I am pretty confident in what the error is.

Put simply, the linker binary has received lots of changes with 6.0. The sequence in which libraries are search changed.

The bad part is that the samsung libraries are kinda stupidly linked (libexynosion overrides some function in libion) which causes the wrong functions to be called.

For example, ion_alloc is called from libion instread of libexynosion. This causes a gralloc error.

I already changed the sequence a little bit and the camera loads further. However still another lib has this error.

I can not believe that we are the only one facing this issue. Other exynos devices with 6.0 should have the same issue in my opinion.

Has anybody seen other devices with this issue?
[Galaxy Tab S Android Development] nFiniti:
Nevermind, I got it working. Had to install all GAPPS in OP to get Google play Services to somewhat function. Still crashes but works enough to test drive it.

Well, guess the "Native" USB DAC 'crap' Google has implemented doesn't work worth a damn on 6.0 either. Soo odd how it works almost flawless across soo many platforms before Android 5, then they release "Native" drivers that cripple all worthwile DACs. It's like they are purposely preventing us from using better DACs than that was installed internally so we'd be forced to use the Wolfson.

And Apple devices have Optical built in. Lol
[Galaxy Tab S Android Development] Yo_MaMa:
I'm using a DAC with this rom with no problems whatsoever
[Galaxy Tab S Android Development] ghost141:
I do tried to active it immediately from developer option at the first time i get it.

But it just really really annoying, itt's not stable enough... it's still a beta. So. NO. ;)

EG : 1 screen for youtube, 1 screen google keep. When i switch the windows to google keep, the video stop playing. DANG!
[Galaxy Tab S Android Development] Ashwin Prabhunerurkar:
Thank you for the hard word you have put in for these devices but can you release an update with repo synced to the latest so we can have the december security update and 6.0.1

I have lost hope for fingerprint scanner and camera is not a necessity for me but being on latest version with the best security is important

Hope you understand

Thank you
[Galaxy Tab S Android Development] jmendezk:
I am using CM13 temasek klte and camera is working.

Hope this is useful.

Enviado desde mi SM-T800 mediante Tapatalk
[Galaxy Tab S Android Development] Schischu:
klte is qualcom, so of course no issues there. My AOSP 6 build for Note 10.1 (2014) LTE has also working camera.

Note 3 would be interesting as same chip as our tab.
[Galaxy Tab S Android Development] NeWONEx:
If you use note 5 TW MM I think it maybe help you

http://xdaforums.com/tmobile-galaxy-note5/general/note-5-marshmallow-dump-t3249840
[Galaxy Tab S Android Development] Schischu:
FYI [MENTION=535343]all[/MENTION] Hearthstone players. thx to [MENTION=4405529]nvertigo67[/MENTION] (source) we've got a "solution".

You will have to enable 4x MSAA in development options and Heartstone will work.
[Galaxy Tab S Android Development] Khar00f:
best news ROM related I've heard in a long time.

Thank you for looking into the issue
[Galaxy Tab S Android Development] brycegreen:
It says to put the gaaps.zip and supersu.zip in the folder so it will flash after an OTA update. Does that mean we will receive Samsung updates as regular or does OP mean future updates to the ROM will be done on the device itself?
[Galaxy Tab S Android Development] wbedard:
It refers to OTA updates created and provided by the ROM developer. The OTA subsystem has no connection to Samsung in any way.

R/

wbedard
[Galaxy Tab S Android Development] brycegreen:
Amazing, thanks! So say if the next version comes out, I will not have to flash the bootloader or wipe my data. Since it's all done through the ROM?
[Galaxy Tab S Android Development] wbedard:
Have a look at the initial paragraph of the following post (though, by all means, feel free to read more...there are a lot of very informative posts in this thread.)

http://xdaforums.com/showthread.php?p=64284302

R/

wbedard
[Galaxy Tab S Android Development] BigLisy:
This is great! Will definitely settle this to be my tablet's main ROM.

One question though, does enabling MSAA mean apps (or at least Hearthstone) to run at a slower FPS due to higher graphic strain? Or it's simply how it's supposed to always be run?
[Galaxy Tab S Android Development] Khar00f:
Not sure how this function works, either when enabled it's enabled for everything in which case there will be a performance hit or alternatively enabling it only tells the system that it's available for use should an app request it, in which case the performance hit wool be limited to those apps that use it.

Doesn't mean the performance hit is anything noticeable.

I reviewed dev options on my note 4 to see if it's enabled by default and it's not, yet hearthstone works fine (running stock TW)

I'm guessing this is more of a workaround but the reason why it doesn't work by default remains unknown.
[Galaxy Tab S Android Development] brycegreen:
I formatted my SD card as internal storage and now when I try to launch Dolphin browser a notice appears saying "Doplhin requires storage permissions", but storage is already permitted in app settings. I tried moving the app to the SD card but the same notice appears. Other apps appear to be launching correctly.
[Galaxy Tab S Android Development] gscollier:
Similar setup here (internal). Dolphin works ok except doesn't remember logins. Downloads fine, all other functionality seems ok.

SM-T700
[Galaxy Tab S Android Development] brycegreen:
When you look under Settings >Apps > Dolphin where is the storage located?

Update: Uninstalled Dolphin, rebooted and re-installed seems to be working just fine.

Big UPs to the DEV on this one. Merry Christmas everyone
[Galaxy Tab S Android Development] gscollier:
Internal

SM-T700
[Galaxy Tab S Android Development] :
The main reason is bad programming in unity or hearthstone (or both): I'm not 100% sure, 'causse I havn't sourve code fpr both, but from what I saw in the logfile, EGL_BAD_MATCH is triggered by creating a new surface from a buffer; unity/heartstone does not check the size of the buffer. I don't have access to the source of mali blobs either, so I have always to guess, what's hapening, but luckily 4xMSSA seems to create a buffer in the size unity/heaarthstone expects.

So you are right: yes, it's only a workaround for bad programming habbits in unity/hearthstone. And: yes, I belive it's a little bit slower.

But: no, it will be used for all apps. That's how I understand this option's explanation text.

You are right again on default setting: on all cm roms, Ive seen since 10.0, 4xMSAA is disabled by default.

Bottom line: no matter if you are looking on aosp or cm, [MENTION=2371134]Schischu[/MENTION] and me have each about 240 MB of rom to put errors in; unity/hearthstone have nearly 3GB of application to put errors in. What do you think has a higher bug count (in absolute numbers)? ;) If I need 3GB program (I don't want to think about, what this means in source code lines), a mali gpu at fullspeed and the a15 cores at 90% for a card game, I must have made a systematical error. I.e.: AngryBirds2 relays also on unity, the graphics are comparable complex, but the size is only about a tenth of hs.

I could only think of two reasons for this oversizing: inability or hiding harmfull code. (or a contract with vodafon.... ;) )
[Galaxy Tab S Android Development] Snow000man:
Installed the 12/12 build on t805. smooth as usual. finally got gapps (benzo gapps from OP) to work on this build. then updated the gapps from play store. I was better off not using any gapps. I had gotten used to it :) I will be removing gapps.

anyway thanks to the developer.

DT2W does not work well. some times it goes directly to home screen but most times to the lock screen. I don't use this feature.

I still have issues with hardware keys backlight always on. I have turned them off from settings for now.

This version also seems to give better mobile signal strength and stability.

all in all a good rom.
[Galaxy Tab S Android Development] Khar00f:
To be fair the game is 1.8GB the other 1.5 is the OBB files which the game extracts and installs itself from and as far as I'm aware there's no other use for them, although I haven't tested it myself I'm pretty sure they can be removed after the initial unpacking and the game would still work.

I think the size odd reasonable given all the textures required but I'm not expert and who cares anyways.

I did want to ask though, I don't know how ROMs work so I'm thinking out loud, but, is your ROM using samsung video drivers or Android generic? And could that be the reason why it might not be compatible (outside if the fact that it's bad programming which is a given cause at this time)? I ask because I don't know if video drivers is something that rom makes have access to out if its close source and you have to revert to generic open source drivers.

If so would it be possible to "hack" the Samsung drivers into the rom?
[Galaxy Tab S Android Development] :
There are two parts: the kenel driver, we have source code for (here all the wunderful magic like gpu overclocking can happen ;) ), the other part is - simply spoken - in libEGL_mali.so, which is a shared library, which is used by heartstone/unity to place the eglcalls. This lib is taken from sammy stock rom. There are also other hardware specific files, we have no source code for, so that we are forced to use binary files from stock rom: sensors, camera, hw accelerated video, managimg drm comtent, gps and all I forgot...).

To use a specific piece of hardware in an app, you need a kernel driver, the closed source binary blobs, some implementation in hal (hopefully it's done by default in aosp, otherwise to have to write yoir own) and - in case of a mismatch between what aosp expects and closed source binaries - a wrapper for the calls....

I don't know, what you have thought and what you expect from "hack samsung drivers in this rom", but I think it has already done. But perhaps you like to elaborate yoir idea?
[Galaxy Tab S Android Development] NimlothPL:
Why this ROM don't have gapps persistance between dirty flashes ?
[Galaxy Tab S Android Development] Nash123:
+1

Checking with security app VTS for android the result is even worse than with latest stock rom. 2 vulnerabilities and 1 test fails.

Thanks :)
[Galaxy Tab S Android Development] WuNgUn:
T700....battery life sucks, considering how good battery life is with marshmallow on my S5.

Might try a wipe/refresh.
[Galaxy Tab S Android Development] dknk99:
This ROM feels and appears fast, thank you.

Things I have noticed:

Turning on the equalizer in Play Music causes the volume to drop greatly. Only fix is to turn it off.

Play Movies or YouTube won't allow purchased movies to play, "This video is not playable on this device"

Button lights stay on, had to turn off in settings.

No vibration for buttons

No reboot option, only shutdown (installed Simple Reboot to enable more restart options)

Install is not as smooth as it could be, installed as per instructions but had to additionally re install after wiping dalvik/cache to stop google services from crashing on initial setup (as suggested by someone in this thread)

The good:

I'm getting good battery life

Streaming music to my Bluetooth speaker works nicely

Super fast

Overall, you have done a good job on this...

SM-T700
[Galaxy Tab S Android Development] 2stardiver:
My SMT705 does strange reboots. Mostly with surfing with chrome tablet jus t reboots. Just last time when rebooted it losed 75% battery. I had 86% battery and rebooted when i looked embedded youtube. After reboot battery was 9% left. I wiped dalvik it losed that 9% in reboot.

I did clean battery stat just last week.

In android battery stat biggest consumer is over-counted: total bat capacity 2100mah, computed power use 1530mah and observed power use 1176mah.