yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] stopa10:
26/7 version on T705

Hi, everybody,

after a few days of extensive tests on my T705, I thought it might be useful to report my findings.

- First, my configuration: Xposed, with Greenify and Amplify. Viper4Android. Android Wear. Main main daily driver, most calls handled via bluetooth.

- I have to say that the ROM is much smoother and feels faster than any Stock-based ROMs I have tried. Also, Doze is very nice, and with the new Greenify is very promising.

- There are still problems, though.

- A small problem I have had after all flashes is related to the permission setting dialog: the "allow/consent" button is not clickable (the "deny" one is). However, this is minor nag, permissions can be handled using the settings screen.

- A major problem is with bluetooth. It seems to me that:

a. with the new version (26/7), bluetooth audio is very distorted (the "Saw/Helium" effect :( )

b. with the audio fix by [MENTION=6069495]haimann95[/MENTION] (and Viper4Android) audio is good, but on incoming calls the bluetooth headset is disconnected after 20secs

In both cases, bluetooth is essentially unusable.

- But there is a second major problem I found: this ROM drains the battery quite a lot. I performed quite a few tests with Better Battery Stats, and there seems to be nothing off with apps and services. The problem seems to be related to the modem: the phone keeps connecting and disconnecting from the network continuously.

Overall, the ROM has great potential, but I will revert to PowerROM for now. I will keep a backup, though. Hopefully, we will see fixes soon. :D

Have a nice evening.
[Galaxy Tab S Android Development] lawrex:
Can you Pontiac me to the correct exposed? I have tried 3 without any luck. Thank you.
[Galaxy Tab S Android Development] stopa10:
With AOSP, you need the "standard" Xposed framework by Rovo. Go to the main Xposed thread and download v86. Alternative versions (Wanam's, Dcldark's) are for Samsung TouchWiz ROMS.
[Galaxy Tab S Android Development] Mahmoud 1999:
can not update

every time it says no updates found since three or four months

and the wifi suddenly crushed and restarts again

please fix:crying::crying::crying:
[Galaxy Tab S Android Development] deanventure:
can you change the quick toggles? especially adding power save and sync?
[Galaxy Tab S Android Development] Schischu:
Update online:

Fixes BT SCO disconnect on HFP

Fixes setting "Preferred Network Type" on 705/805

Fixes doze support. Proper deep sleep handling

Improve dt2w support by better detecting/ignoring invalid wake-up guestures
[Galaxy Tab S Android Development] corb06:
Does this mean I can uninstall Greenify?
[Galaxy Tab S Android Development] Jors55:
Update 160730

First of all, thanks for the great rom:good: I has sum problems to install this rom. Ota or dirty install don't work for me. Get a server error ? So i make a clean flash. The rom works fine now on my T800.
[Galaxy Tab S Android Development] xdaq:
Same here. Appreciate if you could enable the Hotspot and Battery Saving toggle. This ROM is awesome. Tq!
[Galaxy Tab S Android Development] Maheshwara:
Very confusing with all these different versions... Which version is right for our Galaxy S Tab?

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] stopa10:
You need to download the files from the Viper4Android thread in the Tab S General forum, it's the easiest way to get this to work.
[Galaxy Tab S Android Development] Maheshwara:
I wanted the package with both Viper and Atmos...

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] Schischu:
I guess, greenify is for devices that don't support doze as far as I know.
[Galaxy Tab S Android Development] hemantgsmc.in:
thats lik a WHOA ......never thought we wud see marshmallow on the 805.....kudos to the developers.....!!!!keep up the good woork...!
[Galaxy Tab S Android Development] mertcanmusic:
Hi please more screenshoot
[Galaxy Tab S Android Development] Schischu:
Btw. Multiwindow can be enabled in the developer menu.

However does not seem to be very smooth yet...
[Galaxy Tab S Android Development] d4rk1337:
I cant install... it's saying i have a chagalwifi... but have the 805.

Do i have flashed the wrong twrp or how can i prevent this?
[Galaxy Tab S Android Development] rookie12:
Oh ya forget to ask how is the fingerprint lock working
[Galaxy Tab S Android Development] wally18324:
SM-T807P

Is it possible SM-T807P can get some love also ?
[Galaxy Tab S Android Development] siddhesh.raikar:
[ROM][T805][6.0.0_r1] Android 6 Marshmallow - Tab S 10.5 LTE

So.. This is how I did it..

First.. Wipe cache, Dalvik, system and data..

Then reboot recovery..

Then flash rom, gapps and supersu..

After booting into the rom, replace the google play services apk with the right version from apkmirror..
[Galaxy Tab S Android Development] wil123:
What version of Google play services do you install?
[Galaxy Tab S Android Development] siddhesh.raikar:
8.1.18. Ending in 436.. The force stops of google play services went away after that..
[Galaxy Tab S Android Development] calj17:
Congratulations for this project. Will be following the builds

Enviado de meu SM-N910C usando Tapatalk
[Galaxy Tab S Android Development] BallCity:
Would it be possible to flash this on the T800? I'm assuming not as I think the processors are different...
[Galaxy Tab S Android Development] Bataga:
Read that stock marshmallow works with layers. Anyone tried it yet?
[Galaxy Tab S Android Development] calj17:
Testing ROM. Runs smooth. No LTE data and no sdcard.

Question: why bootanimation still the old Lollipop animation?

Enviado de meu AOSP on chagalllte usando Tapatalk
[Galaxy Tab S Android Development] wil123:
It's working fine !

Edit : Gapps found in N6 forum : https://www.androidfilehost.com/?fid=24052804347835438
[Galaxy Tab S Android Development] ashyx:
You have installed twrp for the T800.

---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------

A little confused by this:

B]Prerequisites[/B]

TWRP 2.8.6.2 or higher[/URL]

Applied bootloader update, e.g. by flashing the stock 5.1 samsung rom.

Do you mean 5.0.2?
[Galaxy Tab S Android Development] minieod:
so excited for this to come to t700 in the future.

will be good to redo it all, my lollipop 5.1.1 has been running with some crazy battery drain
[Galaxy Tab S Android Development] wil123:
Finally i found gapps who is 100% functionnal no more google play services force close :)

link here : https://www.androidfilehost.com/?fid=24052804347835251

[MENTION=2371134]Schischu[/MENTION] This rom is fantastic and it's so smooth compared to touchwizz base Thanks for your works my tab s is really flying now
[Galaxy Tab S Android Development] Sveneezy:
I'll be tagging along on this one. :)
[Galaxy Tab S Android Development] praveenvj:
I would like to switch to vanilla android 6 on my T705. Following the thread.

Thanks
[Galaxy Tab S Android Development] wbedard:
Hi [MENTION=2371134]Schischu[/MENTION],

I am so excited about this project! I would love to follow your progress over on GitHub but was unable to locate any repos under your GitHub account that had Marshmallow branches. Have I overlooked something or are you currently keeping the codebase local until it is more stable?

I have a T800 and can't wait to be able to try out this ROM on my device. Keep up the great work!

R/

wbedard
[Galaxy Tab S Android Development] Bushcrafter:
Sorry I do not have access to a computer at the moment.
[Galaxy Tab S Android Development] BallCity:
[T800] I am not sure how to create the logcat. I tried doing an "adb logcat" command prior to booting up, and it simply stays at "waiting for device".

I tried flashing this new build, and I sit at a black screen after the "Galaxy Tab S" screen. You are right, it is a different error - it is no longer rebooting and I just have a black screen.

I will look around to figure out how to adb debug on boot...
[Galaxy Tab S Android Development] Schischu:
If it hangs at Waiting for Device it could be that adbd is not yet enabled in the settings dialog.

If that is the case, dirty flash the last working rom, enable it in developer settings and than dirty flash the latest testing rom again.

Then adb logcat should work.

Thx.
[Galaxy Tab S Android Development] Bushcrafter:
Does anyone know how to get out of twrp when it has froze while restoring data?:)
[Galaxy Tab S Android Development] BallCity:
I have generally had success force rebooting/turning off the device by holding the power button + volume down. Obviously you're going to have to boot back into recovery though in order to restore an OS.

---------- Post added at 04:42 PM ---------- Previous post was at 04:30 PM ----------

Hmm, so, I booted into a working (11/4) Marshmallow ROM and confirmed USB debugging was on. I had no issue running an "adb logcat" while booted into this ROM. However, I then rebooted to recovery, dirty flashed your newest build, ran an "adb logcat" in windows, and rebooted, and it stayed at "waiting for device". For some reason I cannot get a logcat running while booting a ROM....

EDIT: For ****s and giggles, when I restored the working build while still having the logcat wait, it did in fact start outputting logs once my ROM booted past the boot image. The question is, how can I logcat prior to even getting the ROM booted?
[Galaxy Tab S Android Development] Bushcrafter:
Thanks for the reply.
[Galaxy Tab S Android Development] Schischu:
Thats okay, logcat buffers messages.

Can you send me the log by pm? Thx.
[Galaxy Tab S Android Development] BigLisy:
Hearthstone crashes after unpacking (not even force close error message, just poof), big bummer :| First thing I encounter that does not work however.
[Galaxy Tab S Android Development] zigonneux:
we presume that you are talking about a t-800
[Galaxy Tab S Android Development] BigLisy:
Whoops, forgot to mention I'm on a T805.
[Galaxy Tab S Android Development] haimann95:
Let's see who is faster with upgrading the T705 to Android Marshmallow. Samsung or Schischu.
[Galaxy Tab S Android Development] NeWONEx:
Try Samsung and TW

And remember he didn't have T705 and there is issue in T800 he try to solve this issue

You have to wait
[Galaxy Tab S Android Development] haimann95:
Yeah, but it's annoying to see the T705 always as the last device for all roms.
[Galaxy Tab S Android Development] NeWONEx:
I can say the last device get CM here is T805 and The last device get custom rom

So you have to be happy

At all you know the different between make for WiFi or make for Lite and this why he chosen to make for T700
[Galaxy Tab S Android Development] schiphol:
Perfect if this were to come to T705. I'll wait patiently though, hope you can bang out a version with 4g Internet and phone working!

Is anyone working on kernel mods for this project already?

Would be fantastic if we had something like SkyHigh with Marshmallow so everyone can just set up their kernel the way they like rather than defaults some else figured would work well for me.

Why would you need any other tablet for the next year or so?

Thanks!!
[Galaxy Tab S Android Development] Schischu:
And another testing T800, again with old blobs as I need to establish a working base before readding them.

aosp-eng.ubuntu.20151110.200832.zip
[Galaxy Tab S Android Development] calj17:
[MENTION=2371134]Schischu[/MENTION] any idea why adobe Reader is crashing and closing?

Enviado de meu SM-N920G usando Tapatalk
[Galaxy Tab S Android Development] BallCity:
Clean flashed this ZIP then GAPPS from the original post - it boots! Haven't had a chance to test and identify any issues yet though.
[Galaxy Tab S Android Development] Schischu:
Perfect, can you check if changing display colortone and button backlight settings work?

Thx again for your help.
[Galaxy Tab S Android Development] BallCity:
Button backlight: Yup - this setting works! Switched it off, button backlight turned off. Switched it back on, button backlight turned back on.

Colortone - this setting also works! I switched to Movie and it turned more pinkish, etc. I am not sure what the difference is between these but they all seem to change the display.

(Both of these are under the "Display" section in settings, of course)
[Galaxy Tab S Android Development] Maheshwara:
I installed the package you required, but it crashes when installing the drivers. Seems it does not work. So I will have to stick with Atmos.

//Edit

Sorry, mate, was my fault... Just discovered that SuperSu disappeared after ROM upgrade. I still have been root, but the SuperSu app was gone. After reinstall, I was able to grant permissions to Viper and then, driver install was successful. Now I will try it.
[Galaxy Tab S Android Development] stopa10:
Yes, that happens after each update. You need to re-install SuperSU from the Play Store. And yes, that was the problem with Viper, it needs root permissions to install the driver.

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

Well, although they have the same purpose, Greenify and Doze are complementary. In fact, the new Greenify (2.9 beta, only available through the beta channel), can be used to run Doze in aggressive mode, which is awesome.

I will test the new version of the ROM later on today and report about battery drains.
[Galaxy Tab S Android Development] vonschau:
New update

Schischu - great ROM update was smooth and everything works like expected, about time to buy you an other beer:good:

on T-800
[Galaxy Tab S Android Development] Meandi51:
Updated via opendelta w/o any issues.

Thanks [MENTION=2371134]Schischu[/MENTION]
[Galaxy Tab S Android Development] Schischu:
Thank you. As always every donation is deeply appreciated.
[Galaxy Tab S Android Development] chazey2:
You got another, great work thanks.
[Galaxy Tab S Android Development] aegeuss:
Thanks for this update. I have a small problem with the sd card which I am using it as adoptable storage. Last update was flawless but this time the apps on the sd card are seen as unavailable; however I can start them inside Play Store.

Regard.

edit: After playing with new rom for half an hour I have realised lags and general slowness in Nova launcher; it was way more fluid in the previous version.
[Galaxy Tab S Android Development] MUSTANG651:
Thank you very much! Can I ask you to add 3G/LTE only mode for 705/805 models?
[Galaxy Tab S Android Development] choclaterain:
Any chance of support for the SM-t807t? Could I just install it?
[Galaxy Tab S Android Development] DeadPicsel:
I keep getting Signal drops intermittently, it's always when I'm doing something important as well. Is there any way of fixing this issue?
[Galaxy Tab S Android Development] borice91:
GAPPS persistent problem !

Tried to update my Android version with hope to fix the wifi with the last update, and here we are again, with the "Google Play services has stopped" issue.

Nothing works this time. Tried dozen of times to alternate the steps....

Deleting runtime-permissions.xml seems to help when you boot the first/2nd/3th times to grant apps permissions and let the application optimization process to do his job but still after that the Play Store can't start properly. Definitevely need something else.

Help please.
[Galaxy Tab S Android Development] fiowro:
sound while call with the last update

I have tried 2016-07-30 version of the ROM for T705 (both as OTA update and as a clean install after all possible wipes).

Here is my report on calling via bluetooth headset.

Call doesn't mutes sound after 20+ seconds of talk anymore, so this bug is finally gone.

Voice pitch while call is still wrong, so hamster voice effect is present :)

Fortunately the patch from haimann95 still works, so applying it makes this ROM to be fully functional.
[Galaxy Tab S Android Development] fvultee:
Same here, boots fine after most recent rom following these steps, but the dreaded "Google Play services has stopped." Hmm.?
[Galaxy Tab S Android Development] stopa10:
Yes, my tests confirm that:

- no more disconnections when calling with bluetooth

- Bluetooth audio is still distorted

- nor Dolby Atmos nor Viper4Android solve the problem

- the fix by [MENTION=1659056]heimann[/MENTION]95 does, though

[MENTION=2371134]Schischu[/MENTION], you may consider adding the fix by [MENTION=1659056]heimann[/MENTION]95 at post #3916 to your next update.

Battery life has also improved, although there are still frequent disconnections from the cell network.

Overall, I am thinking about keeping this.

Thanks a lot to Schischu and everybody else for the great work. ?
[Galaxy Tab S Android Development] andredss:
Same here :crying::crying::crying:. Any solution?
[Galaxy Tab S Android Development] zephymobile:
need some help just tried to dirty flash new ROM for 7/30 and now i am stuck on animation screen and device wont turn off with holding power button. Any ideas?
[Galaxy Tab S Android Development] majdnem:
push ALL ! buttons at the same time for 10 seconds ... will switch it off
[Galaxy Tab S Android Development] zephymobile:
all buttons?? i pressed volume and home and power at same time and doenst work. I cant press volume down with volume up!!

---------- Post added at 10:27 PM ---------- Previous post was at 10:26 PM ----------

it was volume down and power and home, thanks!

---------- Post added at 10:31 PM ---------- Previous post was at 10:27 PM ----------

dang can't get into twrp now. it'll enter odin but not twrp with volume up. Sheesh how annoying. Anyone with ideas?
[Galaxy Tab S Android Development] Phreaker47:
Yeah, I've been introduced to the "google play services has stopped" thing. Tried latest builds of rom + gapps first, then went backwards one build on each, still same result.

This is on a T-800. (Also, I did have to reboot to recovery before flashing gapps, or I would get the flash error every time)

Anybody have a confirmed combination of builds that doesn't do this?

I'd really like to get Marshmallow on this to see if i can really use bluetooth headphones while watching video.... finally

Update: just got past this by updating TWRP. I had a higher version (2.8.7.1) than OP said I needed, but on a tip I saw elsewhere I updated to TWRP 3.02 and now I am completing the initial setup successfully. Hope it all works! Will know soon enough.
[Galaxy Tab S Android Development] Phreaker47:
Unfortunately I'm going back to Lolly for now... two issues: one, my BT mouse only partially works... clicking scroll wheel no longer works as the home key, and right click no longer works as the back button. Second, FakeGPS currently doesn't work in priv-app for using without mock locations enabled. I need this for, uh, development purposes.
[Galaxy Tab S Android Development] hochoch:
Try holding volume up home and power? It's either up or down but has to be right as the tablet is rebooting. I know volume down and power reboots though. I thought mine was messed up as well but tried the other direction at the right time and it worked.
[Galaxy Tab S Android Development] Phreaker47:
I do this exactly to enter recovery manually:

- power off

- Hold vol up and home keys

- while holding those two, power on like you normally would, let go of the power button when the first splash screen comes on but continue holding vol up and home until you see the teamwin screen
[Galaxy Tab S Android Development] zephymobile:
Thanks for the tip. I actually had to press down and home and power to reset. It would not turn off until I plugged it into USB. Would still not go into TWRP so i had to ODIN it. Crossing my fingers that it may startup after flashing it to 7/12 and not 7/30. It went back to bootloop with reflash of 7/30. Major headache.
[Galaxy Tab S Android Development] TheWynterKnight:
Got stuck in bootloop after flashing OTA update, what did I mess up? (T700)

So first of all thanks a ton for making this and maintaining it, its an amazing project.

Second of all I'm an idiot and probably missed a step somewhere. I got a notification about an OTA update, and so I downloaded it and hit the flash button. After that the tablet rebooted and flashed the new file in recovery then restarted. It appeared to boot up fine, then after about 5 seconds, it shut off and tried to restart. From that point on it was bootloop. I tried to get it into recovery mode, but it would just powercycle and try to restart, so Idk if the recovery got deleted or something. Can somebody let me know a safe way to flash OTA updates from now on, and preferably how to retain root and everything during it?

Actually another thing I remember seeming odd. When I hit flash OTA update, instead of the popup window that stays up while the device is shutting down saying "restarting device" or whatever, it said "Factory Reset". Idk if that's just AOSP being confused about being forced into custom recovery or something, but wanted to put that out in case its related.

[UPDATE] So I was dumb and was able to get into recovery. I wasn't holding the home button. TWRP seemed unharmed by the update, and I was able to run a full wipe of all partitions and flash the 7/30/2016 update with no issues. Took a while to do first boot but made it to home screen just fine, just like usual. Still curious as to how to properly do updates without having to wipe partitions and do a clean flash, as to retain user data.
[Galaxy Tab S Android Development] Mr niceguy:
erase111
[Galaxy Tab S Android Development] Schischu:
Quick reminder for all people with Gapps crashes and bootloops after the OTA
[Galaxy Tab S Android Development] stopa10:
Bluetooth works like a charm for media playback. I use it with MX Player and Viper4Android and is great.
[Galaxy Tab S Android Development] borice91:
And if we have Gapps crashes / issues with fresh installs (Not OTA related)... ?

What can we do ? The current Instructions don't work neither deleting "runtime-permissions.xml" neither alternative methods given by members. Gapps always fails...
[Galaxy Tab S Android Development] stopa10:
There are only a few hints that seem to make a difference here :

- use a recent TWRP, v3.2.0.1 by ashix works fine

- use only the nano version of Open GApps

- reboot *recovery* (not system!) after flashing ROM and before flashing GApps

I never had problems with GApps under these conditions.
[Galaxy Tab S Android Development] borice91:
Ok, thanks for the help.

So I tried 3x times your instructions (+ the ones from original post) and my conclusion is whatever you do, it WON'T WORK with the "stock" version of OpenGapps.

It works fine with the "nano" and the "full" (same as stock but don't remove the AOSP default apps). So that's the current problem. There is a conflict with the default apps and someting in the "stock" package. So I guess it works fine with "full" and also smaller versions.

Note : Also I didn't have to mess with "runtime-permissions.xml".

Thank you very much for your help.

So people who have problems with Gapps : Don't use the stock (and I guess the super too) versions. Use "full" or smaller versions.
[Galaxy Tab S Android Development] bono82:
anyone else having issues with mobile data on the 10.5 using this rom? iam able to recieve texts etc, but it wont connect to data service.. correct APN is set (telia in sweden), but it only gives me "error while searching for networks" when looking in network operators menu.
[Galaxy Tab S Android Development] fenriz666:
Hi there:

Anyone else having issues with battery life? The Rom runs smoothly but drains battery in few minutes for example using uber app (uses GPS) an drain it from 100 % to 63 %, general the battery life in my device is so poor.
[Galaxy Tab S Android Development] stopa10:
Battery life has improved in the last version. Still worse than stock, but definitely improved (Schischu fixed the doze module). There is still work to do, though, since MM is supposed to be much more battery efficient than L.
[Galaxy Tab S Android Development] Schischu:
Thanks for the find, will add a note to the op. Of course the op has always directed to the nano package, so everybody who followed the op letter by letter should!d not have had any problems.. ;)